sim-api

This MCP server exposes Sim blockchain APIs for both EVM (Ethereum-compatible) and SVM (Solana) data via an MCP endpoint. When running, the server listens on port 3000 and exposes the MCP endpoint at /mcp, which can be consumed by clients or integrated into Claude Desktop or other MCP-enabled tools. The EVM tools include getBalances for token balances, getEVMTransactions for transaction history, getTokenPrice for USD pricing, and methods to list supported chains for both transactions and token balances. The SVM tools provide getSVMBalances for Solana wallet balances and getSVMTransactions for Solana transaction history. To use, you run the server locally, obtain an API key for the Sim API, and configure your MCP client to point to the local endpoint (http://localhost:3000/mcp) with the appropriate environment variable (SIM_API_KEY) set for authentication.

Prerequisites:

• Node.js and npm or pnpm installed
• Access to the internet to install dependencies

Steps:

1. Clone the repository and install dependencies

git clone https://github.com/duneanalytics/sim-api-mcp.git
cd sim-api-mcp
pnpm install

2. Obtain a Sim API key:

• Get your API key from the Sim API Console (https://sim.dune.com).

3. Configure environment and start the server:

# Set your API key (use your actual key in place of YOUR_KEY)
export SIM_API_KEY=YOUR_KEY

# Start the MCP server
pnpm run start

4. Verify the server is running on port 3000 and the MCP endpoint is available at http://localhost:3000/mcp

Additional notes: The repository uses pnpm as the package manager, so ensure pnpm is installed and available in your environment.

Tips and notes:

• The MCP endpoint runs by default on port 3000; if you need to change it, modify the server configuration in the project startup script.
• Always secure your SIM_API_KEY; do not commit it to version control.
• When integrating with Claude Desktop or other MCP clients, you can reuse the same mcp-remote configuration pattern shown in the README, pointing at http://localhost:3000/mcp.
• If you encounter connectivity issues, verify that SIM_API_KEY is correctly exported in the environment where the MCP client runs, and ensure the server process has network access to the Sin API services.
• The available tools include EVM and SVM operations as listed in the README; you can extend or customize tool access as needed by adjusting the underlying MCP remote configuration.