Connect the agent you already use.
Archer's marketplace speaks MCP. Any client that can send a custom header can discover and invoke services with one config block, and an autonomous agent can onboard itself from a single skill file with no human in the loop.
Claude Code
One command adds Archer as an MCP server. Works the same in Claude Desktop via the equivalent JSON config.
claude mcp add --transport http archer \
https://api.archerprotocol.com/mcp \
--header "x-api-key: <your key>"Any MCP client
Cursor, Windsurf, or any harness that speaks Streamable HTTP and can send a custom header.
{
"mcpServers": {
"archer": {
"url": "https://api.archerprotocol.com/mcp",
"headers": { "x-api-key": "<your key>" }
}
}
}Autonomous agents
Hermes, OpenClaw, ElizaOS, or any harness with a shell and an inbox. Fetch the raw skill and follow it: email signup, multichain wallets, scoped API keys, MCP wiring.
curl -fsSL https://archerprotocol.com/connect-agent/SKILL.mdQuickstart
- Get an API key: sign in at app.archerprotocol.com/developer and mint a scoped key, or self-sign-up programmatically per the skill file. Scopes are read, quote, swap, bridge, send, wallet; request only what the job needs and set a spend limit.
- Add the MCP server with the config block or command above.
- Prove the connection. Type these into your connected client, word for word if you like:
Say: "List my Archer wallets." -> calls list_user_wallets, returns your addresses Say: "What do my Archer wallets hold?" -> calls get_user_balances, shows funding by chain Say: "Search Archer for a live ETH chart." -> calls discover, returns matching services
Chat-app connectors (claude.ai, ChatGPT) require OAuth and are not supported yet; use a header-capable client from the cards above.
The full onboarding skill lives at a stable URL as raw markdown. Point any agent at archerprotocol.com/connect-agent/SKILL.md and it can take itself from nothing to a funded, MCP-connected account. The shorter index for crawlers is /llms.txt.