awesome-radix s

Awesome Radix MCP Servers is a curated collection of MCP servers designed to integrate with the Radix ecosystem. Each server in this collection exposes a Model Context Protocol (MCP) interface that enables external tooling and services to interact with Radix-based contexts, exchange SBOR-encoded data, and leverage platform-specific features. The servers are organized under names such as Attos World, SBOR EZ Mode, and Astrolescent, each offering its own integration points and endpoints. You can run any of these servers locally or in your environment and connect to them using MCP clients or tooling that supports the protocol. Typical usage involves starting the server, configuring environment variables as needed (such as ports or API keys), and then sending MCP requests to the server's endpoints to publish, query, or subscribe to context data relevant to the Radix ecosystem.

Prerequisites:

• Node.js (LTS version) and npm installed on your machine
• Basic familiarity with running Node.js applications

Installation steps:

1. Clone the repository containing the Awesome Radix MCP Servers: git clone https://github.com/your-org/xstelea-awesome-radix-mcp-servers.git
2. Navigate to the project directory: cd xstelea-awesome-radix-mcp-servers
3. Install dependencies (per server, if applicable): npm install
4. Create or configure any required environment variables per server (as shown in mcp_config):
   • PORT: Port number for the server (default 3000 if not specified)
5. Start the desired MCP server(s):
   • Attos World: node path/to/attos-world-server.js
   • SBOR EZ Mode: node path/to/sbor-ez-mode-server.js
   • Astrolescent: node path/to/astrolescent-server.js
6. Verify the servers are running by hitting their endpoints or checking logs, then connect your MCP client to the running server(s) using the MCP protocol.

Tips and caveats:

• The provided server names map to individual MCP implementations. Ensure you adjust the paths in mcp_config to point to the actual server entry scripts in your environment.
• If you are running multiple servers, consider assigning distinct ports via the PORT environment variable to avoid conflicts.
• Some servers may require additional configuration such as API keys or platform-specific endpoints; consult the respective server documentation for details.
• If you encounter connectivity issues, verify network access, firewall rules, and that the MCP clients are using the correct protocol version supported by each server.
• For debugging, run servers in verbose mode or inspect logs for MCP request/response traces to diagnose formatting or compatibility problems.