OCIP Graph MCP

Node.js Model Context Protocol server that calls your OCIP backend with an API key (Authorization: Api-Key …) so editors (Cursor, Claude Desktop, Windsurf, etc.) can query Neo4j graph data: modules, models, search, subgraphs, and impact helpers.

Prerequisites

1. Create an API key in the OCIP Dashboard (API keys section).
2. Use read-only for safe graph queries, or read-write only if tools should trigger parse jobs via HTTP (this MCP package does not expose parse by default).

Install

cd ocip-mcp
npm install
npm run build

Environment

| Variable | Required | Example | |----------------|----------|----------------------------------| | OCIP_API_KEY | yes | ocip_live_… from dashboard | | OCIP_API_BASE| no | http://127.0.0.1:18000/api |

Cursor / Claude Desktop

Add an MCP server entry pointing at the built file. The args path must be the ocip-mcp package folder on disk, then dist/index.js — for example if the repo root is ~/work/ocip, use ~/work/ocip/ocip-mcp/dist/index.js (do not repeat ocip/ocip-mcp inside ocip-mcp).

{
  "mcpServers": {
    "ocip": {
      "command": "npx",
      "args": ["-y", "ocip-graph-mcp@latest"],
      "env": {
        "OCIP_API_KEY": "ocip_live_your_key_here",
        "OCIP_API_BASE": "http://127.0.0.1:18000/api"
      }
    }
  }
}

Adjust OCIP_API_BASE if your API is on another host (e.g. production).

spawn node ENOENT (Cursor cannot find Node)

The IDE often runs MCP with a minimal PATH, so node is missing even though it works in Terminal.

1. Use the full path to Node (run which node in Terminal and paste it as command):

   • Apple Silicon Homebrew: often /opt/homebrew/bin/node
   • Intel Homebrew: often /usr/local/bin/node
   • nvm: e.g. $HOME/.nvm/versions/node/v22.14.0/bin/node

   "command": "/opt/homebrew/bin/node",
   "args": ["/Users/you/work/ocip/ocip-mcp/dist/index.js"]

2. Or use a login shell so your shell profile (nvm, fnm, etc.) sets PATH:

   "command": "bash",
   "args": ["-lc", "node /Users/you/work/ocip/ocip-mcp/dist/index.js"],
   "env": { "OCIP_API_KEY": "...", "OCIP_API_BASE": "..." }

3. Confirm the server file exists after npm run build: ocip-mcp/dist/index.js.

Cannot find module '.../dist/index.js' (wrong path)

Node is running, but the file path in args is wrong. Check in Terminal:

ls /path/you/used/in/mcp/config/dist/index.js

• Correct (typical clone layout): /Users/you/work/ocip/ocip-mcp/dist/index.js
• Wrong (extra nested segment): .../ocip-mcp/ocip/ocip-mcp/dist/index.js — that folder usually does not exist.

Tools exposed

• ocip_list_projects
• ocip_graph_search — project_id, q
• ocip_list_modules — project_id, optional version
• ocip_get_module — project_id, module_name
• ocip_list_models — project_id
• ocip_get_model — project_id, model_name
• ocip_graph_neighborhood — project_id, name, optional node (Module|Model|Field|Function)
• ocip_function_impact — project_id, function_name, optional model
• ocip_field_impact — project_id, model_name, field_name

Graph reads consume your OCIP monthly quota like normal API usage.