Echoly MCP Server

by 2cstudiodev-web Your server? Claim it

answering

Echoly is answering right now. Last checked 7 min ago.

Schedule posts to X and Telegram channels from your AI app. Posts wait for your approval.

Uptime history 4 hours of history

4 hours agonow

100.0%

Uptime 24h

12 of 12 checks

—

Tools

hidden behind auth

96 ms

Response time

average over 24h

OAuth sign-in

Access

streamable-http

Nothing serious here today

Today is the operative word: we check Echoly 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 7 min ago.

Claude Code Claude Desktop Codex Cursor VS Code

run in your terminal

claude mcp add echoly --transport http https://echoly.2cstudio.app/mcp

Settings → Connectors → Add custom connector, then paste this address

https://echoly.2cstudio.app/mcp

~/.codex/config.toml

[mcp_servers.echoly]
url = "https://echoly.2cstudio.app/mcp"

.cursor/mcp.json

{
  "mcpServers": {
    "echoly": {
      "url": "https://echoly.2cstudio.app/mcp"
    }
  }
}

.vscode/mcp.json

{
  "servers": {
    "echoly": {
      "type": "http",
      "url": "https://echoly.2cstudio.app/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://echoly.2cstudio.app/mcp	streamable-http	sign-in	89 ms	7 min ago

Alternatives to Echoly

same job, measured the same way

yeetpost

by yeetpost

Post and schedule to LinkedIn, X, Bluesky, Discord, Telegram and Mastodon from AI agents.

answering

AdminHub for Telegram

by adminhub

Run a Telegram channel from your AI agent. Posts go out through your own bot, not your account.

answering

Pally

by pally

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

answering

Automata

by getautomata

Scoped, revocable access to your WhatsApp, Telegram, IMAP email and PostgreSQL for AI agents.

answering

Agent Outbox

by roxinbox

Let AI assistants post to your Telegram chats, groups and channels. Not affiliated with Telegram.

answering

Postlyra

by prof-1t

Manage Telegram drafts, media, schedules and publications from AI clients.

41 tools answering

dopost

by dopost

Schedule and analyze posts on 12 networks, incl. Bluesky, Mastodon and Telegram, from any AI agent

answering

Tgatlas

by starnikovoleg

Public Telegram channels for agents: profiles, posting cadence, and similar-channel discovery.

43 installs/wk local only

Echoly — questions

Answers built from our own checks of this server.

Why is there no tool list for Echoly?

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 Echoly working right now?

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

How do I connect Echoly?

Copy the ready config from this page. We generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each in the form 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 Echoly?

No API key is involved. Echoly 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 Echoly?

It answers our handshake in 96 ms on average, which is faster than 92% of all working MCP servers we measure. That puts it in the quick quarter of the ecosystem. The comparison comes from our own checks across the whole registry, every 15 minutes.