Skip to main content

​
Overview

The ACN MCP Server is a remote Model Context Protocol server hosted at mcp.acn.exchange. It exposes ACN’s capabilities as tools that any MCP-compatible agent can call natively. Instead of writing HTTP client code, your agent sees ACN services as tools it can invoke directly.

​
Configuration

Add the ACN MCP server to your agent’s MCP configuration: 
{
  "mcpServers": {
    "acn": {
      "type": "url",
      "url": "https://mcp.acn.exchange/mcp",
      "headers": {
        "x-acn-api-key": "acn_sk_your_api_key"
      }
    }
  }
}
For wallet-based authentication: 
{
  "mcpServers": {
    "acn": {
      "url": "https://mcp.acn.exchange/mcp",
      "headers": {
        "X-Wallet-Address": "0xYourAddress",
        "X-Wallet-Signature": "...",
        "X-Wallet-Timestamp": "...",
        "X-Wallet-Nonce": "..."
      }
    }
  }
}

​
Core Tools

These tools are always available:

​
acn_discover

Search the ACN marketplace for services.
ParameterTypeRequiredDescription
querystringNo*Natural language search query
categorystringNoFilter by category
tagsstring[]NoFilter by tags
max_price_per_callnumberNoMaximum price in USDC
limitnumberNoMax results (default: 10)

​
acn_providers

List all available providers on the network.
ParameterTypeRequiredDescription
categorystringNoFilter by category

​
acn_provider_detail

Get detailed information about a specific provider.
ParameterTypeRequiredDescription
provider_idstringYesThe provider’s unique ID

​
acn_balance

Check your current ACN balance. Requires authentication.

​
acn_call_history

View your recent API call history.
ParameterTypeRequiredDescription
limitnumberNoNumber of results (default: 10)
provider_idstringNoFilter by provider

​
acn_submit_payment

Submit a signed transaction to complete a payment challenge.
ParameterTypeRequiredDescription
call_idstringYesThe call ID from the payment challenge
signed_txstringYesThe signed transaction hex

​
Dynamic Provider Tools

In addition to core tools, the MCP server auto-generates tools for every provider endpoint in the registry. These tools are named: 
{provider_slug}__{endpoint_slug}
For example:
  • resend__send_email — Send an email via Resend
  • coingecko__get_price — Get crypto prices via CoinGecko
  • alchemy__get_block — Get block data via Alchemy
The parameters for each dynamic tool match the endpoint’s schema. Your agent can discover these tools and call them directly.

​
Payment Flow via MCP

When an agent calls a provider tool that requires payment:
  1. Agent calls a provider tool
  2. ACN returns a payment_required status with an unsigned transaction and call_id
  3. Agent uses the Wallet MCP Server to sign the transaction locally
  4. Agent submits the signed transaction via acn_submit_payment
  5. ACN verifies the payment, executes the call, and returns the result

​
Using with Claude Desktop

See Claude MCP Integration for a step-by-step setup guide.