Protocols

MCP — the agent's tools

What tools a Ghosty agent has, how they are named and how they reach each engine through the Model Context Protocol.

Updated 2026-10-03

The agent's tools arrive over MCP (Model Context Protocol). They are the same for every engine: a new tool on the platform is seen by any agent without touching its machine.

Where they come from

Source	Examples	Who provides them
The machine	read and write files, terminal, `pdf-reader`, PDF rendering, TTS	The engine, inside the machine.
The platform	`programar_seguimiento` (schedule a follow-up: a future turn), `enviar_correo` (send email), web search	Studio, per turn, on every channel (chat, apps, WhatsApp, Messenger).
The Teams workspace	documents, forms, reminders, email, memory, brand, prospecting	Teams, with a 5-minute credential per turn.
Your connectors	Gmail, Calendar, Drive, GitHub, Odoo…	On your behalf; see .

How they are named

Inside the model each tool carries its MCP server's prefix: ghosty__doc_read, ghosty__form_create, ghosty__reminder_create. If you tell the agent "use doc_read" it finds it anyway: the prefix belongs to the transport, not the name.

Families in Teams: chat_*, doc_*, form_*, reminder_*, email_send, memory_*, brand_*, prospect_*.

Agent email

enviar_correo exists on every channel and engine. In Teams the agent uses email_send, its workspace's tool.

Sender: Ghosty's address with the agent's name. Replies go to the owner (or to responder_a, if someone on the team sets it).
Attachments: account files by their archivo:<id> id or files from the agent's workspace (adjuntos_contenido); up to 5 and 7 MB in total.
Cap: 50 emails a day per agent; each recipient counts as one.
Customer channels: only to the address of the person writing. The owner opens it to any address in the agent page's Advanced section or with PATCH /api/v2/agents/:id { "email": { "anyFromClients": true } }.
Every send is logged: recipient, subject, channel and attachments.

Scope per channel

Scope is decided by the turn, not the agent:

DM or private channel: all the workspace's tools and the invoker's connectors.
Public channel (WhatsApp): no personal connectors and no destructive actions; the agent can escalate to a person.
Editor over ACP: the machine's tools plus the workspace's if the agent is activated in one.

An agent can only do what the person who invoked it could do.

Permissions

Some actions ask for confirmation (deleting, sending to third parties). The client receives a permission event with options and answers; if nobody answers within ten minutes it is denied. See .

Bring your own MCP servers

With the you give your agent its own MCP servers (http or stdio). The list is replaced whole and the agent restarts:

bash

curl -X PUT https://www.ghosty.studio/api/v2/agents/$GHOSTY_AGENT_ID/mcp \  -H "Authorization: Bearer $GHOSTY_AGENT_TOKEN" -H "Content-Type: application/json" \  -d '{"servers":[    {"name":"notion","type":"http","url":"https://mcp.notion.com/mcp","headers":{"Authorization":"Bearer …"}},    {"name":"fs","command":"npx","args":["-y","@modelcontextprotocol/server-filesystem","/data/work"]}  ]}'

curl -X PUT https://www.ghosty.studio/api/v2/agents/$GHOSTY_AGENT_ID/mcp \  -H "Authorization: Bearer $GHOSTY_AGENT_TOKEN" -H "Content-Type: application/json" \  -d '{"servers":[    {"name":"notion","type":"http","url":"https://mcp.notion.com/mcp","headers":{"Authorization":"Bearer …"}},    {"name":"fs","command":"npx","args":["-y","@modelcontextprotocol/server-filesystem","/data/work"]}  ]}'

Only on engines with their own machine (Ghosty · Lite and Goose). A stdio server needs the binary to exist on the machine (Node and Python are there).

← Previous

A2A — agent to agent

Documentation MCP