Skip to content
ToolCargo

The MCP directory / Open to explore

MCP server directory.
Find your next tool.

Search 3,974 indexed servers from the official MCP Registry and selected vendor documentation. Find remote endpoints and local packages, inspect the publisher’s setup details, then connect in your AI client.

Where will your next task take you?

Free discovery · no account · no API key

Let your agent do the finding.

Paste into your AI agent
Read https://toolcargo.com/agents.txt, then find the MCP servers I need and help me connect them. Ask me what I want to do first.

Or add https://toolcargo.com/mcp as a Streamable HTTP MCP server. Discovery is free and needs no account.

Compare task fit, publisher, permissions and a small acceptance test with the MCP server selection guide.

Connect directly to official MCP servers

Vendor setup guides for your existing accounts. These connections run with the vendor; ToolCargo does not host them or supply their credentials.

Browse the remote MCP server directory →

Not sure which connection to choose? Read local vs remote MCP servers. Building a discovery workflow? See the MCP server search API reference.

telegram-slack-mcp

Close details

Read and reply to your personal Telegram chats and all your Slack workspaces.

Directory identity: io.github.nileshpatil6/telegram-slack-mcp · Version: 0.5.1

Publisher connection metadata
{
  "remotes": [],
  "packages": [
    {
      "registryType": "npm",
      "identifier": "telegram-slack-mcp",
      "version": "0.5.1",
      "transport": {
        "type": "stdio"
      },
      "runtimeArguments": [
        {
          "description": "Which server to run: 'telegram' or 'slack'",
          "isRequired": true,
          "format": "string",
          "value": "telegram",
          "choices": [
            "telegram",
            "slack"
          ],
          "type": "positional",
          "name": "server"
        }
      ],
      "environmentVariables": [
        {
          "description": "api_id from https://my.telegram.org (Telegram server only)",
          "format": "string",
          "name": "TELEGRAM_API_ID"
        },
        {
          "description": "api_hash from https://my.telegram.org (Telegram server only)",
          "format": "string",
          "isSecret": true,
          "name": "TELEGRAM_API_HASH"
        },
        {
          "description": "Set to 1 to allow sending Telegram messages as you. Off by default.",
          "format": "string",
          "name": "TELEGRAM_ALLOW_SEND"
        },
        {
          "description": "One Slack user token (xoxp-) per workspace, comma separated (Slack server only)",
          "format": "string",
          "isSecret": true,
          "name": "SLACK_USER_TOKENS"
        },
        {
          "description": "Set to 1 to allow posting to Slack as you. Off by default.",
          "format": "string",
          "name": "SLACK_ALLOW_SEND"
        },
        {
          "description": "Where the Telegram session is stored. Defaults to ~/.chat-mcp",
          "format": "string",
          "name": "CHAT_MCP_DATA_DIR"
        }
      ]
    },
    {
      "registryType": "pypi",
      "identifier": "telegram-slack-mcp",
      "version": "0.2.2",
      "transport": {
        "type": "stdio"
      }
    }
  ]
}

Remote URLs go into your client's MCP settings. Local packages need a compatible runtime. Check required headers, environment variables, permissions and provider costs before setup.

Publisher repository ↗

3,974 results

Index updated 2026-10-02

This directory combines dated registry listings and selected vendor-documentation entries. Documentation checks are not live account or client verification. Third-party servers run with their own providers, credentials and pricing. ToolCargo discovery supplies setup metadata; it does not run their tools. Explore ToolCargo's hosted connectors.