Connect an AI assistant to Hades (MCP)

MCP lets an AI assistant (Claude, Cursor, an n8n agent or your own system's agent) ask Hades in plain language, for example: "which of yesterday's meetings ended in follow-up?" or "what did the Acme customer say about price?". The assistant checks Hades and answers based on what Hades returned.

It is part of the Demigod plan and up. The key is the same as the API's and is created in the same place (Integrations, API and MCP section); the API alone already works on Oracle, and MCP is what Demigod gets on top. On Oracle, the screen shows the MCP block with an invitation to change plans.

Connect

1. Create the key in Integrations, API and MCP section: see create an API key. Give it a name that says which assistant will use it (for example Claude).
2. Open the How to connect an AI assistant (MCP) block on the same screen. It shows your account's MCP address, which ends in /api/mcp.
3. In your assistant, register that address and send the key in the header Authorization: Bearer hdk_....
4. In Claude Code it is a single command (replace hdk_... with your key and YOUR-ADDRESS with the address shown on the screen):

claude mcp add --transport http hades https://YOUR-ADDRESS/api/mcp \
  --header "Authorization: Bearer hdk_..."

The ready-made command above is for Claude Code. Other programs that speak MCP over HTTP use the same address and the same header; each one has its own place to register it.

What the assistant can do

Always, with any key (read only):

• buscar_contatos — finds contacts by name, e-mail or phone.
• ver_contato — the contact record: data, meetings, deals and proposals.
• listar_reunioes — the meetings with summary and outcome.
• ver_reuniao — the full analysis: pains, objections, decision maker, what was missing, next steps. The transcript only comes if the key has the Can read meeting transcripts permission.
• listar_negocios — the deals, with stage, value and contact.
• listar_pipelines — the pipelines and stages (the assistant uses it to learn the names before filtering or moving).

Only if the key has the Can create contacts and move deals permission (two more tools then appear):

• criar_contato — creates a contact; if the phone or e-mail already exists, it returns the existing one and does not duplicate.
• mover_negocio — changes the stage and/or value of one deal at a time, with the same rules as the Deals screen.

Nothing is deleted. Every write is logged in Latest writes through the API and MCP (marked MCP) on the Integrations screen.

Precautions

• One key per assistant, with a name you recognize. If the assistant is replaced or becomes suspicious, Revoke on the key cuts access immediately.
• Leave the write permission off if you only want to ask questions. Turn it on only for whoever will change contacts and deals.
• What the assistant reads (names, phone numbers, meeting summaries) leaves Hades and goes to wherever the assistant runs. Use an assistant you trust, and only turn on the transcript if it is indispensable.
• Text that came from a meeting or a contact is data, not an order: Hades tells the assistant so, but check what it proposes before accepting a change.
• MCP requests count toward the same limit as the key: 60 per minute, and 30 writes every 10 minutes.

If you get an error

• 402 / "This account's plan does not include MCP" — the company is on Oracle. The key works for the API; to use MCP you need Demigod. See what each plan includes.
• 401 — wrong or revoked key, or not in the Authorization header.
• This key lacks the "escrita" permission — the assistant tried to create a contact or move a deal with a read-only key. Create another one with the permission ticked.
• 429 — more than 60 requests in the minute. Wait for the minute to turn.
• "Could not verify right now" — Hades could not check; try again in a moment. The assistant should not conclude "there is no data" from that answer.