Client Setup

Connect your AI coding assistant to Archer's MCP server using one of the configurations below.

Prerequisites

1. An Archer account at app.archerprotocol.com

2. An API key (create one in the Developer Portal at /developer)

Connection Details

Setting	Value
MCP URL	https://api.archerprotocol.com/mcp
Transport	Streamable HTTP (modern) or SSE (legacy)
Authentication	API key via x-api-key header or Authorization: Bearer header

Note: Claude Code and Claude Desktop require the @archerprotocol/mcp-client npm package (stdio bridge) instead of direct HTTP. See their sections below for details.

---

Claude Code

Claude Code requires a stdio bridge to properly authenticate with remote MCP servers. Install Archer's bridge package:

Add to your project's .mcp.json (recommended) or ~/.claude.json:

{
  "mcpServers": {
    "archer": {
      "command": "npx",
      "args": ["@archerprotocol/mcp-client"],
      "env": {
        "ARCHER_API_KEY": "arch_your_api_key_here"
      }
    }
  }
}

The @archerprotocol/mcp-client package runs locally, connects to Archer's remote server with your API key, and exposes all tools to Claude Code via stdio.

Environment Variables

Variable	Required	Description
ARCHER_API_KEY	Yes	Your Archer API key (starts with arch_)
ARCHER_MCP_URL	No	Override the MCP server URL (default: https://api.archerprotocol.com/mcp)

Example Session

$ claude

> What's the price of ETH right now?
The current price of ETH is $2,142.50 USD.

> Check my balances on Arbitrum
Your Arbitrum balances:
- 0.045 ETH ($96.41)
- 152.30 USDC ($152.30)

> Swap 50 USDC to ETH on Arbitrum
I've prepared a swap of 50 USDC to ETH on Arbitrum.

A transaction approval has been created in your Archer webapp.
Please open app.archerprotocol.com to review and sign the transaction.

> What was the result?
The swap was approved and executed successfully!
Transaction: 0x7a3f...8b2c (Arbiscan link)
You received 0.0233 ETH for 50 USDC.

---

Claude Desktop

Claude Desktop also uses the stdio bridge. Edit the config file:

macOS: ~/Library/Application Support/Claude/claude_desktop_config.json Windows: %APPDATA%\Claude\claude_desktop_config.json

{
  "mcpServers": {
    "archer": {
      "command": "npx",
      "args": ["@archerprotocol/mcp-client"],
      "env": {
        "ARCHER_API_KEY": "arch_your_api_key_here"
      }
    }
  }
}

---

Cursor

Cursor connects directly to Archer's remote MCP server via HTTP.

Via Settings UI

1. Open Cursor Settings

2. Navigate to the MCP section

3. Add a new server with:

   • Name: archer-protocol

   • Transport: SSE

   • URL: https://api.archerprotocol.com/mcp

   • Headers: x-api-key: arch_your_api_key_here

Via Project Config

Create .cursor/mcp.json in your project root:

{
  "mcpServers": {
    "archer-protocol": {
      "type": "sse",
      "url": "https://api.archerprotocol.com/mcp",
      "headers": {
        "x-api-key": "arch_your_api_key_here"
      }
    }
  }
}

---

VS Code / GitHub Copilot

VS Code supports MCP servers at workspace and user scope.

Workspace Config

Create .vscode/mcp.json in your workspace:

{
  "servers": {
    "archer-protocol": {
      "type": "sse",
      "url": "https://api.archerprotocol.com/mcp",
      "headers": {
        "x-api-key": "arch_your_api_key_here"
      }
    }
  }
}

Via Command Palette

1. Open Command Palette (Cmd+Shift+P / Ctrl+Shift+P)

2. Run "MCP: Add Server"

3. Select SSE transport

4. Enter the URL and API key when prompted

---

GitHub Copilot CLI

Use the interactive flow:

gh copilot mcp add

Or edit the config file directly following GitHub's MCP configuration format with the same connection details above.

---

Windsurf

Configure MCP in Windsurf/Cascade settings:

1. Open Windsurf Settings

2. Navigate to Cascade MCP Integration

3. Add a new MCP server, or manually edit mcp_config.json:

{
  "archer-protocol": {
    "type": "sse",
    "url": "https://api.archerprotocol.com/mcp",
    "headers": {
      "x-api-key": "arch_your_api_key_here"
    }
  }
}

Note: Windsurf enforces a 100-tool limit across all enabled MCP servers.

---

Cline

Add via Cline's server configuration flow:

1. Open Cline chat

2. Use the "Adding & Configuring Servers" workflow

3. Provide:

   • Server URL: https://api.archerprotocol.com/mcp

   • Transport: SSE

   • API Key: Your Archer API key

---

Continue

Continue uses workspace-level YAML config. Create .continue/mcpServers/archer.yaml:

name: archer-protocol
type: sse
url: https://api.archerprotocol.com/mcp
headers:
  x-api-key: arch_your_api_key_here

Continue can also import JSON MCP configs from Claude Desktop, Cursor, and Cline formats.

---

Goose

Use the interactive extension flow:

goose configure extension

When prompted:

• Command/URL: https://api.archerprotocol.com/mcp

• Transport: SSE

• Description: Archer Protocol Web3 tools

---

Generic MCP Client

Any MCP-compatible client can connect using the standard HTTP transport:

{
  "type": "sse",
  "url": "https://api.archerprotocol.com/mcp",
  "headers": {
    "x-api-key": "arch_your_api_key_here"
  }
}

If your client supports Streamable HTTP (the newer MCP transport), you can use:

{
  "type": "http",
  "url": "https://api.archerprotocol.com/mcp",
  "headers": {
    "x-api-key": "arch_your_api_key_here"
  }
}

Both transports are supported by Archer's MCP server. Streamable HTTP is preferred when available.

Security Notes

• Never commit API keys to version control. Use environment variables or secrets managers.

• API keys are scoped — create keys with only the permissions you need.

• Transaction operations always require human approval in the webapp.

• You can revoke API keys at any time from the Developer Portal.