Connect

The server is live

6 October 2026. The URL below is open — free, no wallet, no API key. Add it, then ask the first question on this page. Follow X @FeelEthereum for what ships next.

One URL, no wallet, no API key. Add it to your agent, then ask a question in plain language.

Live endpoint

https://mcp.feelyourprotocol.org/mcp

Cost now

Free — full Glamsterdam hardfork

Auth

None — no wallet, no API key

Scope

Hosted product only, not a self-host guide

For browser learning, use feelyourprotocol.org. Using the hosted server means you accept the short Terms.

Add the server to your agent

Pick your client. Each tab has the shortest path for that client.

Add to Cursor

Opens Cursor and asks before installing. Prefer to edit the file yourself? Add this to your user mcp.json (Cursor Settings → MCP):

json

{
  "mcpServers": {
    "feel-your-protocol": {
      "url": "https://mcp.feelyourprotocol.org/mcp"
    }
  }
}

Then restart Cursor or reload MCP servers. You should see six tools. Remote HTTP MCP needs a recent Cursor build.

Claude Code — one command:

bash

claude mcp add --transport http feel-your-protocol https://mcp.feelyourprotocol.org/mcp

Claude Desktop and claude.ai — add the server as a custom connector, not in the config file:

1. Open Customize → Connectors and choose Add custom connector.
2. Name it feel-your-protocol and paste the URL below.
3. Leave authentication empty — the server needs no key.

url

https://mcp.feelyourprotocol.org/mcp

Claude connects to remote servers from Anthropic’s cloud, and custom connectors depend on your plan. Do not put a url entry into claude_desktop_config.json — that file is for local servers only.

One command (works for the Codex CLI, IDE extension, and desktop app, which share config):

bash

codex mcp add feel-your-protocol --url https://mcp.feelyourprotocol.org/mcp

Or add this to ~/.codex/config.toml (or a trusted project’s .codex/config.toml):

toml

[mcp_servers.feel-your-protocol]
url = "https://mcp.feelyourprotocol.org/mcp"

Any host that supports remote MCP over HTTP can use these values:

Field	Value
URL	https://mcp.feelyourprotocol.org/mcp
Transport	Streamable HTTP
Auth at launch	none

Config formats differ per host, so check your client’s MCP documentation for where these go.

After you connect — try this first

Ask your agent:

Amsterdam

Send 1 wei to an empty account under Amsterdam and tell me the gas the wallet would need.

Look forgasUsed near 204,600, with txStateGas near 183,600

Agent will likely call run_transactionEIP-8037 →

That exercises first-touch state gas (EIP-8037) without you naming tools or JSON fields. Then browse Amsterdam now for more prompts.

After connect, prefer natural-language questions. The agent should call the server’s generic tools (run_bytecode, run_transaction, run_block, …) — you do not need to memorize them. Optional compare: ask for the same question on Fusaka then Amsterdam and diff gas or receipts.

If it does not work

Symptom	Try this
No tools show up	Restart the client or reload MCP servers, then check that the URL ends in /mcp.
Connection error	Update your client — remote HTTP MCP needs a recent build — and check that the URL ends in /mcp.
Claude does not list the server	Add it as a custom connector under Customize → Connectors, not in the local config file.
The agent answers without calling a tool	Ask it to run the simulation on the MCP server, and name the fork (Amsterdam or Fusaka).

What the server exposes

You get probe + run + artifact tools covering Amsterdam and the earlier fork lineage. Machine-readable schemas live under Reference → Tool schemas. Human “what can I ask?” lives on What you can ask.

Connect Changelog

Connect Changelog

1. v0.162026-10-06Hosted endpoint is live. The page is connect-and-ask, not a countdown.
2. v0.152026-10-06Launch polish — endpoint card, client tabs with install link and one-line commands, troubleshooting table.
3. v0.142026-10-01Cursor, Claude, Codex, and generic HTTP MCP setup; first-test prompt; launch still pending.
4. v0.132026-10-01Launch connect is free. Client config still lands with the endpoint.
5. v0.122026-09-16Example prompt for a generic Glamsterdam run with no EIP named.
6. v0.102026-09-08Added run_transaction; renamed run_evm_bytecode → run_bytecode.
7. v0.92026-09-02Launch week countdown — 5–9 Oct 2026 target; link to roadmap launch page.
8. v0.72026-08-31Not publicly launched — reframe page as developer early access; point most users to website explorations.
9. v0.62026-08-27Two live tools — compare_evm_variants removed.
10. v0.52026-08-27Third live tool: compare_evm_variants; catalog is EIP-8024 only.
11. v0.42026-07-22Local stdio gateway live — Cursor config, tool list, restart notes, agent guidance.
12. v0.32026-07-20Split from overview — connection placeholder under use/.