MCP server

Kliff runs a Model Context Protocol server. Connect an AI client to it, and the client can list your repositories, start runs, and work with agents in your organization, as you.

Server URL

https://kliff.dev/mcp

You sign in through your browser the first time a client connects. There is no API key to copy.

Cursor

Or add the server to ~/.cursor/mcp.json for every project, or to .cursor/mcp.json in one project:

{
  "mcpServers": {
    "kliff": {
      "url": "https://kliff.dev/mcp"
    }
  }
}

Then open the MCP settings in Cursor, connect kliff, and sign in.

Claude Code

claude mcp add --transport http kliff https://kliff.dev/mcp

Then run /mcp in Claude Code, choose kliff, and sign in.

VS Code

{
  "servers": {
    "kliff": {
      "type": "http",
      "url": "https://kliff.dev/mcp"
    }
  }
}

VS Code asks you to sign in when it starts the server.

Signing in

When a client connects, your browser opens Kliff. Sign in, choose the organization the client works in, and select Allow.

The client acts as you in that organization only. It sees what you can see there, and the runs it starts work within your GitHub permissions. If you leave the organization, the client stops working in it. To use another organization, disconnect the client and connect it again.

Tools

• list_repos: Lists the repositories connected to your organization, and the projects that group them.
• list_runs: Lists runs, newest first.
• get_run: Shows one run: whether it is working, done, or failed, its branch, and the pull request it opened.
• create_run: Starts a run on a repository. It either works on a prompt in a new branch and opens a draft pull request, or reviews an open pull request.
• list_agents: Lists agents, most recently active first.
• get_agent: Shows an agent and its latest steps: messages, tool calls, and replies.
• create_agent: Starts an agent on a repository or a project, with its first message.
• send_agent_message: Sends an agent its next message.
• stop_agent: Stops the agent's turn in progress. The agent keeps its conversation.
• archive_agent: Stops an agent and hides it from the organization. Only the agent's creator, an owner, or an admin can archive it.

Your client asks before it calls a tool, unless you let it run tools on its own.

Turning it off

Owners and admins can turn the server off for an organization in Automations, under Nexus MCP. While it is off, clients can still read runs and agents, but cannot start runs or start, message, stop, or archive agents.

Runs started from a client are listed under Nexus MCP in Automations.

Troubleshooting

A tool says an admin turned Nexus MCP off. Ask an owner or admin of the organization to turn on Nexus MCP in Automations. Reading still works while it is off.

The client cannot find a repository. The client only sees the organization you allowed it in. Connect the repository to that organization in Kliff, or disconnect the client and connect it again to choose another organization.

The client asks you to sign in again. Connect it again from the client's MCP settings and sign in.