Discover, evaluate, and subscribe to Byte Protocol data feeds. 10 tools, zero API keys.
Discover, evaluate, and subscribe to Byte Protocol data feeds. 10 tools, zero API keys. Exposed over MCP by the byte mcp server, that capability becomes something an assistant can invoke while it works, not something you go and do afterwards.
Wire it into your MCP client (Claude Desktop config below), then your agent can:
You will need 4 environment variables: PRIVATE_KEY, RPC_URL, INDEXER_URL, BYTE_GATEWAY_URL. The server will not start without them, which is usually why the tools fail to appear on a first run. Keep credentials in your client's env block or a secrets manager rather than in a file you might commit.
The server ships on npm as byte-mcp-server, so your MCP client can launch it on demand — there is no separate build step. Add the server block to your client's configuration, restart it, and the tools register themselves.
This sits in the developer tooling group, where several servers overlap in what they claim to do but differ sharply once you actually set them up. It is maintained by 0rkz; worth a glance at recent repository activity before you build anything load-bearing on it.
We check each listing at SyncDev against the project's documentation before it goes live — if something here drifts out of date, it is a bug worth reporting.
{
"mcpServers": {
"payperbyte": {
"command": "npx",
"args": ["-y", "byte-mcp-server"],
"env": {
"PRIVATE_KEY": "0x...",
"RPC_URL": "https://sepolia-rollup.arbitrum.io/rpc",
"INDEXER_URL": "http://localhost:8080"
}
}
}
}Configuration as documented by the project. Restart the client after saving.
| Variable | Description | Required |
|---|---|---|
| PRIVATE_KEY | Credential the server authenticates with. | Yes |
| RPC_URL | Endpoint or connection string the server talks to. | Yes |
| INDEXER_URL | Endpoint or connection string the server talks to. | Yes |
| BYTE_GATEWAY_URL | Endpoint or connection string the server talks to. | Yes |
Kill hallucinated APIs — version-accurate, up-to-date library documentation injected straight into context.
Microsoft's official browser automation server — drive a real browser through the accessibility tree, no screenshots needed.
GitHub's official server — repos, issues, pull requests, Actions and code security, straight from your assistant.
Issue tracking at the speed of conversation — Linear's official hosted server with OAuth and zero install.
Local repository surgery — status, diffs, commits, branches and history for any repo on disk.
Timezone sanity for AI — current time anywhere and correct conversions, without the model doing date math.