Connect as yourself with OAuth, or as the whole workspace with an API key.
The MCP server accepts two kinds of credentials. The one you pick decides what the assistant can see.
OAuth
API key
Scope
The person who approved it
The whole workspace
Identity
Tied to a NeetoCal user
Tied to nobody
Set up by
Signing in to NeetoCal from the assistant
Pasting a key into a config file
Used by
Every client except Antigravity
Every client except Claude and ChatGPT
Reaches several workspaces
Yes, tick them while approving
No, one key is one workspace
Revoked by
Removing the connector
Revoking the key in workspace settings
In Claude Code, Codex, Cursor, Gemini CLI, VS Code, and Windsurf, leave the key out of the config to sign in with OAuth. Put the key in to use the API key. Both expose the same tools.
The assistant acts as the person who approved the connection. Lists and searches show only what that person can see. A meeting or booking they cannot open is refused.Use OAuth when a person drives the assistant. For the steps, see Connect agent.
The approval screen, with the scope picker and the workspace list.
If you leave a scope unticked, a tool that needs it is refused with a message that names the scope. For example, a read-only connection can list bookings but cannot book, reschedule, or cancel.One OAuth connection can reach several workspaces. Name the workspace in your prompt, or ask the assistant to list the workspaces it can reach. Every tool takes an optional workspace argument for this.
An API key is not tied to a person. Every tool call reaches the whole workspace, and role checks do not run. Use a key for automation that must see every booking. Do not use one on a machine where the person should see only their own bookings.The key is the same one the REST API uses. Put it in the server entry of the assistant’s config file:
A key belongs to one workspace. To reach two workspaces, add the server twice, with a different key and a different server name in each entry.
An API key gives access to every meeting and booking in the workspace. Treat it like a password: keep it out of shared config files and commits, and revoke it if it leaks.
