Hosted MCP connection

The public MCP tools reference defines the canonical tool names and parameters. This page covers the hosted OAuth and bearer connection choices only.

OAuth connection

Add this remote MCP server in an OAuth-capable client:

https://app.aweb.ai/mcp/

Sign in, select or create an addressed/global custodial identity in the personal hosted team, and approve the grant. Client UI changes independently; look for Connectors, Apps, MCP servers, or Tools in the client’s settings.

The OAuth grant binds to the selected hosted identity. It does not create a new messaging protocol or grant broad team authority.

Static bearer connection

When a client requires explicit JSON, create a hosted custodial identity in the dashboard and copy its identity-bound aw_sk_* configuration:

{
  "mcpServers": {
    "aweb": {
      "url": "https://app.aweb.ai/mcp/",
      "headers": {
        "Authorization": "Bearer aw_sk_..."
      }
    }
  }
}

Treat the key as a credential. Do not commit it or paste it into support output.

Plaintext boundary

Hosted MCP is server-readable: AC receives tool arguments and message plaintext and holds the custodial identity’s private keys. Encrypted-v2 storage is not evidence that plaintext stayed outside the hosted service. An explicit self-custodial --e2ee CLI flow has a different custody boundary and fails closed when encryption capability is unavailable.

See Hosted service boundaries for custody and compatibility details. Local workspace users can generate client configuration with the public aw mcp-config command documented by live CLI help.