# More MCP clients > Connect Crush, Amp, Kimi Code CLI, Warp, Qwen Code, Continue, Augment, Amazon Q Developer and Google Antigravity to the hosted Spicrawl MCP server at https://mcp.spicrawl.com/mcp. Source: https://docs.spicrawl.com/agents/other-clients Any MCP client that speaks Streamable HTTP and can send a custom header connects to Spicrawl. Use these settings, then find your client below: | Setting | Value | | ----------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | Transport | Streamable HTTP | | URL | `https://mcp.spicrawl.com/mcp` | | Header | `Authorization: Bearer ` (`spicrawl_live_…` or `spicrawl_test_…`) | | OAuth | None. The server accepts API keys only, so an OAuth-only client cannot connect, and a client that tries OAuth first needs it turned off for this server. | | stdio-only client | Bridge with `npx -y mcp-remote https://mcp.spicrawl.com/mcp --header "Authorization:${SPICRAWL_AUTH}"` and the environment variable `SPICRAWL_AUTH="Bearer spicrawl_live_..."`. | Once connected, the client lists 25 `spicrawl_*` tools. Set your key in the environment the client starts from, and keep it out of committed files: ```bash export SPICRAWL_API_KEY=spicrawl_live_... # add to your shell profile, then restart the client ``` To confirm the endpoint is reachable before you debug a client, run `curl -i https://mcp.spicrawl.com/mcp`. Without a key it answers HTTP `401` with `Unauthorized: send your Spicrawl API key`. Every tool is described on [MCP server](https://docs.spicrawl.com/agents/mcp.md), and the agent skill is at `https://app.spicrawl.com/skill.md` ([Agent skill](https://docs.spicrawl.com/agents/skill.md)). ## Clients with their own page * [Claude Code](https://docs.spicrawl.com/agents/claude-code.md), [Cursor](https://docs.spicrawl.com/agents/cursor.md), [Codex](https://docs.spicrawl.com/agents/codex.md), [OpenCode](https://docs.spicrawl.com/agents/opencode.md), [Gemini CLI](https://docs.spicrawl.com/agents/gemini-cli.md) * [GitHub Copilot](https://docs.spicrawl.com/agents/github-copilot.md), [Windsurf](https://docs.spicrawl.com/agents/windsurf.md), [Cline](https://docs.spicrawl.com/agents/cline.md), [Kilo Code](https://docs.spicrawl.com/agents/kilo-code.md) * [Zed](https://docs.spicrawl.com/agents/zed.md), [JetBrains](https://docs.spicrawl.com/agents/jetbrains.md), [Goose](https://docs.spicrawl.com/agents/goose.md), [Kiro](https://docs.spicrawl.com/agents/kiro.md) * [Factory](https://docs.spicrawl.com/agents/factory.md), [Devin](https://docs.spicrawl.com/agents/devin.md), [OpenHands](https://docs.spicrawl.com/agents/openhands.md) * [App builders](https://docs.spicrawl.com/agents/app-builders.md), [Frameworks](https://docs.spicrawl.com/agents/frameworks.md) * Claude Desktop: see the Claude Desktop tab on [MCP server](https://docs.spicrawl.com/agents/mcp.md#set-up-your-client). It uses the `mcp-remote` bridge. ## Crush [Crush](https://github.com/charmbracelet/crush) (Charm) supports `http` MCP servers. Header values go through shell expansion, so `$SPICRAWL_API_KEY` is read from the environment when Crush starts. Add the server to `crush.json` in the project (`.crush.json` also works), or to the global `~/.config/crush/crush.json`: ```json title="crush.json" { "mcp": { "spicrawl": { "type": "http", "url": "https://mcp.spicrawl.com/mcp", "headers": { "Authorization": "Bearer $SPICRAWL_API_KEY" } } } } ``` Crush's newer configuration format is a `crushrc` (`./.crushrc`, `./crushrc` or `~/.config/crush/crushrc`), a Bash file with Crush builtins. The same server there: ```bash title="crushrc" mcp add spicrawl --type http --url "https://mcp.spicrawl.com/mcp" \ --header Authorization "Bearer $SPICRAWL_API_KEY" ``` Do not set `"oauth": true` on this server. Start Crush from a shell where `SPICRAWL_API_KEY` is set, then ask it to list its `spicrawl_*` tools. Crush reads skills from `.agents/skills`, `.crush/skills`, `.claude/skills` and `.cursor/skills` in the project, and `~/.agents/skills/` and `~/.config/crush/skills/` globally. It also loads `~/.config/AGENTS.md` as global instructions, and `AGENTS.md` is the default name of the project context file that `/init` writes. Install the skill with `spicrawl skill install --client codex`, which writes `.agents/skills/spicrawl/SKILL.md`. ## Amp [Amp](https://ampcode.com) (Sourcegraph) stores MCP servers under `amp.mcpServers` in `~/.config/amp/settings.json`, or `.amp/settings.json` in a project. `${VAR}` is expanded in the file. `amp mcp add` takes no header flag, so add the entry to the settings file: ```json title="~/.config/amp/settings.json" { "amp.mcpServers": { "spicrawl": { "url": "https://mcp.spicrawl.com/mcp", "headers": { "Authorization": "Bearer ${SPICRAWL_API_KEY}" } } } } ``` If you add other keys to the same file, keep them in the one JSON object. Check the connection: ```bash amp mcp doctor ``` It prints each server's status, including whether a workspace server still needs approval (`amp mcp approve spicrawl`). Amp reads skills from `~/.config/agents/skills/`, `~/.agents/skills/`, `~/.config/amp/skills/`, and `.agents/skills/` and `.claude/skills/` in the project and its parents. It reads `AGENTS.md` from the working directory and its parents, and from `~/.config/amp/AGENTS.md` and `~/.config/AGENTS.md`. `spicrawl skill install --client codex` writes to `.agents/skills/spicrawl/SKILL.md`, which Amp finds. ## Kimi Code CLI [Kimi Code CLI](https://github.com/MoonshotAI/kimi-code) (Moonshot AI) reads `mcp.json` from `~/.kimi-code/mcp.json` (or `$KIMI_CODE_HOME/mcp.json`) for every project, and `.kimi-code/mcp.json` in a project. A project entry overrides a user entry of the same name. An entry with a `url` and no `transport` is an HTTP server. `bearerTokenEnvVar` names the environment variable that holds the key, so the file stays free of secrets: ```json title="~/.kimi-code/mcp.json" { "mcpServers": { "spicrawl": { "url": "https://mcp.spicrawl.com/mcp", "bearerTokenEnvVar": "SPICRAWL_API_KEY" } } } ``` Alternatively, `"headers": { "Authorization": "Bearer spicrawl_live_..." }` writes the key into the file. Servers added while a session is open join only sessions started later. Run `/mcp` in the session to see each server's connection status. `/mcp-config` adds and edits servers from the terminal UI. > **Note:** Older Kimi CLI releases documented `kimi mcp add --transport http`. The current Kimi Code CLI documentation has no `kimi mcp` subcommand; use `mcp.json` or `/mcp-config`. Kimi Code CLI reads skills from `~/.kimi-code/skills/`, `~/.agents/skills/`, and `.kimi-code/skills/` and `.agents/skills/` in the project. It injects `AGENTS.md` (project root or `.kimi-code/AGENTS.md`, plus `~/.kimi-code/AGENTS.md` and `~/.agents/AGENTS.md`) into its prompt. `spicrawl skill install --client codex` writes `.agents/skills/spicrawl/SKILL.md`. ## Warp [Warp](https://www.warp.dev) takes MCP servers as JSON. A server with a `url` is a Streamable HTTP (or SSE) server, and `headers` is an object of request headers. **Step 1: Open the MCP servers page** Go to **Settings → Agents → MCP servers**, or **Warp Drive → Personal → MCP Servers**, or search the command palette for "Open MCP Servers". Choose **+ Add**. **Step 2: Paste the server** ```json { "spicrawl": { "url": "https://mcp.spicrawl.com/mcp", "headers": { "Authorization": "Bearer spicrawl_live_..." } } } ``` Warp's documentation describes no environment-variable expansion for URL servers, so the key is written into Warp's saved configuration. Use a key you can revoke from the dashboard. **Step 3: Start it** Save, then use **Start** on the server. A running server lists its tools. Warp reads project rules from `AGENTS.md` (or `WARP.md`) at the project root. ## Qwen Code [Qwen Code](https://github.com/QwenLM/qwen-code) has separate keys per transport. `httpUrl` is Streamable HTTP; `url` is SSE, so use `httpUrl`. Add the server with one command (`--scope user` stores it in `~/.qwen/settings.json` for every project): ```bash qwen mcp add --scope user --transport http spicrawl https://mcp.spicrawl.com/mcp \ --header "Authorization: Bearer $SPICRAWL_API_KEY" ``` Your shell expands `$SPICRAWL_API_KEY` before Qwen Code stores it, so the key lands in the settings file. To keep it out, write the entry by hand: Qwen Code expands `$VAR` and `${VAR}` in `settings.json` from your environment. ```json title="~/.qwen/settings.json" { "mcpServers": { "spicrawl": { "httpUrl": "https://mcp.spicrawl.com/mcp", "headers": { "Authorization": "Bearer ${SPICRAWL_API_KEY}" } } } } ``` Project scope is `.qwen/settings.json`. Run `qwen mcp list` to check, or `/mcp` inside a session. Qwen Code reads skills from `~/.qwen/skills/` and `.qwen/skills/`. Its context file defaults to `QWEN.md`; to load `AGENTS.md` too, set `"context": { "fileName": ["QWEN.md", "AGENTS.md"] }` in `settings.json`. Install the skill with `mkdir -p .qwen/skills/spicrawl && curl -fsSL https://app.spicrawl.com/skill.md -o .qwen/skills/spicrawl/SKILL.md`. ## Continue [Continue](https://docs.continue.dev) configures MCP servers in YAML. Put a file in `.continue/mcpServers/` at the top of the workspace, or add the same `mcpServers` block to `config.yaml`. MCP tools work in Agent mode only. For a `streamable-http` server, `apiKey` is sent as `Authorization: Bearer `: ```yaml title=".continue/mcpServers/spicrawl.yaml" name: Spicrawl version: 0.0.1 schema: v1 mcpServers: - name: spicrawl type: streamable-http url: https://mcp.spicrawl.com/mcp apiKey: ${{ secrets.SPICRAWL_API_KEY }} ``` Or set the header yourself with `requestOptions.headers`: ```yaml mcpServers: - name: spicrawl type: streamable-http url: https://mcp.spicrawl.com/mcp requestOptions: headers: Authorization: Bearer ${{ secrets.SPICRAWL_API_KEY }} ``` `${{ secrets.SPICRAWL_API_KEY }}` is read from a `.env` file at `~/.continue/.env` or at the workspace root. Add the line `SPICRAWL_API_KEY=spicrawl_live_...` there and keep that file out of version control. Switch to Agent mode and open the tools list to confirm the server and its `spicrawl_*` tools. ## Augment Augment's Auggie CLI supports remote HTTP servers with headers: ```bash auggie mcp add spicrawl \ --transport http \ --url https://mcp.spicrawl.com/mcp \ --header "Authorization:Bearer $SPICRAWL_API_KEY" ``` Or edit `~/.augment/settings.json`: ```json title="~/.augment/settings.json" { "mcpServers": { "spicrawl": { "type": "http", "url": "https://mcp.spicrawl.com/mcp", "headers": { "Authorization": "Bearer spicrawl_live_..." } } } } ``` Check the result with `auggie mcp list`. The command form stores the expanded key in the settings file. > **Augment extension for VS Code and JetBrains:** Augment's extension documents a remote server as a connection type (HTTP or SSE), a name and a URL, with no header field. A server that needs `Authorization` cannot be added that way. Add Spicrawl as a local (stdio) server that runs the `mcp-remote` bridge from the settings table above, or use the Auggie CLI. Auggie reads skills from `~/.augment/skills/`, `~/.claude/skills/`, `~/.agents/skills/` and the matching `.augment/`, `.claude/` and `.agents/` folders in the workspace. It reads `AGENTS.md` and `CLAUDE.md` as rules, including from parent directories. ## Amazon Q Developer In the IDE (VS Code, JetBrains and others), Amazon Q Developer adds HTTP servers from a form and stores them in `~/.aws/amazonq/default.json` (global) or `.amazonq/default.json` (project). **Step 1: Open the MCP panel** Open the Q Developer **Chat** panel and choose the tools icon, then the plus (**+**) symbol. **Step 2: Fill in the server** Pick the scope (global or local). Set **Name** to `spicrawl`, the transport to `http`, and **URL** to `https://mcp.spicrawl.com/mcp`. Under **Headers - optional**, add the key `Authorization` with the value `Bearer spicrawl_live_...`. Choose **Save**. **Step 3: Set tool permissions** Set each tool to Ask, Always allow or Deny. A connection failure shows an alert with **Fix Configuration**. The form writes the key into `default.json`; keep the project-level file out of version control. Legacy `mcp.json` files (`~/.aws/amazonq/mcp.json` and `.amazonq/mcp.json`) are still read while `useLegacyMcpJson` is true, its default. If Amazon Q asks you to authorize in a browser, the server was treated as OAuth: check the header is set. > **Note:** The Amazon Q Developer command-line agent is covered on [Kiro](https://docs.spicrawl.com/agents/kiro.md). ## Google Antigravity [Google Antigravity](https://antigravity.google) uses `serverUrl`, not `url`, for remote servers (it also covers Streamable HTTP). Edit `mcp_config.json`: * Global: `~/.gemini/config/mcp_config.json` * Workspace: `.agents/mcp_config.json` * Antigravity 2.0 app: **Settings → Customizations → Open MCP Config** * IDE: in the Agent panel, **Additional options → MCP Servers → Manage MCP Servers → View raw config** ```json title="mcp_config.json" { "mcpServers": { "spicrawl": { "serverUrl": "https://mcp.spicrawl.com/mcp", "headers": { "Authorization": "Bearer spicrawl_live_..." } } } } ``` The file holds the key in plain text, so keep the workspace copy out of version control. Restart the assistant or reload MCP servers, then ask it to call `spicrawl_usage_summary` or any `spicrawl_*` tool to confirm the connection. Antigravity has its own Agent Skills feature; see its documentation for the skill folder. ## Troubleshooting | Symptom | Cause | Fix | | -------------------------------------------------------------------------- | --------------------------------------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------- | | HTTP `401`, or `Unauthorized: send your Spicrawl API key` | No `Authorization` header, or the key is unknown, revoked or expired. | Check the header is `Authorization: Bearer spicrawl_…` and the variable is set where the client starts. | | The header contains a literal `$SPICRAWL_API_KEY` or `${SPICRAWL_API_KEY}` | The client does not expand variables in that field. | Use the client's own mechanism from its section above (Kimi `bearerTokenEnvVar`, Continue `secrets`), or write the key into a local file that is not committed. | | A browser window opens for authorization | The client is trying OAuth, which the server does not offer. | Send the `Authorization` header; turn OAuth off for this server. | | A remote server cannot be added because there is no header field | The client's form only takes a URL. | Bridge with `mcp-remote` as a local stdio server. | | HTTP `503` with `Retry-After` on connect | The MCP server could not reach the API to check your key. | Retry after the given seconds. The key is fine. | More causes and fixes are in the Troubleshooting table on [MCP server](https://docs.spicrawl.com/agents/mcp.md#troubleshooting).