armor-crypto

Armor Crypto MCP provides a unified interface for interacting with the Armor Crypto ecosystem through AI agents. It exposes tools for wallet management, token swaps, transfers, and advanced trading automations like DCA, stop loss, and take profit across multiple blockchains (starting with Solana in alpha and expanding to Ethereum-compatible chains). The MCP server is designed to be consumed by agent frameworks via the uvx-based runner, enabling your agent to perform wallet operations, execute swaps, initiate and monitor trades, and access structured market data and token information through a single, cohesive API.

To use it, configure the MCP server using your API key, then integrate the provided MCP section into your agent or automation framework (Claude Desktop, Cline, n8n, etc.). Once configured, you can invoke the MCP endpoints to manage wallets, perform cross-chain interactions, and automate complex strategies such as DCA with scheduled orders or conditional take-profit logic. The setup guide in the README demonstrates how to point tools at the Armor Crypto MCP and securely provide the required API key for authentication.

Prerequisites:

• Python installed (3.8+ recommended)
• Access to uvx runner (Python package)

Installation steps:

1. Install the uv package (uvx runner) globally:

pip install uv

2. Ensure you have Python 3.x available and can run uvx commands. Verify installation:

uvx --version

3. Prepare your Armor API key. You’ll need to provide it via the environment variable ARMOR_API_KEY when launching the MCP server.

4. Run the Armor Crypto MCP server using the configuration shown in the README (adjust the key placeholder):

ARMOR_API_KEY=<YOUR_API_KEY> uvx armor-crypto-mcp@latest --version

5. Integrate with your agent or automation framework by including the armor-crypto-mcp section in your config as demonstrated in the project README.

Tips and notes:

• The MCP currently requires an Armor API key to access capabilities. Keep your key secure and avoid exposing it in public repos.
• If you are migrating or adding support for additional blockchains, monitor the alpha/beta status as features expand over time.
• Environment variables can include other config flags as needed by your agent; ensure the agent environment is correctly loaded before starting the MCP.
• When deploying in production, consider rotating API keys and restricting access to the MCP runner only to trusted agents.
• If you encounter issues with uvx execution, verifying the Python environment and PATH can resolve common invocation errors.
• The provided example config uses the mcpServers key armor-crypto-mcp; you can adapt the server name to your naming conventions if needed.