
Indigo Mcp
io.github.IndigoProtocolPublished by GitHub account IndigoProtocolv0.4.2Updated Oct 24, 2026
Indigo Protocol MCP — iAsset prices, CDP analytics, stability pools, staking & governance
Overview
Lets an assistant read Indigo Protocol Cardano DeFi data and build unsigned transactions for CDPs, staking, stability pools, and redemption orders.
- What you can do
- Exposes roughly 69 tools covering iAsset and ADA/INDY prices, CDP and loan browsing, owner lookup, CDP health and liquidation-risk analysis, stability pool state, INDY staking positions, protocol analytics such as TVL and APR, governance polls, and the redemption order book. Write tools build unsigned CBOR transactions for opening, depositing to, withdrawing from, minting, burning, redeeming, freezing, merging, and liquidating CDPs, plus staking, stability pool requests, ROB positions, stableswap orders, and admin interest or price oracle feeds. It also proxies Steelswap swap estimates, Iris liquidity pools, Blockfrost balances, and IPFS storage.
- When to use it
- Useful when an assistant needs to inspect Indigo Protocol positions or protocol metrics on Cardano, or to prepare Cardano DeFi transactions for a user to sign. Read-only queries work without a Blockfrost key, so it can be added just for analytics.
- Requirements
- Local Node.js process installed via npm or run with npx; the setup command configures Claude Desktop, Claude Code, Cursor, or Windsurf. Optional environment variables include INDEXER_URL, CARDANO_NETWORK, MCP_TRANSPORT, PORT, and HOST. BLOCKFROST_API_KEY is required for write operations that build transactions. Optional X402_PRIVATE_KEY, PAYMENT_SERVER, X402_TESTNET, and X402_FACILITATOR_URL relate to payment flows. Network access to the Indigo analytics API and Blockfrost is needed.
Installation
In SourceWeft
- Open Indigo Mcp in the dashboard and add it to a workspace.
- Enable the server for the chats that should use its tools.
Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.
Other MCP clients
Follow the launch instructions in the repository.
README
Indigo MCP
[Smithery] [npm downloads] [Ask DeepWiki]
MCP server for Indigo Protocol — exposes Indigo iAsset data, prices, and CDP/loan analytics to LLM agents via the Model Context Protocol.
⚡ Quick Start — Full Cardano DeFi Stack
MCP Servers (75 tools)
AI Skills (13 skills) — Optional
The setup commands auto-configure Claude Desktop, Claude Code, Cursor, or Windsurf. No manual config editing needed.
Features
- Real-time iAsset prices (iUSD, iBTC, iETH, iSOL, iEUR, iJPY)
- ADA and INDY token price feeds
- CDP/loan browsing with pagination and filtering
- Owner lookup by payment key hash or bech32 address
- CDP health analysis with collateral ratio and liquidation risk status
- Stability pool state and account queries
- INDY staking positions and manager state
- Protocol analytics: TVL, APR rewards, DEX yields, aggregated stats
- Governance: protocol parameters, polls, temperature checks
- Redemption order book and queue aggregation
- DEX proxy: Steelswap swaps, Iris liquidity pools, Blockfrost balances
- CDP liquidation, redemption, freeze, and merge operations
- Leveraged CDP opening via ROB positions
- ROB (Redemption Order Book) position management
- Oracle interest rate feeding and initialization
- Stability pool request processing and cancellation
- Staking reward distribution
- Collector UTXOs, IPFS storage and retrieval
Hosted deployment
A hosted deployment is available on Fronteir AI.
Quick Start
Automatic Setup (Recommended)
Run the interactive setup to automatically configure your MCP client:
This will:
- Ask which client you're using (Claude Desktop, Claude Code, Cursor, Windsurf)
- Prompt for your Blockfrost API key
- Automatically update your config file
Manual Installation
Install globally:
Or run directly with npx (no install needed):
Docker
The image builds the server from source — no prior pnpm build needed, and no
dependency on any external build step:
It runs the HTTP transport on port 3000 (MCP_TRANSPORT=http is baked in), which
is what the Fly deployment uses.
HTTP Transport (Remote)
The server supports HTTP transport for remote/hosted deployments:
This starts an HTTP server with:
POST /mcp— MCP endpoint (Streamable HTTP with SSE)GET /health— Health check
Each client gets its own session: initialize returns an Mcp-Session-Id that
subsequent requests must send back. A client that restarts can simply
initialize again — existing sessions are unaffected and the server does not
need restarting. Bind address and port come from HOST and PORT (MCP_PORT
is accepted as an alias for PORT).
Configuration
Note:
BLOCKFROST_API_KEYis required for write operations (transaction building). Read-only tools work without it. Get a free key at blockfrost.io.
Claude Desktop
Add to ~/Library/Application Support/Claude/claude_desktop_config.json (macOS) or %APPDATA%\Claude\claude_desktop_config.json (Windows):
Standard config:
For nvm users (multiple Node versions):
If you use nvm and have multiple Node versions, you may need to specify the full path and set PATH explicitly:
Note: Replace
YOUR_USERNAMEand Node version with your actual values. Find your Node path withwhich npx.
Claude Code (CLI)
Add to ~/.claude/settings.json or .claude/settings.json in your project:
Cursor
Add to ~/.cursor/mcp.json (global) or .cursor/mcp.json (project-level):
Windsurf
Add to ~/.codeium/windsurf/mcp_config.json:
OpenClaw
Install Indigo skills for OpenClaw:
Skills are automatically configured — start using Indigo tools immediately.
Combined with Cardano MCP
For full Cardano DeFi capabilities, use both Indigo MCP and Cardano MCP together:
Any MCP-Compatible Client
Run the server directly via stdio:
Or install globally and reference the binary:
For any client that supports MCP over stdio, point it to the npx @indigoprotocol/indigo-mcp command with the environment variables above.
Available Tools
Asset Tools
CDP / Loan Tools
CDP Write Tools
Pyth-priced iAssets have a submission deadline. Every iAsset is currently priced through Pyth, and the on-chain feed validator only accepts a transaction for 280 seconds after the price update it embeds. Price-dependent write tools (
open_cdp,withdraw_cdp,mint_cdp,redeem_cdp,freeze_cdp,leverage_cdp,redeem_rob) therefore return asummary.pythblock with the price, its timestamp and asubmitBeforedeadline. If signing takes longer than that — a hardware wallet, or a human approving in a browser — rebuild the transaction rather than submitting a stale one. A price update that has already expired is rejected at build time with a retry hint.
CDP Mint/Burn Tools
CDP Liquidation & Redemption Tools
Leverage CDP Tools
Stability Pool Tools
Staking Tools
Stability Pool Request Tools
Staking Write Tools
Staking Reward Tools
Analytics & APR Tools
Governance Tools
Redemption & Order Book Tools
ROB Write Tools
DEX Proxy Tools
Collector & IPFS Tools
Interest Tools (v3)
Oracle / Pyth Tools (v3)
Stableswap Tools (v3)
Environment Variables
Example Queries
When connected to an LLM agent, you can ask natural language questions like:
- "What are the current prices of all Indigo iAssets?"
- "What is the price of iUSD right now?"
- "How much is ADA worth in USD?"
- "Show me all iETH CDPs"
- "What CDPs does this address own?" (paste a Cardano address)
- "Analyze the health of my CDPs" (with your address or payment key hash)
- "Are any of my positions at risk of liquidation?"
- "Show me the current stability pool state"
- "What are my stability pool deposits?" (with your address)
- "How much INDY am I staking?" (with your address)
- "What's the current TVL of Indigo?"
- "What APR can I earn on iUSD stability pool?"
- "What are the current governance protocol parameters?"
- "Show me the iUSD redemption queue"
- "Get a Steelswap estimate for swapping 100 ADA to iUSD"
- "What are the current DEX yields for iAsset pairs?"
Distribution
The server is published to three places, and they are not the same artifact.
The container image (Dockerfile) builds from source and is used by Fly and any
other container host. It does not consume .smithery/ output — that path is
Smithery-specific.
Cutting a release
- Merge the version bump (
package.json;SERVER_VERSIONis read from it) git tag vX.Y.Z && git push origin vX.Y.Z- CI publishes to npm, then to the MCP Registry (the registry verifies ownership
via the package's
mcpNamefield, so npm has to go first) - Verify against the registry, not the workflow:
npm view @indigoprotocol/indigo-mcp version fly deployfor the hosted HTTP endpoint, andpnpm smithery:publishfor Smithery
Development
Prerequisites
- Node.js >= 20 (the bundled
undicirequires theFileglobal, added in Node 20) - npm
Setup
Scripts
Project Structure
Testing via stdin
The server communicates over stdio using JSON-RPC. You can test tools directly:
x402 Payment Gating
Indigo MCP optionally gates tools behind per-call micropayments using the x402 protocol. Payment is disabled by default — set at least one wallet address to enable it.
How it works
Payment uses the split execution model — the same architecture as openMM-MCP:
- A tool is called (no payment header needed from the caller)
- The gate intercepts and contacts the settlement worker (
mcp.openmm.ioby default) - Worker responds
402with EIP-3009 requirements (amount, recipient, chain) - Gate signs locally using
X402_PRIVATE_KEY— the key never leaves this process - Gate retries with the signed payment → worker verifies on-chain, issues a JWT
- Gate verifies JWT locally, executes the original tool handler
- Settlement tx hash is injected into the tool response
This keeps process isolation clean: indigo-mcp never holds the recipient wallet — only the payer key. Verification and settlement are handled by the openmm.io proxy.
- Read tools (
get_tvl,get_asset_price, …) cost $0.001 USDC per call - Analysis tools (
analyze_cdp_health) cost $0.005 USDC per call - Write tools (
open_cdp,mint_cdp, …) cost $0.01 USDC per call
Environment variables
Split execution flow
When X402_PRIVATE_KEY is set, every paid tool call is handled transparently:
- Gate contacts
PAYMENT_SERVER(https://mcp.openmm.ioby default) - Signs EIP-3009 locally — the private key never leaves this process
- Proxy verifies on-chain, issues a short-lived JWT
- Gate verifies JWT, executes tool, injects settlement tx hash into response
If X402_PRIVATE_KEY is not set the gate is disabled and all tools execute without payment.
Local development
MCP client config with x402
Add the env block to whichever MCP config file your client uses:
Claude Code (~/.claude/settings.json):
Claude Desktop (~/Library/Application Support/Claude/claude_desktop_config.json):
Cursor / Windsurf — same env block applies to ~/.cursor/mcp.json or ~/.codeium/windsurf/mcp_config.json.
Set
X402_TESTNETtofalse(or omit it) for Base mainnet.
License
ISC
Source: README.md at commit de00632
Tools
0Version history
1- v0.4.2LatestSep 16, 2026
Score
50% of the applicable checks met
How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.
- Reached in the last 30 days25 pts
Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.
- Auth declared10 pts
Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.
- Tools listed15 pts
Answer tools/list without a credential, or ship a package that starts in a sandbox without one.
- DescriptionRequired15 pts
- Logo10 pts
- Documentation15 pts
- License10 pts