Get started

Chain.Love MCP Gateway

One MCP gateway for Web3 agents.

Discover services, connect tools, and execute downstream MCP calls through one Chain.Love endpoint.

Get startedView flow

Agent path

  1. 1

    discover

    Find the right chain, category, and service from the registry.

  2. 2

    connect

    Attach session-scoped credentials or select a saved connection.

  3. 3

    inspect

    List the tools exposed by the downstream MCP.

  4. 4

    execute

    Call the downstream tool and return the result to the agent.

What it does

Discovery, registry search, and MCP execution in one flow.

Discovery

Discover services

Start with current networks and service categories instead of hardcoded provider lists.

Registry

Search the registry

Find Web3 infrastructure, APIs, docs, and MCP-ready services through one registry surface.

Execution

Run MCP tools

Connect downstream MCPs, inspect available tools, and call them through the gateway session.

Runtime flow

From an agent request to a downstream tool result.

Agent

Claude, Cursor, Codex, or another MCP client

Chain.Love MCP Gateway

Auth, registry discovery, and execute dispatch

Chain.Love Registry

Release-backed chains, categories, and services

Downstream MCP

GitHub, Blockscout, docs, APIs, or other tool servers

Tool Result

Structured response returned to the same session

Why it matters

A predictable path for agent workflows.

No hardcoded service maps

Agents ask the gateway for current chains and categories before they search, so stale provider lists do not leak into the workflow.

One runtime for discovery and tools

The same MCP endpoint handles registry lookup, connection selection, downstream validation, tool listing, and tool calls.

Credentials stay scoped

Public discovery, gateway authentication, and downstream credentials are handled as separate concerns.

Access

Public discovery, authenticated execution.

Registry discovery can stay open while tool execution remains scoped through gateway tokens and downstream credentials.

  • Public registry discovery can expose service metadata without granting tool execution.
  • Gateway execution can run against public services without a Chain.Love token.
  • Private downstream MCP credentials can be passed with x-chainlove-cred-<credentialKey> headers.
  • Saved connections stay scoped to the owner, and stored token values are not returned.

Setup

Add Chain.Love Gateway to your MCP config.

Use the hosted gateway URL in your MCP client. Add optional downstream credentials only when a private MCP requires them, using x-chainlove-cred-<credentialKey> headers.

Config

mcp_config.json

{
  "mcpServers": {
    "chainlove-gateway": {
      "url": "https://app.chain.love/mcp",
      "headers": {
        "x-chainlove-cred-<credentialKey>": "<credentialValue>"
      }
    }
  }
}

Try it with your agent

Bring Web3 discovery into the MCP workflow.

Get started