InboxMCP MCP Server

by breakcold Your server? Claim it

answering

InboxMCP is answering right now. Last checked 10 min ago. Last commit 13 Oct 2026.

LinkedIn, WhatsApp, Telegram and Instagram inboxes, profiles and outreach for your AI assistant.

Uptime history 69 hours of history

69 hours agonow

100.0%

Uptime 24h

92 of 92 checks

—

Tools

hidden behind auth

336 ms

Response time

average over 24h

Stars

last commit 13 Oct 2026

Nothing serious here today

Today is the operative word: we check InboxMCP every 15 minutes and re-read its code on every release. Watch it and you find out the day that stops being true.

Connect this server

Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 10 min ago.

Claude Code Claude Desktop Codex Cursor VS Code

run in your terminal

claude mcp add inboxmcp --transport http https://inbox-mcp.com/mcp

~/Library/Application Support/Claude/claude_desktop_config.json

{
  "mcpServers": {
    "inboxmcp": {
      "url": "https://inbox-mcp.com/mcp"
    }
  }
}

~/.codex/config.toml

[mcp_servers.inboxmcp]
url = "https://inbox-mcp.com/mcp"

.cursor/mcp.json

{
  "mcpServers": {
    "inboxmcp": {
      "url": "https://inbox-mcp.com/mcp"
    }
  }
}

.vscode/mcp.json

{
  "mcpServers": {
    "inboxmcp": {
      "url": "https://inbox-mcp.com/mcp"
    }
  }
}

This endpoint answered with an authorization challenge. The server is running, and it signs you in through your browser: there is no API key to paste.

Endpoints

URL	Transport	State	Latency	Checked
https://inbox-mcp.com/mcp	streamable-http	sign-in	370 ms	10 min ago

Alternatives to InboxMCP

same job, measured the same way

Ficiel MCP

by ficiel

Read and search your Instagram, WhatsApp and LinkedIn DMs and prepare follow-ups you approve.

answering

Nilyo

by nilyo

Your own LinkedIn, WhatsApp, Instagram, Telegram, Email and Calendar accounts, usable from any agent

answering

Dialogbrain

by dialogbrain

Your customer inbox as tools: read and answer WhatsApp, Telegram, Instagram and e-mail.

answering

Pally

by pally

Chat with Pally, the AI assistant in your texts and on Telegram, from any MCP-compatible AI app.

answering

DOS AI

by dosai

Run WhatsApp and Telegram AI assistants: projects, prompts, leads, chats, analytics.

15 tools answering

Oneprofile

by getoneprofile

Find prospects, research them, and run email and LinkedIn outreach in your Oneprofile workspace.

answering

WarmySender

by warmysender

AI-agent outreach: cold email, warmup, LinkedIn, Instagram, WhatsApp, verification, 200M leads

43 installs/wk answering

ReciboPro Invoices

by elevaredigital

Create invoices from your AI assistant in 6 languages and 10 currencies, ready for WhatsApp.

2 tools answering

InboxMCP — questions

Answers built from our own checks of this server.

Why is there no tool list for InboxMCP?

The server answered our handshake with an authorization challenge, so it is running — but it will not describe its tools to an anonymous client. To see them you need to connect with your own credentials. We record it as alive, not as broken: 100.0% of checks in the last 24 hours got a reply.

Is InboxMCP working right now?

We send a real MCP handshake every 15 minutes. Over the last 24 hours 92 of 92 checks got a reply (100.0%), average response time 336 ms. The bar chart above shows every period we have measured.

How do I connect InboxMCP?

Copy the ready config from this page — we generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each with the file path that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address. You sign in through your browser once and the client keeps the session: no key to copy, and it refuses anonymous clients.

How do you sign in to InboxMCP?

No API key is involved. InboxMCP answers our knock with an OAuth challenge, so you authorise it once in your browser and the client keeps the session. That is also why we see no tool list: it will not describe itself to an anonymous client, and that is the server working as intended, not a fault.

How fast is InboxMCP?

It answers our handshake in 336 ms on average, which is faster than 40% of all working MCP servers we measure. The comparison comes from our own checks across the whole registry, every 15 minutes.

Is InboxMCP open source?

Yes — it is published under the MIT licence and 0 stars on GitHub. The source link is on this page, so you can read exactly what it does with your data before you connect it.