Discover the Best AI Tools

opencompany combines AI chat, durable tasks and workflows, connected integrations, wiki knowledge and cloud coding sessions in a web workspace. Its current setup is maintainer-oriented and depends on managed infrastructure credentials; a credential-independent core local setup is not documented. Provider-backed features require separate service access.

WeFlow CLI queries and exports authorized local WeChat data and builds reading digests, knowledge search and MCP workflows. AI features use configured local or remote models; local storage does not imply all processing stays offline. Data initialization varies by platform and WeChat version, and remote models can receive selected content under privacy settings.

Magzdown Agent Tools converts agent-written Markdown into a link displayed as a paginated document by Magzdown. It includes an executable MCP server alongside editor instructions. The text is encoded into the URL rather than uploaded separately; the tool rejects content over 100 KB, and anyone receiving the link receives the content.

opn-mcp lets assistants shorten and manage links, read analytics and generate QR codes through an opn.onl instance. It requires an API key and a hosted or self-hosted backend; it is a connector, not a standalone shortening service.

ChatCrystal imports AI coding conversations into structured notes, semantic search, a tag graph and reusable MCP memory. It offers a Windows desktop app and local web/CLI interfaces. Summarization and embeddings require separately configured providers; choosing remote providers sends the relevant content to those services.

MCP adapter for creating, listing, updating and cancelling Pingfyr reminders, including recurring schedules and time zones. Connects to the hosted service for delivery through configured email, webhook, messaging or calendar channels. Requires a Pingfyr API key; local stdio use requires Node.js 18+. The adapter is not a standalone offline reminder scheduler.

MCP adapter for Website Toolbox forum categories, topics, posts, users and permissions. Requires an existing forum and its API key. Includes creation, updates and deletion against the live Forum REST API; it is not a read-only forum search tool.

Local-first MCP tools for work memory, time awareness, task breakdown and reframing ambiguous workplace language, aimed at neurodivergent professionals. Requires Python 3.11+, Node.js 22+ and a configured model/client. Local model use is available and cloud providers are opt-in; guardrails are software aids, not diagnosis or demonstrated clinical treatment.

MCP for sending and reading SMS through a paired Android phone and its own number using textbee. Requires a textbee account, API key and active paired device; self-hosted instances are supported. The key has full account access and messages use real mobile service, so no per-message markup does not eliminate carrier costs.

Telegram MTProto terminal client, MCP server and SSE notification stream with messaging, media, scheduling and a local search mirror. Requires Telegram session authentication; the local mirror covers synced data. MCP pushes are off by default, and sending some new reaction emoji requires Telegram Premium.

MCP adapter for the Viber Bot REST API, including messages, media, files, broadcasts and webhooks. Requires Node.js 20+ and a bot token. Access is to the configured bot, not a personal inbox; new bot accounts may require commercial onboarding and applicable service terms.

Discord management MCP for chat, moderation and server configuration, using the client AI and a configured bot. Requires Node.js 20+ and Discord permissions. Safe mode previews destructive actions with confirmation tokens but can be disabled; it is not an unconditional human-approval guarantee. Elastic License 2.0 restricts managed-service redistribution.

MCP for Apple services via local macOS AppleScript or cloud IMAP/SMTP, CalDAV and CardDAV. Requires Node.js 20+; local mode needs macOS permissions, cloud mode needs credentials. Notes, Messages, Reminders and Safari are local-only; reading Messages additionally needs imsg and Full Disk Access. Native apps may still sync or send externally.

QQ messaging and group-management MCP built on NapCatQQ/OneBot v11, with files, scheduled wakes and desktop agent wake rules. Requires QQ, NapCat and platform-specific automation dependencies. This is an unofficial bridge with real messaging and moderation effects; it is not a Tencent-supported API.

MCP for CardDAV contacts, address books, groups and photos on an existing server. Requires credentials and Node.js 22+ or Docker. Google Contacts is unsupported; reads and writes are available, with read-only mode opt-in and address-book restrictions configurable.

MCP voice calls and tiered alerts using SIP, local speech recognition and TTS, with the host agent providing the conversation model. Needs SIP setup and speech components; Windows uses WSL2 or Docker. iPhone critical push alerts may require paid Pushover, and the voice dependency has a GPL licensing caveat.

Telegram MCP gateway with HTTP/stdio transport, multi-user sessions and MTProto access for agent messaging. Requires Telegram authentication; hosted use entrusts the gateway with session access. Per-principal restrictions and read-only ACLs are opt-in, so they should not be assumed active by default.

Desktop MCP integration for email, messaging, calendars, files and other apps on macOS and Windows. Tool availability, permissions and sign-in requirements vary by platform. The core binary is proprietary; this repository supplies release information and a wrapper. Optional Cloud Relay supports web assistants, and local execution does not prevent content reaching cloud models or services.

MCP bridge for Discord messages, channels, forums, roles and moderation. Requires a bot token, appropriate intents and Discord permissions. Read-only mode must be enabled explicitly; normal mode includes destructive operations, still constrained by Discord role hierarchy.

Local MCP and native macOS accessibility bridge for reading and sending WeChat messages through Codex, with compact incremental context and chat matching. Requires macOS, WeChat, Node.js and accessibility permission. UI changes can break selectors, retrieved text reaches Codex, and sends are not idempotent: an uncertain result needs inspection before retrying.

Python, CLI and MCP client sending notifications to a paired WhatsApp phone and receiving replies or button answers. Requires a pingwa key and backend service. Quotas and reply windows apply; the MIT repository covers the client only, while the separate private backend is not included or made self-hostable by the client license.

Local layer over signal-cli adding persistent SQLite message history, full-text search, conversation views and MCP/CLI operations, including desktop history import. Requires configured Signal access and signal-cli. Local persistence can retain message copies, and content returned to an external model is governed by that model rather than Signal transport encryption alone.

MCP bridge searching messages, chats, dates, topics and statistics in an existing Telegram-Archive instance. Requires that archive backend and its data; it is not a standalone live Telegram client or archival crawler. Offers stdio and HTTP, with authenticated protection needed when exposing the HTTP service beyond loopback.

MCP interface to Gambot WhatsApp Business messaging, templates, contacts, CRM and campaigns. Requires an organization token and configured business account. Uses the existing hosted API rather than providing a separate backend; message windows, template approvals, permissions and service limits still apply to real outbound communications.