Connect with sign-in
1
Add the server
Add it to You can also add it from Cursor’s MCP settings.
mcp.json. Use .cursor/mcp.json in a project, or ~/.cursor/mcp.json for all projects:mcp.json
2
Sign in
Cursor asks you to sign in on first use and opens your browser. Pick your workspaces, choose the access level and click Allow. You return to Cursor.
Connect with a key
Cursor expands${env:NAME} in url and headers, so the key stays out of the file:
mcp.json
SPYRO_AI_MCP_KEY in your environment, then restart Cursor. Cursor reads the file when it starts.
Check that it works
Open Cursor’s MCP settings and look for spyro-ai with a green status and its tool list. Then ask the agent: “Use Spyro AI to give me an overview of my workspace.”Try these prompts
- “Use Spyro AI to list my critical audit issues and fix the ones in this codebase.”
- “Which pages have a low click rate in Search Console? Rewrite their title tags.”
- “Audit this page’s URL with Spyro AI and add the missing schema markup.”
Tips
- Cursor asks you to approve tool calls by default. Keep that on for the nine
manage*tools. Spyro AI also asks you to confirm each change. - If you committed
mcp.json, use the${env:...}form so no one’s key is in the repo. - Cursor uses one fixed callback for all MCP sign-ins, which Spyro AI already allows. You do not need an OAuth client.
If it fails
- Server shows an error: restart Cursor after editing the file.
- 401 error: sign in again from the MCP settings, or check the key and that the variable is set.
- More: Troubleshooting.
