Cursor + Snipara

Use Cursor's native HTTP MCP support for agent chat, generated Cursor rules for project guidance, and the optional Snipara extension for editor commands and views.

Primary path

For LLM agents: use Hosted MCP

Cursor can connect directly to the Hosted MCP endpoint. No HTTP-to-stdio proxy package is required.

Recommended onboarding

npx -y create-snipara@latest init --client cursor

npx -y create-snipara@latest doctor --client cursor

The generator preserves an existing root instruction file, writes merge-ready material under .snipara/templates, and creates the Cursor rule only when it is missing. Review generated files before committing them.

Native Hosted MCP configuration

Add the server through Cursor's MCP settings or its current MCP JSON file. Store the API key in the local environment or Cursor's secret mechanism; never replace the variable reference below with a key in a committed file.

{
  "mcpServers": {
    "snipara": {
      "type": "http",
      "url": "https://api.snipara.com/mcp/YOUR_PROJECT_SLUG",
      "headers": {
        "X-API-Key": "${env:SNIPARA_API_KEY}"
      }
    }
  }
}

Cursor's configuration UI and file locations can change between releases. The stable contract is the native HTTP server entry, the project-scoped URL, and local secret-backed authentication.

Verify in Agent mode

Reload Cursor after saving the server.
Open Agent mode and confirm the Snipara server is enabled.
Ask Cursor to call snipara_context_query and verify that source references are returned.
For a structural question, use snipara_code_callers when the specialist Code Graph surface is available to the caller.

Optional editor extension

The public marketplace release is 2.0.8; repository source is currently2.0.9. Until 2.0.9 is published, treat the marketplace artifact as the user contract. Its current manifest exposes 64 commands, 38 language-model tools, and 6 views.

The extension adds editor UI and commands; it does not replace Hosted MCP for Cursor's coding agent. If an inventory differs, check the installed extension version before filing a documentation bug.

Troubleshooting

A 401 indicates a missing, invalid, or unauthorized local API key.
If tools do not appear, verify Agent mode, reload the MCP configuration, and inspect the native server entry.
Native HTTP is sufficient; do not add an HTTP-to-stdio npm proxy.