mcp-atp

The MCP-ATP server implements IQ AI's Agent Tokenization Platform (ATP) as an MCP-enabled service. It exposes tooling to discover AI agents, inspect their statistics, track user token holdings, execute trades for agent tokens, and manage agent logs. Once the server is accessible to your MCP client, you can query for agent stats, pull portfolios, place buy/sell orders using IQ as the base currency, and add or retrieve logs for individual agents. The available tools (as documented in the MCP surface) cover agent discovery, portfolio management, trading, and log management, enabling LLMs to interact with ATP programmatically through the MCP protocol.

To use the server, configure your MCP client with the atp server entry and the appropriate environment variables. For example, provide your wallet private key (ATP_WALLET_PRIVATE_KEY) to authorize trading and position queries. If you build locally, you can point the MCP client to the built index.js file and supply additional config like ATP_API_KEY if required by specific ATP integrations. The server supports discovering agents, getting agent statistics, querying user positions, buying or selling agent tokens, and managing agent logs via the MCP tool interfaces.

Prerequisites:

• Node.js and npm/pnpm installed
• Access to a shell/terminal

Option A: Run without installing globally (recommended)

1. Ensure pnpm is installed: npm i -g pnpm
2. Run the MCP server via dlx (as configured in the MCP client): pnpm dlx @iqai/mcp-atp
3. Provide ATP_WALLET_PRIVATE_KEY in your MCP client configuration as needed to enable trading capabilities.

Option B: Build from source and run locally

1. Clone the repository: git clone https://github.com/IQAIcom/mcp-atp.git
2. Install dependencies and build: cd mcp-atp pnpm install pnpm run build
3. Run the built server (pointing to the built entry): node dist/index.js
4. In your MCP client, reference the local path to the built server as shown in the advanced configuration example (with ATP_WALLET_PRIVATE_KEY and optional ATP_API_KEY).

Notes:

• The ATP integration relies on wallet signing for trading operations. Keep private keys secure and rotate as needed.
• If using ATP_GET_AGENT_POSITIONS, ATP_BUY_AGENT, or ATP_SELL_AGENT tools, ATP_WALLET_PRIVATE_KEY is required.

Environment variables and configuration:

• ATP_WALLET_PRIVATE_KEY: Required for trading and position queries. Treat this as highly sensitive data.
• ATP_API_KEY: Optional API key for certain backend services. Only supply if required by your ATP setup.

Common issues:

• If the MCP client cannot reach the server, verify network access and that the command/paths in mcp_config are correct.
• When building from source, ensure the distribution path in the client matches dist/index.js (or the actual built entry point).
• For security, avoid exposing private keys in shared configurations; use secret management or environment isolation where possible.