Connecting Noibu MCP to Cursor

Last updated: October 14, 2026

This guide explains how to connect the Noibu MCP server to Cursor and use Noibu skills as Cursor Rules.

Prerequisites

  • Cursor installed.

  • Access to Noibu MCP.

  • The latest Noibu skills exported as Markdown files, if the internal MCP Platform Support Matrix does not yet include the newest skills.

Connect Noibu MCP to Cursor

  1. Open Cursor Settings with ⌘⇧J.

  2. Go to Tools & Integrations.

  3. Find the MCP section.

  4. Choose the manual JSON configuration option.

  5. Edit either the global Cursor MCP config at ~/.cursor/mcp.json or the workspace config at .cursor/mcp.json.

  6. Add the Noibu MCP server configuration:

{
  "mcpServers": {
    "noibu": {
      "url": "https://mcp.noibu.com/mcp"
    }
  }
}

Authenticate to Noibu

After adding the Noibu MCP server in Cursor, make sure the user authenticates to Noibu. If Cursor appears connected but tools are not working, confirm that authentication was completed after the plugin/server was added.

Port Noibu skills to Cursor Rules

Cursor Rules can be configured in two scopes: global User Rules or per-repository Project Rules.

A. User Rules (global, recommended for querying-noibu-data)

  1. Open Cursor Settings with ⌘⇧J, then go to Rules or Rules for AI.

  2. Source the rule content from ~/noibu/ai-plugin/src/skills/querying-noibu-data/SKILL.md after cloning the repo, or unzip noibu.zip and use skills/querying-noibu-data/SKILL.md.

  3. Paste the Markdown body into User Rules. Strip the --- frontmatter because Cursor ignores it.

  4. Save. Cursor injects the User Rules into every chat's system prompt.

B. Project Rules (per-repo)

  1. In the repo root, create .cursor/rules/querying-noibu-data.mdc with frontmatter containing description: ... and alwaysApply: true, then paste the body of skills/querying-noibu-data/SKILL.md.

  2. Repeat for other skills: tech-diagnosis.mdc, checkout-analysis.mdc, store-pulse.mdc, product-analysis.mdc, build-business-context.mdc, ab-test-opportunity-finder.mdc, accessibility-audit.mdc and segment-analysis.mdc. Use alwaysApply: false plus a clear description so Cursor auto-attaches each rule by intent.

  3. Commit the rules to the repo so teammates inherit them.

Recommended scope

  • querying-noibu-data: always on because it contains the routing core.

  • tech-diagnosis.mdc, checkout-analysis.mdc, store-pulse.mdc, product-analysis.mdc, build-business-context.mdc, ab-test-opportunity-finder.mdc, accessibility-audit.mdc and segment-analysis.mdc: optional and description-matched.

Verify the rules are loading

Ask Cursor chat: What tools should you use for conversion rate questions? The response should reflect the routing rules and point to the sessions tool, not errors. If the response is generic, the rule is not loading.

Troubleshooting checklist

  • Confirm the MCP JSON was added to the correct Cursor config file: global ~/.cursor/mcp.json or workspace .cursor/mcp.json.

  • Confirm the Noibu MCP URL is exactly https://mcp.noibu.com/mcp.

  • Restart or refresh Cursor if the MCP server does not appear after editing the JSON.

  • Confirm the user authenticated to Noibu after adding the MCP server.

  • Confirm the latest Noibu skills are available as Cursor Rules