titan-builder-mcp

  _   _ _                   _           _ _     _
 | |_(_) |_ __ _ _ __      | |__  _   _(_) | __| | ___ _ __
 | __| | __/ _` | '_ \ ____| '_ \| | | | | |/ _` |/ _ \ '__|
 | |_| | || (_| | | | |____| |_) | |_| | | | (_| |  __/ |
  \__|_|\__\__,_|_| |_|    |_.__/ \__,_|_|_|\__,_|\___|_|
                                           _ __ ___   ___ _ __
                                          | '_ ` _ \ / __| '_ \
                                          | | | | | | (__| |_) |
                                          |_| |_| |_|\___| .__/
                                                         |_|

Rust MCP server for Titan Builder — bring Ethereum block builder capabilities to AI coding agents.

The first MCP (Model Context Protocol) server for an Ethereum block builder. Enables AI agents like Claude Code and Cursor to interact with Titan Builder's MEV infrastructure directly — send bundles, debug failures, submit transactions, and more.

Highlights

• Enhanced Bundle Tracing — AI-ready diagnostic analysis on top of titan_getBundleStats — see below
• 5 MCP tools mapping to Titan Builder's complete API surface
• Single binary — zero runtime dependencies, compiled Rust
• Regional endpoints — US, EU, Asia for minimal latency

Architecture

Quick Start

Install:

cargo install titan-builder-mcp

Configure (Claude Code ~/.claude/settings.json):

{
  "mcpServers": {
    "titan-builder": {
      "command": "titan-builder-mcp",
      "env": {
        "TITAN_RPC_URL": "https://us.rpc.titanbuilder.xyz"
      }
    }
  }
}

Use: Once configured, your AI agent can send bundles, check bundle status, submit transactions, and debug failures through natural language.

Enhanced Bundle Tracing

The core feature. When your bundle fails, you shouldn't have to guess why.

Titan Builder provides Bundle Tracing via titan_getBundleStats — returning status codes, builder payment data, and error details. Our MCP server adds an AI-ready diagnostic layer on top: root cause analysis, actionable fix suggestions, and payment flags.

Without Enhanced Bundle Tracing

Raw API response — you see what happened, but not why or what to do:

{
  "status": "SimulationFail",
  "builderPayment": "0",
  "builderPaymentWhenIncluded": "0",
  "error": "BundleRevert. Reverting Hash: 0xa1b2c3d4e5f6...789"
}

With Enhanced Bundle Tracing

Same response + structured diagnostic analysis:

## Raw Response
{
  "status": "SimulationFail",
  "builderPayment": "0",
  "builderPaymentWhenIncluded": "0",
  "error": "BundleRevert. Reverting Hash: 0xa1b2c3d4e5f6...789"
}

## Analysis
Status: SimulationFail
Root cause: Transaction 0xa1b2c3d4e5f6...789 reverted during top-of-block simulation.

Suggestions:
- Add 0xa1b2c3d4e5f6...789 to revertingTxHashes if this revert is acceptable
- Verify the transaction succeeds via estimateGas against current state
- Ensure builder payment (post-bundle balance - pre-bundle balance) is > 0

What it analyzes

This is pure analysis — no additional API calls. It runs entirely on the response data from titan_getBundleStats.

Tools

Bundle Status Reference

Configuration

Regional Endpoints

Building from Source

git clone https://github.com/VPC-byte/titan-builder-mcp.git
cd titan-builder-mcp
cargo build --release

Related

• titan-builder-skill — Claude Code skill for MEV development assistance and bundle debugging

License

MIT