amper-mcp-server
v0.1.0
Published
MCP server that exposes Amper's 80+ DeFi tools to any MCP client (Hermes, Claude Code, Cursor, etc.)
Readme
Amper MCP Server
MCP server that exposes Amper's 80+ DeFi tools to any MCP client: Hermes, Claude Code, Cursor, Windsurf, or any other MCP-compatible agent.
What it does
On startup, the server calls GET /api/v1/tools to discover all available Amper tools, then registers each as an MCP tool with its JSON schema. When a client invokes a tool, the server calls POST /api/v1/execute and returns the result.
Tools include: token swaps, Aave v3 lending, Morpho vaults, Avantis perpetuals (up to 500x), Derive options, cross-chain bridging, Venice staking, token creation, DeFi analytics, and more.
Setup
1. Get an Amper API key
Sign up at app.amper.chat, subscribe, then go to Settings > API to generate a key.
2. Use with Hermes
# ~/.hermes/config.yaml
mcp_servers:
amper:
command: "node"
args: ["/path/to/amper-mcp-server/dist/index.js"]
env:
AMPER_API_KEY: "${AMPER_API_KEY}"Or via CLI:
hermes mcp add amper --command node --args /path/to/amper-mcp-server/dist/index.js --env AMPER_API_KEY=amp_live_xxx3. Use with Claude Code
{
"mcpServers": {
"amper": {
"command": "node",
"args": ["/path/to/amper-mcp-server/dist/index.js"],
"env": {
"AMPER_API_KEY": "amp_live_xxx"
}
}
}
}Configuration
| Env var | Required | Description |
|---------|----------|-------------|
| AMPER_API_KEY | Yes | Your Amper API key (amp_live_ prefix) |
| AMPER_BASE_URL | No | Override the API base URL (default: https://app.amper.chat/api/v1) |
Build from source
npm install
npm run buildHow it works
- Discovery: Fetches all tools from
/api/v1/toolson startup (cached 5 min) - Execution: Each tool call goes to
POST /api/v1/executewith a unique idempotency key - Timeouts: 65s for trade tools, 35s for read tools (matches Amper's server limits)
- Errors: Rate limits, scope denials, and execution errors are returned as MCP error responses
- Transport: Stdio (Hermes/Claude Code spawn it as a subprocess)
Rate limits
- 30 requests/min per key
- 500 requests/day per key
- Sequential execution (one at a time per key)
