The MCP server uses the same API key as the REST API. Instead of adding a header to every request yourself, you save the key as a bearer token in your assistant’s MCP configuration.
Generating an API key
You need a NeetoCal API key before connecting an assistant. Learn how to generate one.
How MCP authenticates
NeetoCal hosts the MCP server at https://connect.neetocal.com/mcp/messages. Your assistant includes the API key in an Authorization header on every request:
Set this once in your assistant’s MCP configuration. Connect shows the right file and format for each assistant. Replace YOUR_API_KEY with your key, and the assistant sends the header for you.
Each NeetoCal surface authenticates differently:
Keep your key safe
Treat your API key like a password. Create a separate key for each workspace; a key only works in the workspace where you created it.
Your API key gives access to your workspace’s scheduling data. Anyone who can read your assistant’s configuration can use it. Do not commit it to a shared repository or paste it where others can see it.
When authentication fails
MCP does not expose a 401 error the way a direct API request does. A missing or invalid key usually looks like one of these problems:
- The
neetocal tools never appear in your assistant.
- A tool call fails, and the assistant reports it couldn’t reach NeetoCal.
Both usually mean the Authorization header is wrong: the key may be mistyped, belong to another workspace, or have been revoked. Verify or regenerate it in the API Keys article, then follow Troubleshooting. 