mcp

This MCP server exposes Monorail's APIs to your MCP client, allowing you to request token information, balances, and trade quotes. It aggregates liquidity across multiple exchanges (11 exchanges) and covers a large catalog (7,000+ tokens), so you can surface accurate quotes and token data to your AI workflows without managing each exchange individually. The server's responses include quotes along with transaction data that you can pass to a wallet or trading flow; however, this MCP server does not implement wallet functionality or execute trades itself.

To use it in your MCP client, first ensure the server is running and reachable by your client. Then configure your MCP client to point to the provided server entrypoint (for example, the built index.js) so your prompts can invoke the server's methods for quotes, token info, and balances. The server will respond with structured MCP messages containing quote details and any required ancillary data to perform a trade externally if your client supports wallet actions.

Prerequisites:

• Node.js v14+ and npm installed
• Git installed

1. Clone the repository

git clone https://github.com/monorail-xyz/mcp-server.git monorail-mcp-server

2. Install dependencies

cd monorail-mcp-server
npm install

3. Build the project

npm run build

4. Run or integrate with your MCP client

• If you are running directly, start the server (adjust as needed for your environment):

node build/index.js

• To use with a client, reference the built entrypoint in your MCP configuration as shown in the example below:

{
  "mcpServers": {
    "monorail": {
      "command": "node",
      "args": ["C:\\path\\to\\build\\index.js"]
    }
  }
}

Notes:

• The server does not execute wallet transactions; it only provides quotes and token/balance data.
• Ensure network access to Monorail APIs if running behind a firewall or proxy.

Tips:

• If you encounter build issues, ensure dependencies are installed and your Node.js version is compatible with the project setup.
• The MCP server provides quotes with accompanying transaction data; you can wire this data into your wallet or trading interface outside of the MCP server.
• No wallet functionality is implemented in this server; use your own wallet integration to perform trades.
• When deploying, consider environment variables for API keys or rate limiting if you integrate with external services (not documented here).