Connect Keypiece to Claude, Codex, Cursor, and ChatGPT

What you need

You need a Keypiece account and an AI app that supports remote MCP connectors. Selected-board access needs an existing board; account access can create your first organisation and board with the appropriate permissions. Keep this connector address handy:

https://www.keypiece.ai/mcp

Set up a class or module

Selected boards remains the default. Choose selected organisations to include their future boards, or explicitly choose account access to include all boards you can access now or later. Existing connections keep their original permissions until you reconnect. Membership and role permissions are checked on every request.

1. Confirm the signed-in account and approve the permissions needed for your setup.
2. Create an organisation, then create or duplicate a board for each team. Set each board's emoji and colour.
3. Prepare Knowledge documents, tasks, labels, deadlines and team channels.
4. Configure an onboarding form and optional team-board routing. Create invitation links with the intended role, expiry and usage limit. Creating a link does not send it.
5. Use the module overview to review teams' progress, blockers and work awaiting feedback. Large results explicitly report their limits.

The connector also supports card transfers, files up to 2 MiB, calendar events and stand-ups. Board templates copy project content with fresh task progress; team memberships, private attachments, comments and agent execution history stay with the original board. Team routing applies to newly created MCP invitation links.

For agentic AI harnesses

First-run playbook

Keypiece returns usage instructions during the MCP handshake. An agent should follow this sequence before it changes shared work:

1. Call keypiece_connection_status to confirm the OAuth grant.
2. Call keypiece_conventions to load the workspace's agent-owned card rules.
3. Call list_boards and use only discovered board, list, card, member, and label IDs.
4. Read before writing. Use the latest revision and a unique idempotency key for each write intent.
5. Put a concrete checklist on agent-owned cards, update it progressively, and leave progress comments for humans.

Start with view-only access. If the task needs writes, ask the person to grant the smallest additional scopes through Keypiece OAuth; never ask them to paste an API token into the agent.

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 Codex

A user-level Codex MCP entry is shared by the desktop app, CLI, and IDE extension, so you only need to add Keypiece once on a computer.

codex mcp add keypiece --url https://www.keypiece.ai/mcp
codex mcp login keypiece

1. Run the two commands above, or add a Streamable HTTP server named Keypiece from Codex MCP settings.
2. Complete the browser sign-in, then select the boards and permissions Codex may use.
3. Restart Codex so new sessions load the connected tools.
4. Call keypiece_connection_status, then keypiece_conventions, then list_boards.

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.

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.

Troubleshooting

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.