> ## Documentation Index
> Fetch the complete documentation index at: https://docs.codeant.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# MCP Server

> Use CodeAnt as an MCP server in any MCP-compatible client

The CodeAnt CLI is MCP-compatible — you can expose every CodeAnt command as a tool to any [Model Context Protocol](https://modelcontextprotocol.io) client (Claude Desktop, Cursor, Windsurf, VS Code, Zed, etc.) with a single command.

Under the hood we use [`any-cli-mcp-server`](https://github.com/eirikb/any-cli-mcp-server), which reads the CLI's `--help` output and turns each subcommand into an MCP tool. No extra configuration, no wrapper code — your AI assistant gets the same surface area as the CLI.

## Prerequisites

1. **CodeAnt CLI** installed and authenticated — follow the [CLI setup guide](/cli/setup)
2. **Node.js 18 or later** — required by `npx`

## Quick Start

Run CodeAnt as an MCP server:

```bash theme={null}
npx -y any-cli-mcp-server codeant
```

That's it — every CodeAnt command (`review`, `pr comments`, `pr resolve`, `pr list`, …) is now available as an MCP tool.

## Add to Your MCP Client

Drop this into your client's MCP config (for example, `~/.cursor/mcp.json`, `claude_desktop_config.json`, or `.vscode/mcp.json`):

```json theme={null}
{
  "mcpServers": {
    "codeant": {
      "command": "npx",
      "args": ["-y", "any-cli-mcp-server", "codeant"]
    }
  }
}
```

Restart your client and CodeAnt will appear as an available MCP server.

## Faster Startup (Recommended)

Building a cache once skips the `--help` introspection on every launch:

```bash theme={null}
# Build the cache
npx -y any-cli-mcp-server --cache-build codeant

# Point the MCP server at the cache
npx -y any-cli-mcp-server codeant_cache.json
```

Then reference the cache file in your MCP config. Use an **absolute path** — MCP clients launch the server from their own working directory, so a relative filename will not resolve:

```json theme={null}
{
  "mcpServers": {
    "codeant": {
      "command": "npx",
      "args": ["-y", "any-cli-mcp-server", "/absolute/path/to/codeant_cache.json"]
    }
  }
}
```

## What You Can Do

Once connected, ask your assistant things like:

* *"Run a CodeAnt review on my uncommitted changes."*
* *"List open PRs on this repo and fetch unresolved CodeAnt comments on #42."*
* *"Resolve the CodeAnt comments I just fixed."*

The assistant calls the matching CodeAnt CLI commands directly through MCP — same auth, same output, same behavior as running them in your terminal.

<Tip>
  For first-class Claude Code and Cursor integrations with curated slash commands and verdict-based fix flows, see [Claude Code](/cli/claude-code-integration) and [Cursor](/cli/cursor-integration). The MCP server is the right choice when you want raw CLI access from any other MCP client.
</Tip>