Skip to content

ERI MCP Server

The Model Context Protocol (MCP) delivery interface for ERI signals. Replaces the need for custom software surfaces by delivering signal data directly into AI agents, customer workflows, and internal systems via a standardized protocol.

Why MCP-First

eco|monetize's default delivery mechanism for all platform outputs is MCP server integration — not custom dashboards or portals. MCP allows: - Signal data available in any MCP-compatible AI client (Claude, etc.) - Customer integration without custom engineering - Internal agent consumption of live signal data - Standardized, versioned API surface

Delivery Phases

Phase Scope Target
Phase 1 Spec + reference implementation 2026-05-19
Phase 2 Wire existing signal sources (Signal Pipeline output) TBD
Phase 3 Webhook push layer (real-time signal delivery) TBD

Signal Delivery Model

ERI Signal Pipeline
       ↓
ERI MCP Server (v1)
       ↓
┌──────────────────────────────────┐
│ Claude (internal agents)          │
│ Customer AI workflows             │
│ Partner integrations              │
│ Assessment delivery platform      │
└──────────────────────────────────┘

Assessment Delivery

The MCP server is also the target delivery mechanism for Assessment outputs — Ecosystem Revenue Architecture Assessment™ results delivered as structured MCP responses rather than PDF/email.

Current State (2026-04-23)

  • Mission M-2026-0421-eri-mcp-server-v1 in Decompose phase
  • Phase 1 spec authoring in progress
  • Reference implementation pending spec completion