Claude Desktop

How it works

Claude Desktop loads MCP servers from its config file; Apender runs as a local stdio process.

Architecture

Claude Desktop → MCP (stdio) → Apender API.

Configuration

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

Example server block — adjust paths as needed. Full reference: MCP configure.

{
  "mcpServers": {
    "apender": {
      "command": "node",
      "args": ["/absolute/path/to/apender-mcp-server"],
      "env": {
        "APD_API_URL": "<API base URL from Dashboard → API keys>",
        "APD_API_KEY": "apd_live_your_key",
        "APD_WORKSPACE_ROOT": "/absolute/path/to/git/repo"
      }
    }
  }
}

Authentication

APD_* env in the server block — values from Dashboard → API keys.

Create keys in Dashboard → API keys.

Workspace root

APD_WORKSPACE_ROOT = git repo root for that workspace.

Example

Planning flow: set workspace root to the target repo.

Troubleshooting

MCP server fails to start

Use absolute paths for the server command and args in the host config.