Claude Code (MCP)

Syncupp speaks the Model Context Protocol, so Claude Code can read and update your workspace directly — ask it what is overdue, have it create a task, or summarise a board.

To be clear about what this is: it is an MCP endpoint rather than a general REST API.

Connecting

1. In Syncupp, go to Settings → Integrations → Claude Code (MCP).
2. Create a key. Choose read or read & write, and an expiry.
3. The screen shows a ready-to-paste claude mcp add command with the key already filled in. Run it in your terminal.

The key is shown once. Keys start with sup_mcp_, which makes them easy to spot in a secret scanner.

Endpoint and authentication

If you are wiring up a client by hand rather than using the generated command:

POST https://api.syncupp.com/api/v1/mcp

# Either header works:
Authorization: Bearer sup_mcp_xxxxxxxxxxxxxxxx
x-api-key: sup_mcp_xxxxxxxxxxxxxxxx

The key identifies both the user and the workspace, so there is nothing else to pass. A request beyond the key's scope — a write with a read-only key — is refused.

Operations

Keys, scopes and expiry

• Read-only by default. A key is a long-lived credential handed to a model; the damage a misunderstood instruction can do is far smaller when nothing can be written. Granting write is a deliberate choice per key.
• Expiry. New keys default to 90 days and can be set up to 365, or to never expire for CI-style use. A key with an expiry limits how long a leak is useful without anyone having to notice it.
• Revoking. Revoke a key in Settings and it stops working immediately. Revoked keys are kept rather than erased, so the record of what existed survives.
• Scoped to you. A key acts as the person who made it and sees only what they can see.

On REST

There is no general-purpose REST API today. Rather than describe this as one, we would rather point you at what exists: MCP for reading and updating a workspace programmatically, and webhooks for hearing about changes as they happen. A documented REST API is on the roadmap.