MCP server

Build and launch

npm run build:mcp
node /absolute/path/to/venue-mind/packages/mcp-server/dist/index.js

Durable Project sessions

• Filesystem repository with atomic writes.
• One active Project per MCP connection.
• venue.list_projects and venue.open_project select Project scope.
• Set VENUEMIND_DATA_DIR to an explicit writable data directory.
• Project record schema version 10.

Protocol surfaces

• 56 tools generated from one shared contract source across WebMCP and standalone MCP.
• Current Project, Plan Version, Proposal, schema, documentation, and compatibility resources.
• Project and Plan Version resource templates with completion.
• Supervised planning and Plan audit prompts.
• Progress notifications for Validation and Simulation.
• Structured standard-error logs and graceful interruption handling.

Codex

codex mcp add venuemind --env VENUEMIND_DATA_DIR=/absolute/path/to/venuemind-data -- node /absolute/path/to/venue-mind/packages/mcp-server/dist/index.js
codex mcp get venuemind

Claude Desktop, Cursor, and generic clients

{
  "mcpServers": {
    "venuemind": {
      "command": "node",
      "args": [
        "/absolute/path/to/venue-mind/packages/mcp-server/dist/index.js"
      ],
      "env": {
        "VENUEMIND_DATA_DIR": "/absolute/path/to/venuemind-data"
      }
    }
  }
}

• Claude Desktop: add the entry to claude_desktop_config.json and restart.
• Cursor: save it as .cursor/mcp.json for Project scope or ~/.cursor/mcp.json for global scope.
• Generic local MCP hosts commonly accept the same process configuration.

Official MCP Inspector

npx @modelcontextprotocol/inspector node /absolute/path/to/venue-mind/packages/mcp-server/dist/index.js

ChatGPT-compatible remote deployment

ChatGPT custom MCP apps connect to remote endpoints, not directly to a local stdio process. Put an authenticated Streamable HTTP Adapter or supported secure MCP tunnel in front of the same server Module; never expose the stdio process itself to the network.

• Validate OAuth tokens and token audience.
• Publish protected-resource metadata.
• Bind Project access to the authenticated principal.
• Enforce VenueMind authorization scopes.
• Use TLS, restrict origins, and reject caller-supplied organization or actor authority.

Compatibility

• MCP server 0.7.0.
• Preferred protocol revision 2026-07-28.
• Minimum supported revision 2025-03-26.
• Tool contract 1.6.0.
• Approval, Occupancy Alert acknowledgement, and Incident response authority: human-only. Live Plan Deviation tools create records and review-state post-event Proposals only.

Human-only approval

The MCP surface can inspect, preview, validate, branch, switch, read, and export. Approval is deliberately absent; the VenueMind Studio owns the human commit decision.