Connecter des agents au MCP MultiVoice

Les agents ne se connectent pas seuls. Configurez l’URL MCP ; un humain termine l’OAuth dans le navigateur.

URL MCP

https://db.multivoice.ai/mcp

Paramètres canoniques

Config name	multivoice
MCP URL	https://db.multivoice.ai/mcp
Transport	Streamable HTTP POST only
GET /mcp	GET /mcp returns 405 — expected; no SSE
Resource	https://db.multivoice.ai/mcp
Issuer	https://db.multivoice.ai
PRM	https://db.multivoice.ai/.well-known/oauth-protected-resource/mcp
AS metadata	https://db.multivoice.ai/.well-known/oauth-authorization-server
Authorize	https://db.multivoice.ai/oauth/authorize
Token	https://db.multivoice.ai/oauth/token
Register (DCR)	https://db.multivoice.ai/oauth/register
Auth	OAuth 2.1 Authorization Code + PKCE S256, public client

{
  "mcpServers": {
    "multivoice": {
      "url": "https://db.multivoice.ai/mcp"
    }
  }
}

Connect → browser OAuth (human login). Do not put API keys or JWTs in JSON. First smoke: multivoice.account.get.

codex mcp add multivoice --url https://db.multivoice.ai/mcp
codex mcp login multivoice

Do not use GET on /mcp as transport (405 is normal).
Do not start stdio/npx wrappers. Do not call LLM/synthesis servers instead of MCP.
Write only the URL into client config. Never insert tokens, passwords, CLIENT_API_KEY.
Stop and ask the human to Connect / codex mcp login.
Orders: orders.get_create_options → sources.inspect → orders.prepare_create → show total → orders.execute_create.
Language ids lowercase (ru, not RU).

Also see /llms.txt for crawlers and agents.