> ## Documentation Index
> Fetch the complete documentation index at: https://docs.antasphere.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Connecting agents (MCP)

> Your Antasphere account is reachable by agents over MCP at https://account.antasphere.com/mcp, protected by the account service's own OAuth sign-in. Nothing to install and no secret to copy: the agent discovers how to sign in on its own, you approve it once, and you can revoke it at any time.

## claude.ai / Claude Desktop (OAuth)

Add a custom connector with the URL:

```
https://account.antasphere.com/mcp
```

The client discovers everything itself: it registers, you sign in and approve the consent screen,
and the connector holds a short-lived access token that renews in the background. Revoking the
connector, or leaving the organization it was used in, cuts it off immediately: every call is
checked against your live account.

Consent means **"act as you"**: the connector acts with your identity, across your organizations.
Which organization a call targets is a per-call choice: tools take an optional `workspace`
argument, and without it the request goes to your default organization (set in the dashboard),
else your oldest membership. Naming an organization you do not belong to is refused, and `get_me`
lists the ones the connector can name.

## Claude Code / CLIs (API key)

The same endpoint accepts your API keys directly, no OAuth dance:

```bash theme={null}
claude mcp add --transport http antasphere https://account.antasphere.com/mcp \
  --header "Authorization: Bearer ant_..."
```

Create keys in the dashboard (API keys → New). Scopes decide what an agent can do with a key:
`account:read` for reads, `account:write` for changes.

## Check that it works

```bash theme={null}
npx @modelcontextprotocol/inspector   # connect to the URL above → sign in → call get_me
```

`get_me` returning your identity proves the whole chain in one call.