mcpbeat Sign in

Chatra MCP by usefulapi MCP Server

answering

Chatra MCP by usefulapi is answering right now. Last checked 2 min ago. It exposes 10 tools. Last commit 25 Oct 2026.

Read and update Chatra visitors; send, edit and delete chat and pushed messages.

Uptime history 28 hours of history
28 hours agonow
100.0%
Uptime 24h
92 of 92 checks
10
Tools
read from the server
344 ms
Response time
average over 24h
0
Stars
last commit 25 Oct 2026

What changed 4

Every tool that appeared, vanished or quietly changed what it asks for. Recorded since 25 October 2026. No other catalogue keeps this.

25 Oct a tool changed version4 times that day
and 3 more, back to 25 October 2026

Nothing serious here today

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

Three servers free · no card

Connect this server

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

run in your terminal
claude mcp add chatra --transport http https://chatra.usefulapi.io/mcp
Settings → Connectors → Add custom connector, then paste this address
https://chatra.usefulapi.io/mcp
~/.codex/config.toml
[mcp_servers.chatra]
url = "https://chatra.usefulapi.io/mcp"
.cursor/mcp.json
{
  "mcpServers": {
    "chatra": {
      "url": "https://chatra.usefulapi.io/mcp"
    }
  }
}
.vscode/mcp.json
{
  "servers": {
    "chatra": {
      "type": "http",
      "url": "https://chatra.usefulapi.io/mcp"
    }
  }
}

Available tools 10

Read directly from the server with tools/list, grouped by what they act on. If a tool disappears, we record the date.

chatra
chatra_delete_message
WRITE, IRREVERSIBLE: delete an agent message from the conversation. Only agents' messages can be deleted, not visitors'. Returns the deleted message. DELETE /messages/{id}.
chatra_delete_pushed_message
WRITE, IRREVERSIBLE: delete a pushed message sent earlier. Returns the deleted message. DELETE /pushedMessages/{id}.
chatra_edit_message
WRITE: replace the text of an agent message that was sent earlier. Only agents' messages can be edited, not visitors'. The visitor sees the edited text. Returns the updated message. PUT /messages/{id}.
chatra_edit_pushed_message
WRITE: replace the text of a pushed message sent earlier; the visitor sees the edited text. Returns the updated message. PUT /pushedMessages/{id}.
chatra_get_message
One chat message by id (a visitor's or an agent's): type (agent or client), text, visitor id, agent id, timestamp (ms) and receivedFrom. Chatra has no endpoint to list a conversation, so the id must come from a send call or a webhook. GET /messages/{id}.
chatra_get_pushed_message
One pushed (automated) message sent earlier by id: text, visitor id, agent id, timestamp (ms), isPushed. GET /pushedMessages/{id}.
chatra_get_visitor
A chat visitor by id: name and contact details (basicInfo, integrationData and the merged `info`), custom form answers, location, browser, the link to the chat in the Chatra dashboard, the agent group, and the pages viewed in the latest visit. The id is the `clientId` your website passed to the widget or the visitor id from a Chatra webhook; Chatra has no endpoint to list or search visitors. GET /clients/{id}.
chatra_push_message
WRITE: send an automated message (order status, product update, announcement) to a visitor whose account is bound to Chatra through a clientId. It is delivered into the visitor's chat on behalf of a random agent, a given agent (agent_id) or a random agent of a group (group_id). It reaches a real customer and cannot be unsent except by deleting it, so only call it with text the user asked you to send. Returns the new message with its id. POST /pushedMessages/.
chatra_send_message
WRITE: send a chat message to a visitor as a Chatra agent. The visitor sees it immediately in their chat window as if the agent typed it, so only call it with text the user asked you to send. It cannot be unsent except by deleting it. Say which agent writes: agent_id, or agent_email + agent_name + received_from (a dummy agent is created in Chatra when the email is unknown). For automated notices (order status, announcements) use chatra_push_message instead. Returns the new message with its id. POST /messages/.
chatra_update_visitor
WRITE: edit a visitor's basic info (name, email, phone, notes) exactly as if an agent edited it in the Chatra dashboard. Only the fields you pass change; `null` removes a value. Returns the updated visitor. PUT /clients/{id}.

Endpoints

URLTransportStateLatencyChecked
https://chatra.usefulapi.io/mcp streamable-http answering 172 ms 2 min ago

Alternatives to Chatra MCP by usefulapi

same job, measured the same way
Chaport MCP by usefulapi
by usefulapi

Read Chaport visitors, chats, operators and webhooks; update visitors and chats; message visitors.

14 tools answering
Vision6 MCP by usefulapi
by usefulapi

Read Vision6 lists, contacts, messages and reports; update contacts; send transactional email/SMS.

23 tools answering
Missive MCP by usefulapi
by usefulapi

Read email/chat conversations, messages, contacts and teams; draft, send and update threads.

19 tools answering
Teamup Calendar MCP by usefulapi
by usefulapi

Read and search Teamup Calendar events and sub-calendars; create, update, delete and undo events.

15 tools answering
OpenPhone MCP by usefulapi
by usefulapi

Send and read OpenPhone messages, calls, contacts and phone numbers.

16 tools answering
Cronitor MCP by usefulapi
by usefulapi

Manage Cronitor monitors and send telemetry pings — list, inspect, create, update, delete.

6 tools answering
Cronofy MCP by usefulapi
by usefulapi

MCP server for Cronofy — read calendars, events and free/busy, and create, update or delete events.

8 tools answering
FireText MCP by usefulapi
by usefulapi

Read FireText credit, messages and reports; send an SMS to up to 10 numbers; manage opt-outs.

13 tools answering

Chatra MCP by usefulapi — questions

Answers built from our own checks of this server.

What can Chatra MCP by usefulapi do?
It exposes 10 tools, read directly from the server on our last check. Among them: chatra_delete_message, chatra_delete_pushed_message, chatra_edit_message, chatra_edit_pushed_message, chatra_get_message, chatra_get_pushed_message and 4 more. The full list with descriptions is on this page — we take it from the server itself via tools/list, not from a README. How MCP servers expose tools in the first place →
Is Chatra MCP by usefulapi 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 344 ms. The bar chart above shows every period we have measured.
How do I connect Chatra MCP by usefulapi?
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.
Does Chatra MCP by usefulapi need an API key?
No. Chatra MCP by usefulapi completed a full MCP handshake with us as an anonymous client and listed its tools without asking for anything. All 10 of them are readable on this page. This is what we observed, not what the docs claim.
How fast is Chatra MCP by usefulapi?
It answers our handshake in 344 ms on average, which is faster than 46% of all working MCP servers we measure. The comparison comes from our own checks across the whole registry, every 15 minutes.
Is Chatra MCP by usefulapi open source?
The code is open source: it is published under the MIT licence, written in JavaScript, 0 stars on GitHub and 1 open issue. The licence covers the code in the repository, not the hosted service at chatra.usefulapi.io, which runs on its operator's own terms.