How it works
This is how a request travels between your AI client and Atendia.
Atendia MCP is a service of its own, hosted by Atendia. It stores no data: every read goes to the Atendia API with the key your client sends.
The path of a request
AI assistant → https://mcp.atendia.pt/mcp, with x-api-key
1. The server checks the key with the Atendia API and opens the session
2. Every read goes to the Atendia API (/api/v1) with the same key
3. The API answers with the key's permissions; the MCP returns the answerThe MCP server
Speaks Streamable HTTP with your client. Checks the key, keeps the session and closes it after 30 minutes without requests.
The Atendia API
Answers every read with your key's permissions. The MCP has no rules of its own: it only asks for what the key can read.
These docs
Explain the MCP and build the configuration block in your browser. They take no MCP requests.
Addresses
- MCP server (Streamable HTTP)
- https://
mcp.atendia.pt/ mcp - Server status
- https://
mcp.atendia.pt/ health
What the MCP does not do
It changes no data, opens no test conversations, makes or cancels no calls and buys no numbers. What no key can do does not appear in the MCP; the safety model lists each action, with the reason.