Connect any agent

Every agent connects to the same place. Pick the endpoint, then a key or OAuth, then paste the recipe for your agent below.

URL     https://a2ahello.com/mcp            one connection, every opted-in business
        https://a2ahello.com/t/<slug>/mcp   one business
Header  Authorization: Bearer a2h_live_...  an API key the business issued
or      OAuth 2.0, discovered from
        https://a2ahello.com/.well-known/oauth-authorization-server

A business issues its own a2h_live_ keys on the console's Access tab; with OAuth each person signs in through a2ahello and chooses which businesses may take orders. On /mcp, call find_business first, then pass its tenant_id to every other tool.

Checked: our go-live check calls a business's tools the way that agent does, and a business is listed to that agent only after it passes. Compatible: it speaks the same open standards and connects the same way, but we do not test it yet.

Muse Checked

In Muse, add a custom connector with the endpoint and choose API key or OAuth. With a key, a2ahello expects it in the header below. With OAuth, give Muse the metadata URL if it asks. No password, cookie, or second secret is needed.

Endpoint      https://a2ahello.com/mcp   (or https://a2ahello.com/t/{slug}/mcp)
API key       Authorization: Bearer a2h_live_...
OAuth         https://a2ahello.com/.well-known/oauth-authorization-server

Format as of 2026-10-17, from Muse Connector Platform docs (authentication: API keys or OAuth with PKCE; Meta does not publish the connector form itself).

ChatGPT Checked

Turn on developer mode, then create an app with the endpoint as its MCP server URL and OAuth as its authentication: ChatGPT registers itself with our server (dynamic client registration) and each person signs in once. Read tools also work with no authentication. ChatGPT's connector has no API-key option.

MCP server URL   https://a2ahello.com/mcp
Authentication   OAuth (dynamic client registration), or No authentication for read tools

Format as of 2026-10-17, from OpenAI, ChatGPT developer mode.

Grok Checked

In the xAI Responses API, add a remote MCP tool. xAI's docs do not say whether its authorization field adds the word Bearer, so send the whole header in headers.

"tools": [{
  "type": "mcp",
  "server_url": "https://a2ahello.com/mcp",
  "server_label": "a2ahello",
  "headers": { "Authorization": "Bearer a2h_live_..." }
}]

Format as of 2026-10-17, from xAI, Remote MCP tools.

Gemini Checked

Gemini CLI: one command, or the same entry in ~/.gemini/settings.json. For OAuth instead of a key, leave out the header: Gemini CLI finds our sign-in server from the 401 and registers itself; run /mcp auth a2ahello. Gemini Enterprise reaches a business's own agent over A2A: register its agent card, https://a2ahello.com/t/{slug}/a2a/agent-card.json.

gemini mcp add --transport http --header "Authorization: Bearer a2h_live_..." a2ahello https://a2ahello.com/mcp

{
  "mcpServers": {
    "a2ahello": {
      "httpUrl": "https://a2ahello.com/mcp",
      "headers": { "Authorization": "Bearer a2h_live_..." }
    }
  }
}

Format as of 2026-10-17, from Gemini CLI, MCP servers; Google Cloud, register an A2A agent in Gemini Enterprise.

Microsoft Copilot Compatible

In Copilot Studio, open the agent's Tools page, then Add a tool, New tool, Model Context Protocol. Enter a server name, a description, and the server URL. For authentication choose OAuth 2.0, type Dynamic discovery: Copilot Studio finds our endpoints and registers itself. With an API key instead, choose type Header and the header name Authorization, and enter the value Bearer a2h_live_...; we have not checked that Copilot Studio sends the value unchanged, so prefer OAuth. Copilot Studio can also call a business's own agent over A2A.

Server name     a2ahello
Server URL      https://a2ahello.com/t/{slug}/mcp   (or https://a2ahello.com/mcp)
Authentication  OAuth 2.0, Dynamic discovery

Format as of 2026-10-17, from Microsoft Learn, connect an agent to an existing MCP server; Microsoft Learn, Copilot Studio A2A.

Claude Checked

Claude (web and desktop): Settings, Connectors, Add custom connector, and paste the endpoint. Leave the OAuth client ID and secret empty: Claude registers itself and each person signs in once. Custom connectors use OAuth, not a key, and Claude Desktop does not connect to remote servers written into claude_desktop_config.json. Claude Code: one command with a key, or the same command without the header, then /mcp to sign in with OAuth.

claude mcp add --transport http a2ahello https://a2ahello.com/mcp --header "Authorization: Bearer a2h_live_..."

{
  "mcpServers": {
    "a2ahello": {
      "type": "http",
      "url": "https://a2ahello.com/mcp",
      "headers": { "Authorization": "Bearer ${A2AHELLO_KEY}" }
    }
  }
}

Format as of 2026-10-17, from Claude Code, MCP; Claude Help Center, custom connectors via remote MCP servers.

OpenClaw Checked

Add one server under mcp.servers in ~/.openclaw/openclaw.json (JSON5). For OAuth, replace headers with auth: "oauth" and run openclaw mcp login a2ahello.

{
  mcp: {
    servers: {
      a2ahello: {
        url: "https://a2ahello.com/mcp",
        transport: "streamable-http",
        headers: { Authorization: "Bearer a2h_live_..." },
      },
    },
  },
}

Format as of 2026-10-17, from OpenClaw, configuration: MCP, skills, and plugins.

Hermes Checked

Add one server under mcp_servers in ~/.hermes/config.yaml. For OAuth, replace headers with auth: oauth: Hermes handles discovery, registration, and PKCE.

mcp_servers:
  a2ahello:
    url: "https://a2ahello.com/mcp"
    headers:
      Authorization: "Bearer a2h_live_..."

Format as of 2026-10-17, from Hermes Agent, MCP.

Agents change their screens and config formats; if a field here no longer matches, use the agent's own name for it with the values above, and tell us at [email protected].