Connect

The MCP server lets an AI client — Claude Code, Cursor, the MCP Inspector, anything that speaks the Model Context Protocol — read and write one store through the same access rules as the HTTP API. There are two ways to run it:

• Hosted — POST https://core.inmake.dev/mcp (Production) and POST https://demo-core.inmake.dev/mcp (Demo). Stateless Streamable HTTP, JSON responses; nothing to install. The store header pins the session to one store.
• The stdio bin — drop-core-mcp, shipped in the Starter. Runs locally, switches stores and environments at runtime (useStore), and can enable image generation with your own Gemini key.
• As yourself — POST https://inmake.dev/mcp, the console's endpoint, with a personal access token instead of a store token: one connection reaches every project you are a member of, with your own role and capabilities. See below.

The first two need a store-scoped access token — mint a service token in CRM & Studio under Settings › Advanced › Tokens (see Authentication). Prefer a store token over a master token: every tool result echoes the tokenScope it ran on, and a master token triggers a loud warning in the stdio bin.

Claude Code#

claude mcp add --transport http inmake-<store-id> https://core.inmake.dev/mcp \
  --header "access-token: <token>" \
  --header "store: <store-id>"

Use https://demo-core.inmake.dev/mcp with a Demo token to work on the Demo twin of the store (name it inmake-<store-id>-demo, so both can be connected side by side). The console's Settings › Advanced › MCP page has these configs filled in for your project — Claude Code, Codex and Antigravity.

.mcp.json#

{
  "mcpServers": {
    "inmake-<store-id>": {
      "type": "http",
      "url": "https://core.inmake.dev/mcp",
      "headers": {
        "access-token": "<token>",
        "store": "<store-id>"
      }
    }
  }
}

MCP Inspector#

npx @modelcontextprotocol/inspector

Pick Streamable HTTP, enter the URL and the two headers. tools/list shows exactly what the store offers; the Tools page documents every one of them, and the Try-it rail on that page sends the same JSON-RPC calls from here.

As yourself — the console endpoint#

A member of a project in CRM & Studio can skip the store token: create a token under Profile › Personal access tokens (in_…, shown once) and connect to the console's endpoint:

claude mcp add --transport http inmake https://inmake.dev/mcp \
  --header "Authorization: Bearer in_…"

No store header: listStores lists the projects the token may open, useStore {store, env} picks the active one for the session, and each call runs with your own member token for that project (so the project's Activity shows your e-mail). The full guide — what a personal token may and may not do, the /me API and the token exchange the Starter's launcher uses (DROP_PAT) — is Personal access tokens.

First conversation#

1. Ask the agent to read the store: readStoreDocument on store (the root document — name, locales, capabilities) and listCollections.
2. Read the agent guide resource drop-core://docs/agents — the data model, paths and workflows an agent should follow — and the rule fragments under drop-core://rules/* (a client without resource support uses the readRule tool — {name: "agents"}, {name: "css-scoping"}, …).
3. Write with care: updateStoreDocument is a deep merge, writeSchema replaces the whole field list, and everything on Production is live.