The server lives at a single endpoint:

https://mcp.withkord.com/mcp

The first time your agent calls Kord, your MCP client opens a browser tab where you sign in with the Google or Microsoft account you already use for Kord and click Allow. That's the whole setup - the agent then acts with your permissions and nothing more.

What a connected agent can do

Read tools cover the full working context: list your teams and repositories, browse the file tree, read a file's version history, and inspect review sessions - files, reviewers, comments, markups - plus change requests and issues.

• Open a review session with changed files. An agent that edited documents on your machine can stage the files and open a review session in Kord, ready for your reviewers - instead of leaving changed files in a folder for you to upload by hand.
• Add files to an open review session - new files, or new revisions of files already under review.
• Link a cloud folder as a new repository - the agent equivalent of "Track folder from cloud", using a cloud connection you've already set up inside Kord.
• Answer questions about your project - "which review sessions are still waiting on me?", "what changed in the last revision of the vessel datasheet?", "which change requests are still open on this repository?"

Claude Code

Add the server from your terminal:

claude mcp add --transport http kord https://mcp.withkord.com/mcp

Then run /mcp inside Claude Code and pick kord to complete the browser sign-in. From then on Claude Code can browse your repositories and open review sessions directly.

Claude.ai and Claude Cowork

Kord connects to Claude.ai as a custom connector, which also makes it available in Claude Cowork sessions:

1. Open Settings → Connectors in Claude.ai.
2. Click Add custom connector and paste https://mcp.withkord.com/mcp.
3. Click Connect and complete the browser sign-in with your Kord account.

On a Claude Team or Enterprise plan, an organization owner adds the connector once under the organization's Connectors settings, and each member just clicks Connect.

Cursor, Windsurf, and other MCP clients

Any client that speaks MCP over HTTP works. In a JSON-configured client, add a server entry pointing at the URL (the exact key names vary slightly by client):

{
  "mcpServers": {
    "kord": { "type": "http", "url": "https://mcp.withkord.com/mcp" }
  }
}

Authentication and permissions

Authentication is OAuth 2.1 - the same standard your MCP client already uses for other connectors. There are no personal access tokens and no shared API keys: the sign-in mints a session tied to your Kord account, and every tool call runs under your exact access. An agent can only see the teams, repositories, and review sessions you can see, and its actions show up in the activity log under your name.

You can review and revoke connected agents at any time from your Kord settings.

Requirements

You need a Kord account, the connector signs in with it. If your team isn't on Kord yet, chat with us and we'll get you set up.

Unrelated to MCP: a machine-readable index of this site's pages for LLM crawlers lives at withkord.com/llms.txt.