MCP Integration

Sidenote ships a Model Context Protocol (MCP) server that lets AI agents upload documents, read reviewer feedback, and push updated versions — all without a human at the API layer.

This guide shows you how to connect your MCP-compatible agent to Sidenote and run a full human-in-the-loop review cycle.

Requirements

• Plan: MCP and API access are included on every plan, including Free, and are not metered. Inference runs on your own agent, so we don't charge for the connection. Creating, editing and publishing brand specs over MCP requires a paid plan; reading them does not.
• Auth: Agents authenticate via OAuth 2.1 with PKCE, which most clients handle for you. API keys are also supported for machine-to-machine use — create one from your dashboard and send it as a Bearer token.
• Endpoint: MCP server URL: https://sidenote.ink/api/mcp
• Protocol: JSON-RPC 2.0 over HTTP POST with Bearer token authentication. A fair-use rate limit protects the service from runaway request loops; normal agent work will not reach it.

Connecting your MCP client

Most MCP-compatible clients (Claude Desktop, Cursor, Windsurf, and custom agents) handle the OAuth flow automatically once you point them at the Sidenote MCP URL.

Add Sidenote to your MCP client configuration:

{
  "mcpServers": {
    "sidenote": {
      "type": "http",
      "url": "https://www.sidenote.ink/api/mcp"
    }
  }
}

On first connection, your client will:

1. Open a browser window.
2. Ask you to sign in to Sidenote.
3. Request authorization for the agent.

After that, access and refresh tokens are managed automatically by the client.

If your client needs the full OAuth discovery URL, use:

• OAuth metadata: https://sidenote.ink/.well-known/oauth-authorization-server

Available MCP tools

Once connected, your agent can call these tools over MCP.