Skip to content
Merged
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
33 changes: 28 additions & 5 deletions docs/guides/developer-setup.md
Original file line number Diff line number Diff line change
Expand Up @@ -107,21 +107,44 @@ Save the returned API key.

## Step 7: Generate Claude Desktop Config

Create `claude_desktop_config.json` for your business team:
Create `claude_desktop_config.json` for your business team.

**For Claude Desktop (local server via npx):**
```json
{
"mcpServers": {
"seller-agent": {
"url": "http://your-server:8000/mcp/mcp",
"headers": {
"Authorization": "Bearer <operator-api-key-from-step-6>"
}
"command": "npx",
"args": [
"mcp-remote",
"http://your-server:8000/mcp/",
"--header",
"Authorization: Bearer <operator-api-key-from-step-6>"
]
}
}
}
```

**For Claude Desktop (local server via uvx — Python only, no Node.js needed):**
```json
{
"mcpServers": {
"seller-agent": {
"command": "uvx",
"args": [
"mcp-remote",
"http://your-server:8000/mcp/",
"--header",
"Authorization: Bearer <operator-api-key-from-step-6>"
]
}
}
}
```

> The trailing slash on `/mcp/` is required for `mcp-remote`.

## Step 8: Hand Off

Give the `claude_desktop_config.json` file to your publisher operations team. They'll add it to Claude Desktop and complete the business setup (media kit, pricing, approval gates, buyer registration) through the interactive wizard.
Expand Down
Loading