API keys and authentication
Atendia MCP uses your organization's API keys. Every request carries the key; the server checks it with the Atendia API and reads only what that key can read.
Create a key
- Open the Atendia console.
- Go to Settings → API keys.
- Choose «New API key», name it and choose its type: «Read only» or «Read and calls». Only an Owner or Administrator can create keys.
- Copy the key: you only see it once. Keep it somewhere safe, such as your password manager.
The two key types
- «Read only»: reads agents, calls, campaigns, numbers, tools, the knowledge base and widgets. It is enough for MCP.
- «Read and calls»: reads the same and, through the API, also asks for and cancels outbound calls. Over MCP it does the same as «Read only»: the MCP makes no calls.
For MCP, use a «Read only» key. Even so, whoever has the key can read your organization's data, including call transcripts. Keep it like a password and revoke it if you lose it.
How to send the key
Send the key with every MCP request, in the x-api-key header. The server also accepts Authorization: Bearer <key>.
Changing keys
- Create a new key in Settings → API keys. For MCP, «Read only» is enough.
- Put the new key in the client's configuration.
- Reconnect the client and check that you see the Atendia resources. A session opened with the old key does not answer the new one: the client opens a new session.
- Revoke the old key in Settings → API keys. From then on, it stops working.