Claude Desktop

Claude Desktop speaks MCP over stdio. Configure it by editing claude_desktop_config.json.

Where the config lives

• macOS: ~/Library/Application Support/Claude/claude_desktop_config.json
• Windows: %APPDATA%\Claude\claude_desktop_config.json
• Linux: ~/.config/Claude/claude_desktop_config.json

Claude Desktop creates the file on first launch. If it's missing, create it.

Add the Plainwork server

{
  "mcpServers": {
    "plainwork": {
      "command": "npx",
      "args": ["-y", "@plainwork/mcp"],
      "env": {
        "PLAINWORK_API_KEY": "pw_agent_…",
        "PLAINWORK_API_URL": "https://api.plainwork.xyz/v1"
      }
    }
  }
}

Replace pw_agent_… with the token from Plainwork → Settings → Agents → New agent. See Authentication.

Restart Claude Desktop. The Plainwork tools appear in the tools picker.

Pin a version

@plainwork/mcp at the latest is usually what you want. To pin:

{
  "mcpServers": {
    "plainwork": {
      "command": "npx",
      "args": ["-y", "@plainwork/mcp@0.1.0"],
      "env": { "PLAINWORK_API_KEY": "pw_agent_…" }
    }
  }
}

Verify

Ask Claude:

Create a page in my "Meeting Notes" collection summarising today's standup.

If auto-approve is off (the default), Claude reports "Proposal submitted — awaiting approval." Open Plainwork; the proposal is in the pending inbox. Approve it and the page appears in the collection.

If Claude reports a Plainwork API error (401), the token is wrong or revoked — see Invalid token.

Multiple agents

Each claude_desktop_config.json entry gets its own key. If you run multiple workspaces, or want separate attribution per user, give each entry a distinct key name (plainwork-personal, plainwork-work) and a separate agent in each workspace.