Skip to main content

Cursor

Cursor supports MCP servers via its Tools & Integrations panel. This page shows the Infrahub MCP server configuration and notes specific to Cursor's tool-approval UX.

Quick start​

See the Installation guide for the minimal Cursor configuration snippet. This page covers Cursor-specific UX tuning beyond the basics.

Configure​

  1. Open Settings → Cursor Settings → Tools & Integrations.
  2. Under MCP tools, click Add Custom MCP.
  3. Paste the configuration below into mcp.json:
{
  "mcpServers": {
    "infrahub_mcp": {
      "command": "uvx",
      "args": ["infrahub-mcp"],
      "env": {
        "INFRAHUB_ADDRESS": "http://localhost:8000",
        "INFRAHUB_API_TOKEN": "your-api-token"
      }
    }
  }
}
  1. Save the file. Restart Cursor if prompted.

The server appears under MCP tools once Cursor starts it. Click the entry to expand tool/resource details.

Remote (HTTP) transport​

For a shared MCP server deployment:

{
  "mcpServers": {
    "infrahub_mcp": {
      "type": "streamable-http",
      "url": "http://localhost:8001/mcp"
    }
  }
}

Cursor's tool-approval model​

Cursor prompts the user before every tool call by default, which is useful during onboarding but noisy for chatty read-only flows. Two ways to tune this:

  • Auto-approve read tools — in Settings → MCP tools → infrahub_mcp, whitelist get_schema, get_nodes, search_nodes, query_graphql.
  • Keep manual approval for writes — leave node_upsert, node_delete, propose_changes, mutate_graphql on interactive approval so a human explicitly confirms each mutation. This matches Cursor's default for destructive actions.

For a server-side hard lock, set INFRAHUB_MCP_READ_ONLY=true and Cursor will only ever see read tools.

Workspace rules​

Add a Cursor rule (.cursor/rules/infrahub.mdc) to bake the agent workflow into Cursor's system prompt:

When the Infrahub MCP server is connected:

- Read infrahub://schema before guessing kind names
- Use get_nodes or search_nodes before query_graphql
- Always follow node_upsert / node_delete with propose_changes
- Ask before calling write tools even if auto-approve is on

Troubleshooting​

SymptomFix
Cursor shows Failed to start MCP serverCheck Cursor's MCP log (Output → MCP) for the exact stderr.
Tool descriptions look truncatedSome Cursor versions truncate MCP responses — upgrade to the latest.
$ref errors in tool schemasEnable INFRAHUB_MCP_DEREFERENCE_SCHEMAS=true to inline references.