@seanpropapp/mcp

Run SeanPropApp's proposition methodology from inside Claude Desktop, Cursor, or Claude Code using your own subscription. No API key required: the server assembles a methodology prompt and returns it; your MCP host's LLM does the inference.

The methodology stays server-side. This package is a thin client that calls /api/mcp/assemble-prompt with your token and returns the assembled prompt.

What it exposes

• Tool run_module(moduleId, company, persona?, priorOutputs?) — for agentic hosts (Cursor, Claude Code).
• 17 prompts (one per methodology module) — for menu hosts (Claude Desktop).
• Resource methodology://version — the current methodology version.

Get a token

Sign in at https://prop.seanoneill.com/mcp-setup and click Generate token. Copy it (shown once).

Local testing (before this is published to npm)

cd packages/mcp-server
npm install
npm run build

Then point Claude Desktop at the local build. Edit ~/Library/Application Support/Claude/claude_desktop_config.json:

{
  "mcpServers": {
    "SeanPropApp": {
      "command": "node",
      "args": ["/ABSOLUTE/PATH/TO/proposition-app/packages/mcp-server/dist/index.js"],
      "env": {
        "SEANPROPAPP_MCP_TOKEN": "<your token>",
        "SEANPROPAPP_MCP_URL": "http://localhost:3000"
      }
    }
  }
}

• SEANPROPAPP_MCP_URL is optional and defaults to https://prop.seanoneill.com. Set it to http://localhost:3000 to test against a local dev server, or omit it to hit production.
• Restart Claude Desktop after editing the config. The 17 modules appear in the prompts menu (the + / slash-command area); pick one and provide the company.

Published usage (after go-public)

{
  "mcpServers": {
    "SeanPropApp": {
      "command": "npx",
      "args": ["-y", "@seanpropapp/mcp"],
      "env": { "SEANPROPAPP_MCP_TOKEN": "<your token>" }
    }
  }
}

Environment

• SEANPROPAPP_MCP_TOKEN (required) — your MCP bearer token.
• SEANPROPAPP_MCP_URL (optional) — API base URL; defaults to production.