@simie/mcp

Connect Claude, Cursor, VS Code, or any MCP client to your Simie organization — CRM, knowledge base, forms, e-commerce, analytics, and agent management, as MCP tools scoped to exactly what your identity is allowed to touch.

Quick start

npx -y @simie/mcp setup

That's it. Setup signs you in (your browser opens to approve access — no keys to copy), optionally connects your own database, and prints ready-to-paste config for every MCP client. Example for Claude Code:

claude mcp add simie -- npx -y @simie/mcp serve --profile default

Or in .mcp.json / claude_desktop_config.json / .cursor/mcp.json / .vscode/mcp.json:

{
  "mcpServers": {
    "simie": { "command": "npx", "args": ["-y", "@simie/mcp", "serve", "--profile", "default"] }
  }
}

No credentials ever live in these config files. Your API key (and optional database connection string) are stored in ~/.simie/mcp/config.json with 0600 permissions, on your machine only.

Two modes

Platform mode (default — no database needed). Tools execute through the Simie platform over HTTPS. Includes Gmail / Calendar / Drive and connected external tools. Requires a connection to simie.ai while serving.

Database mode (BYO-DB orgs). If your organization runs on its own Postgres, setup (or npx -y @simie/mcp init) stores your connection string locally — it is never sent to Simie — and tools run directly against your database. Includes offline grace: a signed grant snapshot lets the server keep working for up to 24h if the platform is unreachable.

Commands

| Command | What it does | |---|---| | setup | First-run golden path: login → optional database → client config | | login | Sign in via browser device flow, or --api-key sk_live_… to paste a key | | init | Store your own database connection string (local only) | | serve | Start the MCP server over stdio (what your MCP client runs) | | config | Print client config (--claude-code --claude-desktop --cursor --vscode) | | whoami | Show the signed-in identity, org, and grant count | | logout | Remove this machine's config for the profile |

All commands take --profile <name> (default default) so multiple orgs or identities can live side by side. Self-hosting Simie? Add --api-url https://your-instance.

What you get

~250 tools across CRM (contacts, deals, journeys, tasks), knowledge base (articles, vector search, memory), forms, e-commerce, analytics, channels/SMS, Gmail/Calendar/Drive (when connected), PDF generation, and full agent/skill/MCP-profile management — plus read-only MCP resources for agent context. Exactly which tools you see is decided server-side by your identity and the profile configured in the dashboard (Agents → MCP Servers).

Security model

• Server-derived identity. Who you are and which tools you get is resolved by the platform from your user-bound API key — never asserted by the client. Org admins configure profiles (tool allow-lists, agent identities) in the dashboard.
• Scoped, revocable keys. Keys carry explicit scopes and are revocable in Settings → API Keys; a running server re-checks every 15 minutes and shuts down if revoked. In platform mode every single tool call is re-authorized server-side.
• Your database stays yours. In database mode the connection string never leaves your machine.
• Destructive actions confirm first. Tools that delete things ask for confirmation through your MCP client (and the platform independently enforces it in platform mode).
• Audited. Every tool invocation is recorded in your org's audit log with the acting identity.

Requirements

Node.js 20+. A Simie account (simie.ai).

Troubleshooting

• "No local config for profile …" — run npx -y @simie/mcp setup first; the MCP client only runs serve.
• "Access denied by the platform" — the key was revoked or your membership changed; run login again.
• "Cannot reach the platform" in platform mode — platform mode has no offline grace; retry when online, or connect your own database (init) for offline-capable database mode.
• Verify anytime: npx -y @simie/mcp whoami.

License

AGPL-3.0-only © Sustaina Company. Source: github.com/simieco/simie (apps/mcp).

For Simie platform developers: a legacy env-driven mode (SIMIE_LEGACY_DIRECT=true + DATABASE_URL + SIMIE_IDENTITY) exists for local monorepo use via the separate dist/index.js entrypoint only — not this npm bundle, whose serve has no env-trust path. See docs/reference/mcp.md. It trusts the environment and must never be exposed beyond an operator-controlled machine. Dev loop: pnpm --filter @simie/mcp test · pnpm --filter @simie/mcp build:bundle · release: pnpm release:mcp (see docs/guides/mcp-release.md).