Sidebox documentation
Connect Sidebox to Cursor
Add the Sidebox HTTP server to Cursor’s MCP configuration, then let Cursor open OAuth for your Sidebox account.
Before you start
Use a current Cursor version. You can add the server from Customize → MCPs or configure it for one project or globally.
Add Sidebox
- Open Customize in the sidebar, choose MCPs, and add a server, or edit .cursor/mcp.json in the current project (shown below).
- Save the configuration. Cursor opens the Sidebox sign-in flow when it connects; review and approve read-only workspace access.
- Confirm the Sidebox tools appear as available, then ask the verification prompt in Agent chat.
{
"mcpServers": {
"sidebox": {
"url": "https://sidebox.dev/api/mcp"
}
}
}Review the Sidebox consent
Sidebox uses OAuth with automatic client registration (DCR); do not provide an OAuth client ID or client secret. The MCP client handles the browser redirect and registration steps.
The browser sign-in opens Sidebox’s consent page. Review the client name and the read-only access to all current and future owned projects, including archived projects, then approve if that access fits your use. The connection can read stored private workspace context and cached data within your plan’s history allowances. It cannot edit projects or trigger provider refreshes, rank checks, or paid SEO research.
Verify the connection
Ask: “Review revenue, traffic and deployments using available data.” The response should retain source identity and mark unknown or unavailable values clearly.
Revoke or remove Sidebox
In Sidebox, open Account → MCP connection and revoke the Cursor connection. Remove the entry from .cursor/mcp.json or Cursor settings to remove it from the client.
Revoking in Sidebox blocks future tool reads for that connection. The client may still retain results already returned in its conversation history.
Troubleshooting
- Check that the JSON is valid and the server URL includes /api/mcp, then restart Cursor.
- If Sidebox does not appear in Agent tools, enable it under Customize → MCPs and restart the current chat.
- If OAuth fails, remove the old Sidebox authorization, reload Cursor, and connect again.
For shared endpoint, permission, data freshness, and limit details, see the MCP overview.
Client controls can change. Check the current Cursor Docs: MCP integrations if a menu or OAuth step differs.