Cursor Admin MCP Server

Model Context Protocol server for Cursor Admin API - instant team analytics power-up for AI assistants. Monitor productivity, usage, and spending.

Local serverstdioTypeScript

What is the Cursor Admin MCP MCP server?

Cursor admin mcp mcp server lets Claude, Cursor and other MCP clients work with Cursor Admin MCP directly. Model Context Protocol server for Cursor Admin API - instant team analytics power-up for AI assistants. Monitor productivity, usage, and spending.

What Cursor Admin MCP does

Think of this as equipping your AI with X-ray vision for your development team:

Tools it exposes

Once connected, the assistant can call these 6 tools directly:

  • startDate — Start date in epoch milliseconds
  • endDate — End date in epoch milliseconds
  • Prerequisites — The Prerequisites tool exposed by this server
  • Setup — The Setup tool exposed by this server
  • Testing — The Testing tool exposed by this server
  • Building — The Building tool exposed by this server

Installing the cursor admin mcp mcp server

The server is distributed via npm as cursor-admin-mcp, so most clients can run it without a manual build step. Add it to your MCP client's configuration and restart the client to pick it up — the copy-paste configs for Claude Desktop, Claude Code and Cursor are on this page.

Configuration

Before the server will start you need to supply one environment variable: CURSOR_API_KEY. Keep credentials in your client's env block or a secrets manager rather than committing them.

Requirements

  • Node.js 16+ - A Cursor team admin API key (get it from your team settings)

Where it fits

Developer-tool servers are usually the first ones people connect, because they turn "help me with this code" into an assistant that can actually read the repo and act on it. Cursor Admin MCP sits in that group, and the shape of its toolset — startDate, endDate, Prerequisites among others — tells you what it is really for. Worth comparing against the other developer tools servers in this directory before you commit to one, since several overlap in scope but differ sharply in setup cost and permissions.

Practical notes

  • This server runs locally, so it operates with whatever access your machine and its credentials already have. Scope that deliberately rather than by default.
  • It will not start until its required credentials are present, so set those before wondering why the tools never appear.
  • Maintained by h3ro-dev, written in TypeScript.
  • MCP clients ask for confirmation before each tool call by default. Keep that on while you learn what the cursor admin mcp mcp server actually does with your data.
  • Every entry in this directory is reviewed by hand before it goes live, and details are checked against the project's own documentation.

Available tools

ToolWhat it does
startDateStart date in epoch milliseconds
endDateEnd date in epoch milliseconds
PrerequisitesThe Prerequisites tool exposed by this server.
SetupThe Setup tool exposed by this server.
TestingThe Testing tool exposed by this server.
BuildingThe Building tool exposed by this server.

How to install the Cursor Admin MCP MCP server

{
  "mcpServers": {
    "cursor-admin": {
      "command": "npx",
      "args": ["-y", "cursor-admin-mcp"],
      "env": {
        "CURSOR_API_KEY": "your-value"
      }
    }
  }
}

Add to claude_desktop_config.json, then restart Claude Desktop.

Configuration

  • Node.js 16+ - A Cursor team admin API key (get it from your team settings)
VariableDescriptionRequired
CURSOR_API_KEYCredential the server authenticates with.Yes

Example prompts to try

  • Use Cursor Admin MCP to startDate.
  • Use Cursor Admin MCP to endDate.
  • Use Cursor Admin MCP to Prerequisites.

Frequently asked questions

It connects Cursor Admin MCP to MCP-compatible AI assistants such as Claude and Cursor, exposing 6 tools (startDate, endDate, Prerequisites, and more) that the assistant can call on your behalf. Instead of copying data back and forth by hand, the assistant works with Cursor Admin MCP directly.