mcp-gateway
Provides tools for running EVM bytecode in a simulated Ethereum execution environment, enabling agents to test and execute smart contract bytecode.
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@mcp-gatewaysimulate EVM bytecode for a simple transfer"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
mcp-gateway
MCP server gateway for Feel Your Protocol — exposes the mcp-execution-engine to AI agents over stdio (local) and HTTP (later).
Repo: github.com/feelyourprotocol/mcp-gateway · Release: v0.1.0 (stdio, local agents)
Architecture
Agent (Cursor, Claude Desktop, …)
→ MCP stdio transport
→ mcp-gateway (tools + TaskProcessor)
→ mcp-execution-engine (isolated EthereumJS lab)Layer | This repo | Role |
Gateway |
| MCP transport, tool registry, payments seam (later) |
Engine |
| Pure simulation core — no HTTP or MCP |
Docs: mcp-docs.feelyourprotocol.org
Related MCP server: multivon-mcp
Tools (v0.1.0)
MCP tool | Shape | Status |
| probe | Shipped (stdio) |
| simulate | Shipped (stdio) |
| transaction | Shipped (stdio) |
Local development
Clone the execution engine as a sibling directory (required — gateway depends on file:../mcp-execution-engine):
git clone https://github.com/feelyourprotocol/mcp-execution-engine.git
git clone https://github.com/feelyourprotocol/mcp-gateway.git# From mcp-execution-engine
npm ci && npm run build
# From mcp-gateway
npm ci
npm run test:ci # build + vitest
npm run build && npm start # stdio MCP server (for agent config)Cursor / Claude Desktop
{
"mcpServers": {
"feel-your-protocol": {
"command": "node",
"args": ["/absolute/path/to/mcp-gateway/dist/index.js"]
}
}
}Build first (npm run build). Use an absolute path to dist/index.js.
After pulling or changing gateway code: run npm run build again, then restart the MCP server in Cursor (Settings → MCP → restart feel-your-protocol, or reload the window). Cursor caches the tool list from the running process — it will not pick up new tools until restart.
On startup the server logs to stderr (visible in MCP logs):
[fyp-mcp] FeelYourProtocol v0.1.0 ready — tools: describe_capabilities, run_bytecode, run_transactionIf you only see one tool in that line, the running binary is stale.
JSON schemas
Machine-readable tool inputs (also published on mcp-docs):
License
MIT
Lab host
Merges to main run .github/workflows/deploy.yml (rsync production tree to the AWS lab; engine sibling is not overwritten). Ops and SSH cutover: private server-config aws/hosts/mcp-lab/SETUP-CD.md.
This server cannot be deployed
Maintenance
Related MCP Connectors
MCP server for building and testing AI agents with multi-model experimentation and insights.
Self-hosted MCP server: 26 deterministic dev, security, and EVM tools.
MCP server for AI agents to plan, verify, and deploy Cloudflare-native apps.
MCP server connecting AI agents to non-custodial staking data across 130+ networks.
Related MCP Servers
AlicenseCqualityCmaintenanceAn MCP server providing unified access to blockchain operations, bridging, swapping, and crypto trading strategies for AI agents.37179GPL 3.0
multivon-mcpofficial
AlicenseAqualityAmaintenanceMCP server that gives AI coding agents direct access to evaluation tools.23Apache 2.0- AlicenseNot gradedqualityDmaintenanceAn MCP server that bridges AI models with Ethereum blockchains via all JSON-RPC calls, enabling natural language queries for block numbers, balances, transactions, and smart contract data.4 npm21MIT
- AlicenseNot gradedqualityDmaintenanceMCP server providing AI assistants with tools for advanced EVM smart contract analysis, including proxy detection, implementation resolution, and security analysis.1MIT