Back to MCP Servers
🧩

byte-protocol MCP Server

API key required

PayPerByte — per-byte data for AI agents: x402 USDC on Base, EIP-712-attested. No token.

To add byte-protocol to Claude, run the install command below or copy the ready-made config for Claude Code, Claude Desktop, Cursor and VS Code further down. Restart your client after adding it and its tools show up in your next conversation. It needs 3 environment variables, listed below.

AIDevToolsData

Install

npx -y byte-mcp-server@0.13.0

Environment variables

PRIVATE_KEYSet in your MCP config
RPC_URLSet in your MCP config
BYTE_GATEWAY_ATTESTERSet in your MCP config

Install with your client

Terminal
claude mcp add byte-protocol --env PRIVATE_KEY=<YOUR_PRIVATE_KEY> --env RPC_URL=<YOUR_RPC_URL> --env BYTE_GATEWAY_ATTESTER=<YOUR_BYTE_GATEWAY_ATTESTER> -- npx -y byte-mcp-server@0.13.0

Run this in a terminal to add the server to Claude Code.

What this does

byte-protocol exposes a set of tools to Claude over the Model Context Protocol. After you add it to claude_desktop_config.json (snippet above) and restart Claude Desktop, those tools become callable inside any conversation.

Requirements

This server needs the following environment variables to be set before it can run:

PRIVATE_KEY
RPC_URL
BYTE_GATEWAY_ATTESTER

Set these via the env object in your MCP config (see claude_desktop_config.json snippet above).

Frequently asked questions

How do I install byte-protocol?

Run the Claude Code command in the install section to add byte-protocol to Claude Code, or copy the ready-made config for your client from the install section on this page. Restart your client afterwards and the tools appear in your next conversation.

Which clients work with byte-protocol?

This page carries setup and config for Claude Code, Claude Desktop, Cursor and VS Code. Any other MCP client that accepts a standard server config can connect to byte-protocol as well.

Does byte-protocol need an API key?

Yes. Before it can run, set these environment variables: PRIVATE_KEY, RPC_URL, BYTE_GATEWAY_ATTESTER. They go in the env block of your MCP config.

Imported from the Official MCP Registry. The details above come from the registry entry; the maker can claim this listing to correct them, add docs, and see its traffic.

Is this your MCP server?

Claim this listing to see its traffic, fix details yourself, and skip the review queue on future updates.

Listed on clauderules.net

Add this badge to your README

Show visitors this server is listed in the ClaudeRules directory. The badge links straight to this listing.

Markdown
[![Listed on clauderules.net](https://clauderules.net/api/badge/io-github-0rkz-byte-protocol)](https://clauderules.net/mcp/io-github-0rkz-byte-protocol)
HTML
<a href="https://clauderules.net/mcp/io-github-0rkz-byte-protocol" target="_blank" rel="noopener noreferrer"><img src="https://clauderules.net/api/badge/io-github-0rkz-byte-protocol" alt="Listed on clauderules.net" /></a>