Connect to Alpen MCP

Endpoint

MCP over Streamable HTTP. JSON-RPC 2.0. Open access, no API key. Read-only. Rate limited by IP.

What you get

• get_network_info

  Get information about an Alpen network. Returns chain ID, RPC endpoint, currency, status, explorers, faucet, bundler, and notes for the requested network. If network_id is omitted, returns the currently active network. Use this when an agent needs to know which testnet is live, what RPC URL to use, what chain ID to add to a wallet, or where the explorer lives.

• get_contracts

  Get smart contract addresses deployed on an Alpen network (e.g. ERC-4337 EntryPoint, bridge). If network_id is omitted, uses the currently active network. Returns null entries for contracts that aren't yet published.

• get_partners

  List Alpen ecosystem and infrastructure partners. Returns name, category, relationship, status, and a short description for each. Use this when an agent needs to know who's deploying on Alpen, what's available for integration, or to answer questions like 'does Alpen support lending' or 'what oracles are available'. Optional filters narrow by category, relationship, or status.

• search_docs

  Search Alpen Labs documentation, whitepapers, research, transcripts, and external blog posts. Returns relevant excerpts ranked by semantic similarity. Use this when an agent needs to answer a technical or factual question about Alpen (architecture, bridge, ZK rollup, garbled circuits, BTD, partners, etc).

• explorer_get_address_summary

  Read an address summary from Alpen's Blockscout explorer. Returns native sBTC balance, whether it has token transfers/tokens, token balances, and links. Use when the user asks you to check the block explorer for their wallet or whether tokens showed up.

• explorer_get_address_transactions

  Read recent transactions for an address from Alpen's Blockscout explorer, including status, method, decoded input, revert result, and explorer links. Use to debug whether a wallet action actually succeeded or reverted.

• explorer_get_transaction

  Read one transaction from Alpen's Blockscout explorer by hash. Returns success/revert status, decoded method/input, value, fee, token transfers, and explorer link. Use when the user gives a tx hash or asks what happened to a transaction.

Claude Desktop

Recent versions support remote MCP servers via the Connectors UI.

1. Open Claude Desktop, then Settings → Connectors.
2. Click Add custom connector.
3. Paste the endpoint URL above as the server URL. Name it something like alpen.
4. Save and restart Claude Desktop if prompted.

On older Claude Desktop versions you'll edit ~/Library/Application Support/Claude/claude_desktop_config.json directly. See the docs at claude.ai for the JSON shape.

Claude.ai (web)

Available on Max, Team, and Enterprise plans.

1. In Claude.ai, open the connectors menu.
2. Add a custom connector with the endpoint URL above.
3. Approve and start a new chat. The Alpen tools will appear.

Cursor

1. Open Cursor settings, search for MCP.
2. Add a new server with the endpoint URL above.
3. Reload Cursor. Tools become available in agent mode.

Quick check

Confirm the server is reachable before wiring up a client:

# List all available tools
curl -X POST https://alpen-web.vercel.app/api/mcp \
  -H 'content-type: application/json' \
  -d '{"jsonrpc":"2.0","id":1,"method":"tools/list"}'

# Get the active testnet
curl -X POST https://alpen-web.vercel.app/api/mcp \
  -H 'content-type: application/json' \
  -d '{"jsonrpc":"2.0","id":2,"method":"tools/call","params":{"name":"get_network_info","arguments":{}}}'