web3 -hub

Web3 MCP Hub serves as a centralized registry for MCP servers focused on Web3, blockchain, and decentralized applications. It aggregates production-ready MCP servers and provides ready-made configuration examples so developers can quickly connect their MCP clients to a broad set of capabilities, from multi-chain data access to on-chain actions. The hub content emphasizes categorized servers (by ecosystem and function) and includes configuration samples that show how to enable tooling across networks. To use the hub, you typically add MCP server definitions to your client configuration, referencing a package that exposes the MCP server, and specifying any needed environment variables such as API keys. For example, you can point your MCP client to a server such as the Web3 MCP server, enabling Ethereum, Solana, and Bitcoin tooling through environment flags. You can then query cross-chain data, perform transactions, or retrieve on-chain state via the MCP protocol.

The hub also demonstrates concrete configuration patterns, including how to structure the mcpServers object with command, args, and env fields. Tools available via the included servers range from multi-chain balance and transaction queries to NFT data access, on-chain governance interactions, and DeFi protocol queries. By following the examples, you can extend your client setup to incorporate additional servers from the registry and tailor access with environment variables for API keys or feature toggles.

Prerequisites:

• Node.js 18+ or Python 3.10+ (depending on how you deploy MCP servers)
• npm or yarn
• Git (optional but recommended for cloning repositories)

Installation steps:

1. Install Node.js and npm from the official website or using your system package manager.
2. Clone the hub repository (or install via your chosen distribution method):

git clone https://github.com/rudazy/web3-mcp-hub.git
cd web3-mcp-hub

3. Install dependencies:

npm install

4. Start the hub registry (or run in your preferred environment). If the repo provides a start script, use it; otherwise a typical command is:

npm run start

5. Verify the registry is running and accessible, then add MCP server configurations to your client using the examples provided in the registry.

If you are deploying a specific MCP server locally, follow the respective server’s installation guide in the registry, then point your client to the server’s endpoint as described in its configuration snippet.

Notes and tips:

• When wiring up servers, ensure your API keys (if required) are kept secure and provided via the env field rather than hard-coded.
• The registry examples often show enabling toolsets per network (e.g., ENABLE_ETHEREUM_TOOLS, ENABLE_SOLANA_TOOLS). Adjust these flags to match the networks you intend to use.
• Validate MCP client version compatibility with the server you deploy; MCP protocol features may evolve and require corresponding client updates.
• If you encounter network or authentication errors, check environment variable names and values, and confirm network access from your deployment environment.
• Use the Quick Start sample to customize the mcpServers block for your own setup, including adding additional servers as needed.
• For large-scale deployments, consider orchestrating multiple MCP servers behind a load balancer or a gateway if supported by your MCP client.