Skip to main content

​
Build Pipelines with Your AI Coding Agent

The Indexing Co MCP server connects AI coding agents to the Indexing Co API and live event stream. Describe your data needs in natural language, and the agent handles pipeline creation, transformation logic, testing, and deployment — no dashboard or config files required. Live Event Stream Preview — colorized terminal output showing USDC transfer events streaming in real-time

​
What You Get

​
Setup

​
1. Install the MCP Server

​
2. Add Your Credentials

Create ~/.indexing-co/credentials with your API key:
Sign up at accounts.indexing.co if you don’t have an API key yet.

​
3. Register with Your Agent

Install the skill to give Claude pipeline workflow knowledge — how to structure filters, write transformations, pick destinations, and debug delivery:

​
What You Can Do

Once set up, just describe what you want in natural language:
  • “Index all USDC transfers on Base to my Postgres database”
  • “Set up a webhook for Uniswap V3 swaps on Ethereum”
  • “Stream Aave supply events on Arbitrum so I can see them live”
The agent will walk through the full pipeline workflow: create a filter, write and test a transformation, set up the destination, deploy, and verify.

​
MCP Server Tools

The MCP server gives your agent direct access to the Indexing Co API:

​
Live Event Preview

For pipelines using the DIRECT adapter, you can stream events straight to your terminal with the preview CLI:
This renders a live, colorized stream of events as they flow through your pipeline — addresses in magenta, transaction hashes in blue, numbers in yellow, and nested objects indented with recursive colorization. Press Ctrl+C to see a summary with total event count, duration, and average throughput.

​
DIRECT Adapter Setup

To use the preview CLI, configure your pipeline with the DIRECT adapter:
The connectionUri is the channel name you pass to the preview CLI. Events are only sent when at least one subscriber is connected.
The DIRECT adapter can run alongside any other adapter. For example, you can stream to both Postgres and the preview CLI simultaneously by creating two pipelines with the same filter and transformation but different delivery configs.

​
Example Workflow

Here’s what a typical session looks like:
  1. You: “I want to track all USDC transfers on Base”
  2. Agent: Creates a filter with the Base USDC contract address
  3. Agent: Writes a transformation using utils.evmDecodeLogWithMetadata for Transfer events
  4. Agent: Tests the transformation against a recent block
  5. Agent: Deploys the pipeline with your chosen destination
  6. Agent: Backfills a few blocks and verifies data arrives
  7. You: “Stream the events so I can see them”
  8. Agent: Launches the preview CLI and triggers a backfill — live events appear in your terminal

​
Security

The MCP server runs locally — API credentials stay on your machine. The agent operates with the same permissions as your API key, so treat your credentials accordingly.

​
Resources