# Remote MCP

> No install: point your client at https://api.clawifi.dev/mcp (streamable HTTP) and send your key as Authorization: Bearer, or in X-Clawifi-Api-Key. Every tool call is billed exactly like the REST route it runs. OAuth is not offered; use an API key. api.clawifi.qzz.io keeps working for older clients.

Canonical page: https://clawifi.dev/docs/remote-mcp

## Claude Code

**Claude Code**

```sh
claude mcp add --transport http clawifi https://api.clawifi.dev/mcp \
  --header "Authorization: Bearer $CLAWIFI_API_KEY"
```

## Cursor

**Cursor**

```json
{ "mcpServers": { "clawifi": { "url": "https://api.clawifi.dev/mcp", "headers": { "Authorization": "Bearer ${env:CLAWIFI_API_KEY}" } } } }
```

Paste into ~/.cursor/mcp.json; Cursor reads CLAWIFI_API_KEY from your environment.

## Codex

**Codex**

```toml
[mcp_servers.clawifi]
url = "https://api.clawifi.dev/mcp"
bearer_token_env_var = "CLAWIFI_API_KEY"
```

Add to your Codex config.toml; Codex sends CLAWIFI_API_KEY as the bearer token.

## Tools

Tools: fetch_url, scrape_url, extract_url, search_free, map_site, start_crawl, get_crawl, create_job, get_job, list_history, list_monitors, estimate, account and credits.

## Without a key

Without a key, search_free, fetch_url, scrape_url (with passages) and map_site still work as a trial: 12 calls a minute and 50 a day per address, with the playground's caps. Past that the tool answers with a link to get a free key at https://clawifi.dev/signup.