Connect Claude to the hosted Maskin MCP in under five minutes. Maskin is an open-source workspace where your whole team — humans and AI agents — works together with shared memory, context, and process. This guide walks you through connecting Claude to the hosted Maskin MCP so you can drive a workspace from inside Claude Code or Claude Desktop.
You don't need to clone anything, install dependencies, or run a local server. Maskin is hosted at maskin.sindre.ai.
Click Open in Claude at the top of this page. The pre-filled prompt tells Claude to drive Steps 4–5 based on where it's running. You still do Steps 1–3 in the Maskin UI yourself (sign in, paste Anthropic key, copy your Maskin API key + workspace ID) — those require browser auth.
What Claude does next depends on its environment:
claude mcp add maskin … directly, runs /reload-plugins (or tells you to restart Desktop), then calls get_started and drives the template pick interactively.Maskin and Remote MCP server URL: https://maskin.sindre.ai/mcp, plus auth headers Authorization: Bearer <KEY> and X-Workspace-Id: <ID>. Once wired, Claude calls get_started and drives the template pick.Want the most direct path? Start Claude Code in your terminal and paste the prompt below — Claude Code has shell access so it executes every step itself:
Help me connect the hosted Maskin MCP. Ask me for my Maskin API key (ank_...) and workspace ID from maskin.sindre.ai Settings. Then run `claude mcp add maskin --transport http --url https://maskin.sindre.ai/mcp --header "Authorization: Bearer <KEY>" --header "X-Workspace-Id: <ID>"`, run `/reload-plugins`, and call the `get_started` MCP tool interactively.
Prefer to wire it by hand? Follow the numbered steps below — same result.
Once you're in, you'll see the unified pipeline view: Insights → Bets → Tasks. All work — yours and your agents' — lives as objects in this pipeline.
Maskin needs your Anthropic API key to run agent sessions in its sandboxes. Keys are stored encrypted and scoped to the workspace.
To let Claude talk to your workspace, you need two values from the UI:
ank_… value that appears — this is your Maskin API key. You'll only see it once.Keep both values handy for the next step.
From a terminal, run:
claude mcp add maskin \
--transport http \
--url https://maskin.sindre.ai/mcp \
--header "Authorization: Bearer <YOUR_MASKIN_API_KEY>" \
--header "X-Workspace-Id: <YOUR_WORKSPACE_ID>"
Replace <YOUR_MASKIN_API_KEY> with the ank_… key from Step 3 and <YOUR_WORKSPACE_ID> with the workspace UUID.
If Claude Code is already running, reload plugins so the new tools show up in the current session:
/reload-plugins
Open your Claude Desktop MCP config (Settings → Developer → Edit config) and add the maskin entry:
{
"mcpServers": {
"maskin": {
"type": "http",
"url": "https://maskin.sindre.ai/mcp",
"headers": {
"Authorization": "Bearer <YOUR_MASKIN_API_KEY>",
"X-Workspace-Id": "<YOUR_WORKSPACE_ID>"
}
}
}
}
Save the file and restart Claude Desktop.
Back in Claude Code or Claude Desktop, ask:
Use the maskin MCP to call
get_started.
get_started is the entry-point tool. It previews and applies a workspace template — either development (for shipping a product), growth (for running a launch or outreach pipeline), or custom (a short questionnaire that tailors the workspace to whatever you're working on). Once you pick one, Claude seeds the workspace with object types, statuses, custom fields, and a first set of objects, and kicks off the pipeline.
If the tool returns a response without errors, you're connected. From here Claude can create and update insights, bets, and tasks, run triggers, and stream events directly against your hosted workspace.
get_started is just the start — list objects, create bets, fire triggers, and manage agent sessions all from Claude. Run list_tools to see the full set.Stuck? Open an issue in sindre-ai/maskin or read the README for deeper background on the data model, agent sessions, and the event stream.