Set up per workspace, billed per organization
MCP access is configured per workspace, not per organization:- A key belongs to one workspace, and you create it under that workspace’s Settings → MCP. Each workspace can have up to 5 keys.
- A sign-in connection can cover several workspaces in one approval, but each workspace gets its own access level and daily credit limit, and you can revoke each one separately.
- OAuth clients belong to you and work in every workspace where you are an admin.
Who can set up MCP
You need to be an admin of the workspace to create keys, approve app connections, see connected apps and revoke access.
A key or app connection keeps working only while the person who created it is still a workspace admin. If their role is removed or lowered, their keys and apps stop working. Credits are always spent from the organization’s pool. See Team members to change roles.
The page has four parts:
- Server URL - the address to paste into your AI app, with a Copy button.
- MCP keys - keys for tools that send a header.
- Connected apps - apps that signed in with their own approval.
- OAuth clients - an advanced option for a few enterprise apps.
Create a key
1
Open Create MCP key
Under MCP keys, click Create MCP key. You can have up to 5 keys per workspace.
2
Name it
Name the key after the app that will use it (for example Claude Code laptop), so you can revoke the right one later. Up to 60 characters.
3
Choose what it can do
- Read reads your site data and runs research.
- Read + actions can also change your calendar, articles, publishing, AI prompts, keywords, audits, internal links, competitors and settings. You confirm each change in Spyro AI.
4
Set a daily credit cap
Default is 500 credits per day, from 50 to 10,000. See Credits and limits.
5
Copy the key
Click Create key, then copy the key right away. It starts with
sk_mcp_ and is shown only once.Revoke a key
Click the revoke icon on the key, then Revoke key. Any app still using it stops working at once and gets a 401 error. This cannot be undone, so create a new key if you need one later. A key also stops working if its creator is no longer an admin of the workspace, or the workspace is deleted.Connect an app by signing in
When an app opens the Spyro AI sign-in page, the Connect an app to Spyro AI screen shows:- The app’s name, marked Verified or Unverified. Spyro AI verifies a few well-known web apps: claude.ai, ChatGPT, Perplexity and Cursor’s web agents. Apps running on your own computer (Claude Code, Cursor, VS Code, Codex, Gemini CLI and others), Gemini, and any app Spyro AI has not verified show a warning. That is expected. Only continue if you started the connection yourself.
- Workspaces it can use. Pick one or more. A workspace is greyed out if you are not its admin, its plan does not include MCP, or its subscription is not active.
- What it can do. Read your data, or Read and take actions. With actions, you still confirm each change in Spyro AI before it runs.
- Daily credit limit per workspace. Default 500, from 50 to 10,000.
See and revoke connected apps
Connected apps lists each app with who connected it, its access, when it connected, when it was last used and the credits it used this month. Click revoke to disconnect it from this workspace right away. To use it again, connect it again from the app.OAuth clients (advanced)
Most apps connect with sign-in alone. Create an OAuth client only when an app asks for a client ID and secret, such as Gemini Enterprise.1
Open OAuth clients
On Settings → MCP, expand OAuth clients and click Create OAuth client.
2
Enter the details
Give it a name (it can’t contain “Spyro”) and one redirect URI per line, using the values your app gives you. Use
https URLs, or http only for localhost, 127.0.0.1 or [::1].3
Copy the client ID and secret
The secret is shown once. Clients belong to you and work in every workspace you manage.
Security checklist
- Use sign-in whenever your app supports it, because it needs no secret in a file.
- Choose Read unless the app really needs to make changes.
- Read each confirmation summary before you click Confirm.
- Keep the daily cap low for new connections, then raise it if you need.
- Use one key per app so you can revoke it alone.
- Revoke connections you no longer use, and check Last used now and then.
- If a key leaks, revoke it and create a new one.
