mcp

This Injective MCP Server exposes a comprehensive set of tools to interact with the Injective chain via MCP calls. It includes wallet management (generate, import, list, remove), market and account queries (list markets, get prices, balances, positions, and token metadata), and trading capabilities (open/close positions, both with standard Cosmos signing and EIP-712 Ethereum signing, as well as limit orders). It also supports transfers to other addresses, subaccount deposits and withdrawals, multi-chain bridging through Peggy and deBridge, and raw EVM transaction broadcasting on Injective EVM. Connect the MCP server to a Claude MCP client (Desktop or Code) and invoke these tools using natural language prompts that map to the available tool calls. The server maintains encrypted key storage locally and uses on-chain data to respond with up-to-date market and account information.

Typical usage flow: connect to Claude, list markets, check prices, view balances, deposit into a trading subaccount, open a position (or a limit order), monitor open orders or positions, and bridge tokens if needed. For bridging, you can obtain deBridge quotes and then execute the bridge through the corresponding tools. For EVM interactions, you can broadcast raw transactions through evm_broadcast.

To get started, ensure you point Claude at the running MCP server and provide any required environment configuration (for example, INJECTIVE_NETWORK) so the server communicates with the desired Injective network (mainnet or testnet).

Prerequisites:

• Node.js (LTS) installed on your machine
• npm (comes with Node.js)
• Access to the repository containing the MCP server code

Installation steps:

1. Clone the repository: git clone https://github.com/your-org/injective-mcp-server.git cd injective-mcp-server

2. Install dependencies: npm install

3. Build the MCP server (if a build step is provided): npm run build

4. Run the MCP server (pointing to the built server path used in mcp_config): node dist/mcp/server.js

5. Connect Claude (Desktop or Code) by adding the MCP server configuration as described in the readme, ensuring INJECTIVE_NETWORK is set to the desired environment (mainnet or testnet).

Notes:

• If you run in a development environment, you might use a local path for the server.js in mcp_config. Adjust the path accordingly.
• Make sure any required environment variables (e.g., INJECTIVE_NETWORK) are configured wherever the MCP server is launched.

Tips and common issues:

• Private keys are stored encrypted on disk and are never exposed to Claude. Be mindful that wallet passwords may appear in MCP client logs when passed as tool parameters.
• The INJECTIVE_NETWORK variable selects mainnet or testnet; ensure this matches your intended deployment to avoid cross-network issues.
• If you encounter path issues for the server.js, verify that the build step outputs to dist/mcp/server.js as expected by the mcp_config.
• For performance, consider running the MCP server with adequate CPU/RAM and network access to fetch market data and broadcast transactions promptly.
• When testing on testnet, use testnet faucet links and testnet tokens to avoid risking real funds.
• Review the architecture diagram in the repository to understand where each feature (markets, accounts, trading, evm, bridges) is implemented for advanced customization.