Connect Agents to Sidepins

Sidepins lets AI agents read, claim, reply to, triage, and resolve your comments.

Most users should connect Sidepins to Claude Code with MCP. It takes one API key and one terminal command.

1. Create an agent key

1. Open Sidepins.
2. Go to Settings -> Agents.
3. Create an agent key.
4. Copy the key. It starts with sp_.

Keep this key private. Do not commit it to git, paste it into shared config, or put it in project-level MCP settings.

2. Connect Claude Code

Run this in your terminal, replacing sp_... with the key you copied:

claude mcp add sidepins -s local -e SIDEPINS_API_KEY=sp_... -- npx -y sidepins-mcp

The -s local scope keeps the key on your machine instead of writing it into shared project config.

3. Verify the connection

Open Claude Code and run:

/mcp

You should see sidepins listed.

You can also check from the terminal:

claude mcp list
claude mcp get sidepins

4. Ask Claude to work

Use Sidepins to list my open comments and claim the next one.

Claude can now use Sidepins tools to read comments, claim work, reply, resolve, reopen, hand off, triage, release claims, renew leases, and set priority.

Other MCP clients

Use sidepins-mcp with any MCP client that can launch a stdio server.

If the client accepts JSON MCP config, add:

{
  "mcpServers": {
    "sidepins": {
      "command": "npx",
      "args": ["-y", "sidepins-mcp"],
      "env": {
        "SIDEPINS_API_KEY": "sp_..."
      }
    }
  }
}

If the client asks for a command instead:

SIDEPINS_API_KEY=sp_... npx -y sidepins-mcp

Use the CLI

Use sidepins-cli when you want to test setup or inspect comments from your terminal.

Set your key:

export SIDEPINS_API_KEY=sp_...

Run a health check:

npx -y sidepins-cli doctor

Useful commands:

npx -y sidepins-cli doctor
npx -y sidepins-cli mcp add claude
npx -y sidepins-cli mcp test
npx -y sidepins-cli inbox
npx -y sidepins-cli comments list --limit 10

If sidepins-cli is installed globally or linked locally, the package also exposes the sidepins command:

sidepins doctor
sidepins mcp add claude
sidepins mcp test
sidepins inbox
sidepins comments list --limit 10

sidepins mcp add claude uses Claude Code local scope by default.

Add the Sidepins review skill

Use sidepins-review-agent when your agent supports skills and you want it to follow Sidepins’ review workflow.

Install this public skill path:

Michael-Schwartz-is/sidepins-skills/sidepins-review-agent

Then ask your agent:

Use $sidepins-review-agent to handle my open Sidepins comments.

The skill does not replace MCP. Connect sidepins-mcp first; the skill tells the agent how to use it well.

Keep keys safe

• Do not commit SIDEPINS_API_KEY.
• Use Claude Code local scope: claude mcp add sidepins -s local ....
• Do not put keys in project-level MCP config unless everyone with repo access should have that key.
• If a key is exposed in chat, logs, screenshots, or git history, rotate it in Sidepins Settings.

Troubleshooting

Run the Sidepins doctor:

sidepins doctor

Smoke test MCP:

sidepins mcp test

If you use npx instead of installing the CLI:

npx -y sidepins-cli doctor
npx -y sidepins-cli mcp test

Check Claude Code MCP registration:

claude mcp list
claude mcp get sidepins

Inside Claude Code, run:

/mcp

If sidepins-mcp prints this and waits, that is expected:

Sidepins MCP server ready, waiting on stdio.

The MCP server is meant to be launched by an MCP client. Direct terminal runs are mostly useful as a quick environment check.

If auth fails:

• Confirm the key starts with sp_.
• Confirm the key is in the MCP client's environment, not only your interactive shell.
• Create a fresh key in Sidepins Settings if you are unsure whether the old one was copied correctly.
• Rotate the key if it may have been exposed.