Connect Keypiece to Claude, Cursor, and ChatGPT

MCP is a controlled bridge between an AI app and Keypiece. You add one web address, sign in, then choose exactly which boards and actions that app may use.

AI connectors

MCP setup

Connect an AI app to selected Keypiece boards with OAuth. No API key copying is required.

What you need

You need a Keypiece account with access to at least one board and an AI app that supports remote MCP connectors. Keep this connector address handy:

https://www.keypiece.ai/mcp

The simple version

  • Add the Keypiece connector URL to your AI app.
  • A Keypiece sign-in window opens.
  • Choose the boards and permissions to share.
  • Return to the AI app and start asking it to work with Keypiece.

You do not need

  • A Keypiece API token pasted into the connector.
  • A local server running on your computer.
  • Access to every board in the workspace.
  • Developer experience for the Claude setup.

Recommended for non-technical users

Connect Claude

In Claude, a custom connector is the friendly name for a remote MCP connection. Menu labels may vary slightly between Claude plans.

  1. Open Claude and go to Settings → Connectors.
  2. Choose Add custom connector.
  3. Name it Keypiece and enter https://www.keypiece.ai/mcp.
  4. Choose Connect. Sign in to Keypiece when the browser window opens.
  5. Select the board or boards Claude may use, then choose view-only or write permissions.
  6. Return to Claude and confirm Keypiece is enabled for the conversation.

On Claude Team, a workspace Owner or Primary Owner may need to add the connector once before members can connect their own Keypiece accounts. That workspace approval is controlled by Claude, not Keypiece.

Connect Cursor

Cursor can use the same remote connector. Add this configuration to the project's .cursor/mcp.json, or to your personal Cursor MCP configuration if you want it available across projects:

{
  "mcpServers": {
    "keypiece": {
      "url": "https://www.keypiece.ai/mcp"
    }
  }
}
  1. Save the configuration, then open Cursor's MCP settings.
  2. Enable Keypiece and choose Connect or Authorize.
  3. Sign in to Keypiece, select boards, and approve only the permissions you want Cursor to have.
  4. Ask Cursor to list the authorized Keypiece boards before trying a write action.

Connect ChatGPT

ChatGPT calls MCP integrations custom apps or connectors. Availability, write support, and the exact menu labels depend on your plan and workspace settings.

  1. Open ChatGPT settings and find Apps or Connectors.
  2. If your plan offers custom apps, create one named Keypiece with https://www.keypiece.ai/mcp.
  3. Scan or refresh the available tools, then sign in with Keypiece when prompted.
  4. Select the permitted boards and scopes on the Keypiece consent screen.
  5. Enable the Keypiece app in a conversation and test with a read-only request first.

Business, Enterprise, or Education workspaces may require an administrator to enable developer mode, add the app, and publish it to members. Personal plan capabilities can be more limited.

Choose the smallest useful permission set

Every connection is tied to your Keypiece identity, selected boards, and approved scopes. The AI app does not inherit access to boards you did not select.

Start with view-only

  • boards:read — see authorized board details.
  • lists:read — see lists on those boards.
  • cards:read — read cards on those boards.
  • comments:read — read card discussions.

Add writes only when needed

  • cards:write — create, edit, move, or close cards.
  • comments:write — add or edit card comments.
  • Sensitive write actions remain subject to Keypiece safeguards and audit logging.
  • You can revoke the complete grant at any time.

Optional: turn external alerts into Keypiece cards

MCP is for interactive AI work. Inbound Issue Tracker webhooks solve a related automation problem: an error monitor, support form, or other service can send an event to Keypiece and create one incident report plus one linked Backlog card.

Good MCP flow

  • Ask Claude to summarize open cards.
  • Ask Cursor to create a card for a code change.
  • Ask an AI client to comment on an existing card.

Good webhook flow

  • Send a production error to Issue Tracker automatically.
  • Convert a support-form submission into a Backlog card.
  • Route a monitoring alert into the team's triage workflow.

Troubleshooting

No sign-in window

Allow pop-ups for the AI app and try Connect again. Make sure the URL begins with https://www.keypiece.ai/.

Connector unavailable

Your AI plan or workspace may require an owner to enable custom connectors first.

Board is missing

Confirm your Keypiece account can access the board, then reconnect and include it on the consent screen.

Writes are refused

The grant is probably view-only. Reconnect with the required write scopes, or keep the safer view-only setup.

Connection became stale

Disconnect the old grant in Keypiece and authorize a new one. Do not replace the production URL with a localhost address.

Disconnect or change access

Open Keypiece connection management, find the AI app, and revoke its grant. Revocation removes that app's access without changing your board membership or other connectors.