MCP server for terminal commands, file operations, and process management
Relaystation 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.
What it does
Pay-per-call agent infrastructure: file storage & handoff, compute tools, messaging, e-sign, KYC.
Quickstart
# 1 — add it to Claude Code
claude mcp add --scope user --transport http relaystation-mcp https://api.relaystation.ai/mcp
# 2 — ask your agent for something these tools do
# ask_operator, message_agent, create_agent_address and 11 more
Relaystation costs nothing on mcprush: there is no plan to choose here, no cap to set and nothing mcprush can bill you for.
Collected from a public index. Nobody has claimed this account, so nothing here was written by its author — claim it if it is yours.
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.
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 relaystation-mcp https://api.relaystation.ai/mcpReconnect, or start a new session, and the tools appear in the model’s tool list.
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.
14 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.
Send a question to the human operator via their Telegram and wait for their reply. Use when you need a decision, approval, or clarification you can't infer from the conversation. The operator gets a Telegram notification on their phone; their reply comes back to you here. Typical reply latency: 1-15 minutes when operator is away from desk; ~10 seconds when at-desk. Cost: $0.005 above the daily fre
| Parameter | Type | Required | Notes |
|---|---|---|---|
| message | string | yes | — |
| max_wait_seconds | integer | no | — |
| attached_baton_id | string | no | — |
Send a message to another Relaystation agent's ephemeral address (format <local_part>@courier.relaystation.ai). Same-Relaystation routing only (v2 launch); external domains return EXTERNAL_DOMAIN_NOT_SUPPORTED_V2. Free — agent-to-agent traffic has no per-message cost (subject to the recipient's per-address inbox quota; default 100 messages within the 30-day retention window). Use for multi-agent c
| Parameter | Type | Required | Notes |
|---|---|---|---|
| to_address | string | yes | — |
| body | string | yes | — |
| subject | string | no | — |
| attached_baton_id | string | no | — |
Mint a new ephemeral Relaystation address for this agent to receive messages from other agents. Returns a unique <local_part>@courier.relaystation.ai address tied to this agent's customer. Free up to the daily mint cap (default 10/day per customer); above-cap mints debit bridge.agent_address.over_cap_price_micros (default $0.001) via Pattern A. purpose_label is informational. ttl_seconds defaults
| Parameter | Type | Required | Notes |
|---|---|---|---|
| ttl_seconds | integer | no | — |
| purpose_label | string | no | — |
Create a baton — a prepaid storage object. Pick a preset (drop=store a file, pass=share a file, scratchpad=collaborate via append log, checkpoint=a single current document that each write REPLACES, ledger=hash-chained tamper-evident log) and optional tier, or supply a customShape. To collaborate on a document — human↔human, human↔agent or agent↔agent — use checkpoint: it holds one current st
| Parameter | Type | Required | Notes |
|---|---|---|---|
| preset | string | yes | — |
| tier | string | no | Bundle tier — valid tiers depend on preset (drop: femto/pico/nano/micro/standard/big · pass: femto/pico/nano · scratchpad: pico/nano/micro/standard/big · checkpoint: nano/micro/standard/big · ledger: |
| customShape | object | no | — |
| name | string | no | — |
| description | string | no | — |
| tags | array | no | — |
| content | string | no | — |
| contentType | string | no | — |
| contentEncoding | string | no | — |
| flags | object | no | — |
Read a baton's content + metadata. FREE (reads draw down the prepaid egress budget, no per-call charge). Address by owner id (requires your key) or by a collaborator token id (tok_…, the token IS the credential). Large multi-entry batons return a presigned download URL or a hint to page via list-entries; small content returns inline. Example: read_baton {id:"bat_<id>"}
| Parameter | Type | Required | Notes |
|---|---|---|---|
| id | string | yes | Baton id, or a collaborator token id (tok_…). |
Write to a baton — append (for append / append-chained presets) or overwrite (for single-object / checkpoint presets). FREE (consumes the prepaid writes budget; no per-call charge). Owner or editor/write-token only. Set overwrite=true to replace in full on overwrite-shaped batons. Example: append_to_baton {id:"bat_<id>", content:"<text or base64>"}
| Parameter | Type | Required | Notes |
|---|---|---|---|
| id | string | yes | Baton id, or a write-capable token id (tok_…). |
| content | string | yes | — |
| contentType | string | no | — |
| contentEncoding | string | no | — |
| overwrite | boolean | no | — |
| version_id | integer | no | Optimistic-lock guard for overwrite. |
Mint a collaborator token for a baton so another agent — or a human — can read and/or write without your key. FREE. type is read / write / read_write; optionally cap reads_allowed / writes_allowed, set an expiry, or restrict by IP. Up to 100 tokens per baton. Owner only. Returns the token id (tok_…) to share as the baton credential, plus an editUrl a human can open in a browser to read and edit
| Parameter | Type | Required | Notes |
|---|---|---|---|
| id | string | yes | — |
| type | string | yes | — |
| reads_allowed | integer | no | — |
| writes_allowed | integer | no | — |
| expires_at | string | no | — |
| require_fingerprint | boolean | no | — |
| ip_allow_list | array | no | — |
Your current Relaystation balance and available (post-hold) credit, plus account profile. Read-only, FREE. Requires your rs_live_* key (or wallet-JWT / MCP token); scoped to YOUR account only. Example: balance {}
No parameter schema on file.
Create a one-tap Stripe Checkout link to add credit to YOUR balance — hand it to a human to open and pay. NO money moves here (it returns a URL; the balance is credited when the human pays). Use when you hit insufficient balance. amountUsd is dollars (whole cents). FREE to call. Requires your rs_live_* key (or wallet-JWT / MCP token); not for x402 callers. Example: create_topup_link {amountUsd:1
| Parameter | Type | Required | Notes |
|---|---|---|---|
| amountUsd | number | yes | — |
| successUrl | string | no | — |
| cancelUrl | string | no | — |
Search the full Relaystation tool catalog by keyword and get back the best matches. Use this first to find a tool, then describe_tool for its schema and call_tool to run it (or call a named hot tool directly). query is free text (e.g. "merge pdf", "csv to json", "send telegram"). detail controls how much is returned per match: "name" | "summary" (default) | "full" (with inputSchema). `limi
| Parameter | Type | Required | Notes |
|---|---|---|---|
| query | string | yes | — |
| detail | string | no | — |
| limit | integer | no | — |
Get one tool's full description and input schema by exact name (as returned by search_tools). FREE. Example: describe_tool {name:'pdf_merge'}
| Parameter | Type | Required | Notes |
|---|---|---|---|
| name | string | yes | — |
Run a tool found via search_tools by name, passing its arguments. Dispatches the safe/billable utility tools (the cputools catalog + free reads/quotes) through the identical auth + billing + validation as a direct call. Consequential tools (account, money, credential, messaging — e.g. create_topup_link, create_baton, mint_token, ask_operator) are NOT dispatchable here: call them directly by name s
| Parameter | Type | Required | Notes |
|---|---|---|---|
| name | string | yes | — |
| arguments | object | no | — |
Create a binding-by-goodwill agreement between agents/parties and get back a contractId + termsHash + per-signer read tokens. The contract IS a hash-chained, auto-witnessed record (terms = entry 1, consents append after); it is tamper-evident and permanently verifiable, but it is NOT legally binding, NOT court-enforceable, and involves NO escrow or money movement — enforcement rests on the good fa
| Parameter | Type | Required | Notes |
|---|---|---|---|
| terms | string | yes | — |
| requiredSigners | array | yes | — |
| arbitration | boolean | no | — |
| signingWindowSeconds | integer | no | — |
Append your consent to a contract (one entry on its hash chain). FREE. Two forms, no cross-method satisfaction: a "wallet" signer supplies an EIP-712 ContractConsent signature over the contract's termsHash (the signature IS the authentication — no account needed); an "account" signer must be authenticated as the matching Relaystation customerId. When the LAST required signer signs, the contract be
| Parameter | Type | Required | Notes |
|---|---|---|---|
| id | string | yes | — |
| method | string | yes | — |
| walletAddress | string | no | — |
| signature | string | no | — |
- 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 Relaystation or to call it, at any volume.
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 listing is an address its publisher runs, and you connect to it directly — this marketplace is not in the path. The scanner reads packages and public source, and an address is neither. So there is no grade — not a withheld one, an unmeasured one.
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.0.0.
No release note was published with this version.
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.
Any signed-in account that does not publish Relaystation can review it, once — before installing it or after. A review from an account that has installed it is marked as one.
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.