A TypeScript implementation of a simple MCP server that exposes datetime information to agentic systems and chat REPLs
Nothing to run from here
Chatra MCP by usefulapi is installed from its publisher's own source and answers where it runs, so this marketplace is not in the path of a single call. There is no address here to send one to, and a panel that pretended otherwise would be showing you an answer we made up. Install it and call it from your own client — the Installation tab has the entry for each one.
10
tools declared
—
trust score
remote
at its publisher
—
calls last 7d
What it does
Read and update Chatra visitors; send, edit and delete chat and pushed messages.
Quickstart
# 1 — add it to Claude Code
claude mcp add --scope user --transport http chatra-mcp-by-usefulapi https://chatra.usefulapi.io/mcp
# 2 — ask your agent for something these tools do
# chatra_get_visitor, chatra_update_visitor, chatra_get_message and 7 more
Chatra MCP by usefulapi costs nothing on mcprush: there is no plan to choose here, no cap to set and nothing mcprush can bill you for.
Publishernot claimed
USAll 664 servers
usefulapi664 servers
25 categories
Collected from a public index. Nobody has claimed this account, so nothing here was written by its author — claim it if it is yours.
Installation
Where are you running it?
Every route below installs the same thing and ends at the same approval screen. Nothing here runs on your machine and nothing runs on ours: this server answers at its publisher’s own address, and what you install is the connection straight to it.
Claude Codedeclared by this listing
This is a public server: it answers at its publisher’s own address and this marketplace is not in the path. Claude Code registers it in one command; --scope user makes it available in every project. The transport below is http, as the publisher's own manifest declares it.
claude mcp add --scope user --transport http chatra-mcp-by-usefulapi https://chatra.usefulapi.io/mcpReconnect, or start a new session, and the tools appear in the model’s tool list.
Free on mcprush, and it answers at its publisher’s own address: this marketplace is not in the path, so there is no key of ours to hold and no card to add.
What it writes
One config entry pointing straight at the publisher’s own address — this marketplace is not in the path, and nothing from this listing executes on your machine.
What you approve
10 tools, with what each one reads, writes and reaches shown before you agree — the same list on every route above. Read the tool surface.
Tool surface
What the model actually sees. Descriptions are diffed on every release — see version history.
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 /
| Parameter | Type | Required | Notes |
|---|---|---|---|
| client_id | string | yes | Chatra visitor id: the clientId your website passed to the chat widget (ChatraSetup.clientId) or the visitor id from a Chatra webhook (client.id). |
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}.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| client_id | string | yes | Chatra visitor id: the clientId your website passed to the chat widget (ChatraSetup.clientId) or the visitor id from a Chatra webhook (client.id). |
| name | no | Visitor name; null removes it. | |
| no | Visitor email; null removes it. | ||
| phone | no | Visitor phone number; null removes it. | |
| notes | no | Agent notes about the visitor; null removes them. |
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}.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| message_id | string | yes | Chatra message id (from the reply of a send call or from a webhook). |
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 (
| Parameter | Type | Required | Notes |
|---|---|---|---|
| client_id | string | yes | Chatra visitor id: the clientId your website passed to the chat widget (ChatraSetup.clientId) or the visitor id from a Chatra webhook (client.id). |
| text | string | yes | Message text (plain text, 1-5000 characters). |
| agent_id | string | no | Chatra agent id (shown on the agent's page in Chatra). |
| agent_email | string | no | Agent email (instead of agent_id; needs agent_name and received_from). |
| agent_name | string | no | Agent display name (with agent_email). |
| received_from | string | no | Short name of the sending system, e.g. 'usefulapi-mcp'; marks the message in webhooks. |
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}.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| message_id | string | yes | Chatra message id (from the reply of a send call or from a webhook). |
| text | string | yes | Message text (plain text, 1-5000 characters). |
WRITE, IRREVERSIBLE: delete an agent message from the conversation. Only agents' messages can be deleted, not visitors'. Returns the deleted message. DELETE /messages/{id}.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| message_id | string | yes | Chatra message id (from the reply of a send call or from a webhook). |
One pushed (automated) message sent earlier by id: text, visitor id, agent id, timestamp (ms), isPushed. GET /pushedMessages/{id}.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| message_id | string | yes | Chatra message id (from the reply of a send call or from a webhook). |
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 se
| Parameter | Type | Required | Notes |
|---|---|---|---|
| client_id | string | yes | Chatra visitor id: the clientId your website passed to the chat widget (ChatraSetup.clientId) or the visitor id from a Chatra webhook (client.id). |
| text | string | yes | Message text (plain text, 1-5000 characters). |
| agent_id | string | no | Chatra agent id (shown on the agent's page in Chatra). |
| group_id | string | no | Chatra agent group id (on the group's page); a random agent of the group writes. |
WRITE: replace the text of a pushed message sent earlier; the visitor sees the edited text. Returns the updated message. PUT /pushedMessages/{id}.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| message_id | string | yes | Chatra message id (from the reply of a send call or from a webhook). |
| text | string | yes | Message text (plain text, 1-5000 characters). |
WRITE, IRREVERSIBLE: delete a pushed message sent earlier. Returns the deleted message. DELETE /pushedMessages/{id}.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| message_id | string | yes | Chatra message id (from the reply of a send call or from a webhook). |
Free
$0 forever
- Every tool — any call limit is its publisher’s, not ours
- No card, and mcprush charges nothing for it
- Runs at its publisher’s own address — this marketplace is not in the path
- Nothing to cap, because mcprush bills nothing
What counts against your monthly calls
| Tool | Unit | Calls used | Out of the allowance |
|---|
Nothing here is billable: mcprush charges nothing to install Chatra MCP by usefulapi or to call it, at any volume.
Call allowance · this installenforced at the gateway
Monthly allowance, in calls
—
—
Alert at 80% · then the tool returns a normal MCP error
Used this month: —
—Grade not published
No rule-by-rule report on file for this release
Two independent axes, because powerful and malicious are different questions. The grade is threat only. The capability level is blast radius, and it is never a penalty on the grade — it is priced as one subtract-only term in the score, where you can see it.
This server is graded from the tools it lists rather than from source code — each tool’s name, description, input schema and annotations, exactly as the server lists them. We have its list, and the grade appears here once the scanner has read it. Nothing on this tab is ever borrowed from another listing.
Release history
This is an address its publisher runs: which release it serves is theirs to choose, so there is nothing here to pin. The history below is for reading; the current release on file is 1.17.5.
1.17.5
undated
latestNo release note was published with this version.
—
no reviews yet
Who can review
One review per account, from a signed-in account that does not publish this listing. Nothing else is asked — you can say what you think before you install it. Publishers can reply once per review, and a review can be edited or deleted by whoever wrote it.
Sign in to write one
Any signed-in account that does not publish Chatra MCP by usefulapi can review it, once — before installing it or after. A review from an account that has installed it is marked as one.
No reviews yet
Nobody has reviewed this listing. The rating on the card is the mean of the reviews written here and nothing else, so there is no rating until somebody writes the first — which takes a signed-in account that does not publish it, and nothing else.