Local development

Production and local dev use different transport paths because Anthropic’s Connector OAuth runs in the cloud and cannot reach localhost.

Prod vs dev

	Production	Local dev
Claude connection	Native Connector	`mcp-remote` in Claude Desktop config
Bridge URL	`https://agent.artos.sh/mcp`	`https://agent.dev.artos.sh/mcp`
OAuth	Anthropic cloud → public `api.artos.sh`	On your machine → local Caddy/API
OAuth client	Claude’s CIMD (`client_id` = claude.ai URL)	Our CIMD doc via `--static-oauth-client-info`
Callback	Claude hosted callback	`localhost:8898/oauth/callback`

Native Connector cannot hit localhost — use mcp-remote for local stacks.

Key URLs

Thing	Production	Dev
Bridge MCP	`agent.artos.sh/mcp`	`agent.dev.artos.sh/mcp`
API / OAuth AS	`api.artos.sh`	`api.dev.artos.sh`
Consent	`my.artos.sh/oauth/consent`	`my.dev.artos.sh/oauth/consent`
Agent profile	`profile-artos.vercel.app/.well-known/ucp`	same
CIMD client	`profile-artos.vercel.app/well-known/oauth-client.json`	same

mcp-remote example


{
  "mcpServers": {
    "artos": {
      "command": "npx",
      "args": [
        "-y",
        "mcp-remote",
        "https://agent.dev.artos.sh/mcp",
        "--static-oauth-client-info",
        "https://profile-artos.vercel.app/well-known/oauth-client.json"
      ],
      "env": {
        "NODE_EXTRA_CA_CERTS": "/path/to/mkcert-rootCA.pem"
      }
    }
  }
}

NODE_EXTRA_CA_CERTS is required when the dev bridge uses mkcert TLS.

CIMD redirect URIs

The CIMD oauth-client.json must list http://localhost:8898/oauth/callback (and any other dev callback ports you use).

Operator docs

Bridge deployment, env vars, and deep troubleshooting live in the internal artos-mcp-bridge README and AGENT-COMMERCE-FLOW .