"Understanding File Structures" matching MCP servers:

Enables uploading local files to Slack with a message, supporting channels, DMs, threads, and file titles.

Enables a Telegram bot to securely deliver local files to the owner's private chat and lets the owner approve in-chat plugin updates.

Enables Codex to locate QQ groups by name or number and search group file directories and recent chat attachments by filename, then download selected files through a locally deployed NapCat instance, returning paths, sizes, and SHA-256 hashes.

A Model Context Protocol server providing file search and question tools for AI models. Enables keyword search in files with line numbers and integration with external chat services.

Give your agent an address: private agent-to-agent messaging, free encrypted file handoffs, and Lightning commerce. Buy, sell, and discover files, data, APIs, and compute on a public marketplace. Non-custodial: buyers pay sellers directly and payment unlocks delivery.

Connects Claude Code instances to a clawborrator hub via WebSocket, enabling cross-session communication, file exchange, and agent dispatch.

Enables peer-to-peer asynchronous conversation between Claude.ai and Claude Code instances via a shared file-based notebook, allowing them to leave messages, start threads, and organize by project.

Exposes Poi's external APIs (file upload/download, commenting, license key issuance) as MCP tools for use with LLM clients like Claude.

Lets separate coding-agent sessions coordinate through a shared, role-addressed mailbox instead of a human relaying every message, over a single local SQLite file or a hosted server with many isolated channels. Messages can be sent as tracked obligations that stay open until one side resolves and the other confirms, alongside threads, full-text search, work statuses, and an append-only versioned pin system where protected changes require recorded agreement from every declared role.

MCP server for inter-agent mailbox communication using file-based mailboxes in .claude directories.

Lets MCP clients sign a member in through LinkedIn's three-legged OAuth flow, read that member's OpenID profile, and publish text posts on their behalf, with stored sessions kept in a local mode-0600 file. It uses only public member APIs, so messaging, invitations, media uploads, and other people's data stay out of scope.

Security-first SendGrid MCP server: two-phase sends, dry-run by default, recipient allowlists, rate limits, audit log, no BCC. One auditable file.

Automatically transcribes Google Chat voice messages using Groq Whisper API, and also supports local audio file transcription.

An MCP server and CLI for Ed Discussion that gives LLMs access to threads, comments, attendance, moderation, file uploads, and instant local search through 43 tools.

A local MCP server that structures stock mentions and narrative flows from Telegram channels, providing momentum detection and historical analysis for AI assistants like Claude.

Enables multiple AI agents and humans working in the same project to share status, exchange messages, and claim files through a local collaboration board. It supports project-specific enablement, conflict-aware file claims, and shared state via SQLite.

Provides secure, read-only access to Slack workspaces, letting MCP clients read channels, messages, users, and file metadata without write permissions.

Exposes the Telegram Bot API as tools for Claude Code or any MCP client, enabling message sending, chat management, file handling, and bot information retrieval.

Enables agents and applications to send notifications through configurable channels such as Telegram or a JSONL file, with queued delivery, status tracking, idempotency, and event-based routing.

Integrates AI assistants with Slack workspaces using OAuth 2.0 authenticated user tokens for secure, multi-functional interaction. It enables comprehensive operations including channel management, message searching, file handling, and reaction management through natural language.