SideButton
Claude Connector

SideButton for Claude — Agent Fleet Dispatch

Turn any Claude conversation into a dispatch console for your SideButton agent fleet. Ask Claude to run an SE or QA workflow on a Jira ticket, and an agent VM picks it up, does the work, and reports back.

What this connector does

The SideButton cloud MCP adds seven tools to Claude for orchestrating your agent fleet:

  • See the fleet — list agents, their active jobs, and Claude Code session status.
  • Check one agent — detailed health, browser connection, system metrics.
  • Dispatch a job — send a workflow (e.g. se-work, qa-validate) to a named agent.
  • Queue a batch — queue several Jira tickets at once for a single workflow.
  • Run or queue a named workflow — for ad-hoc work outside the standard agent-role set.

Agents run on Linux VMs you provision through your SideButton account. Each agent has its own Claude Code session, browser, and installed knowledge packs. The cloud MCP just gives Claude a remote control for the fleet — the actual work happens on the agent VM.

Requirements

  • A SideButton cloud account. Sign in at sidebutton.com/portal.
  • At least one provisioned agent VM visible in your portal's Agents tab.
  • Workflows configured for your agents (SE, QA, PM — or custom).
  • A Claude client that supports custom connectors (Claude.ai, Claude Code, Claude Desktop).

Set up the connector

1. Add the connector in Claude

In Claude settings, go to Connectors → Add custom connector and enter: 

https://sidebutton.com/mcp/sse

2. Sign in

Claude will open an OAuth 2.1 flow. You will be redirected to SideButton, then to our identity provider (Auth0) to sign in with your SideButton account. After consent, Claude stores an access token scoped to your account.

3. Verify

In your next Claude message, try:

List my SideButton agents and show their status.

Claude will call list_agents and report back. If you see your fleet, you're ready to dispatch work.

Tools reference

Tool Type Purpose
list_agentsread-onlyList all agents with status, session count, active job.
list_workflowsread-onlyList workflows available to your account.
get_agent_statusread-onlyDetailed status of one agent: health, browser, sessions, metrics.
dispatch_agent_jobwriteSend a workflow to a named agent VM. Returns a job ID.
queue_jobswriteQueue one or more tickets for a workflow across the fleet.
run_workflowwriteRun a named workflow immediately (dispatch now).
queue_workflowwriteAdd a named workflow to the dispatch queue.

Every tool declares its type to Claude (readOnlyHint or destructiveHint) so Claude can ask for confirmation before dispatching work. Tool names are under 64 characters; no tool mixes read and write operations.

Example prompts

  • Dispatch a single job:
    Run se-work for SCRUM-142 on agent 5 with high effort.
  • Queue a batch:
    QA-validate SCRUM-120, 121, and 122. Use max effort.
  • Check fleet health before dispatching:
    Which of my agents is free right now? Send the next ticket there.
  • Run an ad-hoc workflow:
    Run nightly-backup on agent-11 now.

Security & privacy

  • OAuth 2.1 — authorization code flow with PKCE (S256), Dynamic Client Registration per RFC 7591.
  • Metadata — RFC 8414 and RFC 9728 discovery documents at /.well-known/oauth-authorization-server and /.well-known/oauth-protected-resource.
  • Origin validation — MCP endpoints reject requests from unknown browser origins (DNS-rebinding protection).
  • Scope — the connector only sees your account. No cross-tenant access.
  • Data — details in our Privacy Policy, section 2.5 (Cloud Services).
  • Revocation — remove the connector from Claude settings, or revoke its token from the portal's Settings page.

Troubleshooting

HTTP 401 on tool calls

Your OAuth token expired or was revoked. Reconnect the connector in Claude.

HTTP 403 "forbidden_origin"

Your client is sending an Origin header we don't recognize. Allowed origins are claude.ai, claude.com, sidebutton.com, and loopback. Non-browser clients (Claude Code, curl) usually send no Origin header and pass through.

Agent is offline

Open the portal's Agents page to see agent health. An offline agent cannot be dispatched to — try another agent, or check the VM from the portal.

"Workflow not found"

Workflow IDs are case-sensitive and must match what your account has installed. Call list_workflows first to see the exact names.

More resources