mcp-gateway
MCP server that enables AI agents to simulate EVM bytecode and probe capabilities, serving as a gateway to an Ethereum execution engine.
README
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 (stateless EthereumJS)
| Layer | This repo | Role |
|---|---|---|
| Gateway | mcp-gateway |
MCP transport, tool registry, payments seam (later) |
| Engine | mcp-execution-engine |
Pure simulation core — no HTTP or MCP |
Docs: mcp-docs.feelyourprotocol.org
Tools (v0.1.0)
| MCP tool | Shape | Status |
|---|---|---|
describe_capabilities |
probe | Shipped (stdio) |
simulate_evm_bytecode |
simulate | 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 (30 tests)
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-EVM v0.1.0 ready — tools: describe_capabilities, simulate_evm_bytecode
If you only see describe_capabilities in that line, the running binary is stale.
JSON schemas
Machine-readable tool inputs (also published on mcp-docs):
License
MIT
Recommended Servers
playwright-mcp
A Model Context Protocol server that enables LLMs to interact with web pages through structured accessibility snapshots without requiring vision models or screenshots.
Audiense Insights MCP Server
Enables interaction with Audiense Insights accounts via the Model Context Protocol, facilitating the extraction and analysis of marketing insights and audience data including demographics, behavior, and influencer engagement.
Magic Component Platform (MCP)
An AI-powered tool that generates modern UI components from natural language descriptions, integrating with popular IDEs to streamline UI development workflow.
VeyraX MCP
Single MCP tool to connect all your favorite tools: Gmail, Calendar and 40 more.
graphlit-mcp-server
The Model Context Protocol (MCP) Server enables integration between MCP clients and the Graphlit service. Ingest anything from Slack to Gmail to podcast feeds, in addition to web crawling, into a Graphlit project - and then retrieve relevant contents from the MCP client.
Kagi MCP Server
An MCP server that integrates Kagi search capabilities with Claude AI, enabling Claude to perform real-time web searches when answering questions that require up-to-date information.
Neon Database
MCP server for interacting with Neon Management API and databases
Exa Search
A Model Context Protocol (MCP) server lets AI assistants like Claude use the Exa AI Search API for web searches. This setup allows AI models to get real-time web information in a safe and controlled way.
Qdrant Server
This repository is an example of how to create a MCP server for Qdrant, a vector search engine.
E2B
Using MCP to run code via e2b.