Skip to main content
Looking for an open-source, self-hosted alternative to MCPcat? mcpeye is product analytics and observability for MCP servers that you run entirely on your own infrastructure — no SaaS, no sending your agents’ raw intent data to someone else’s cloud.
In one line: MCPcat is closed-source and hosted; mcpeye is open-source (MIT) and self-hosted, and its hero feature — the Intent Gap Report — tells you not just what happened, but what to build next.

​
mcpeye vs MCPcat at a glance

mcpeyeMCPcat
LicenseOpen source (MIT)Closed source
HostingSelf-hosted (docker compose up)Hosted SaaS only
Your data leaves your stackNeverSent to their cloud
MCP session replay✅✅
Agent-goal analytics✅✅
Intent Gap Report (build-next roadmap)✅⚠️ partial
Missing-capability capture✅❌
SDKsTypeScript, Python, Ruby—
PriceFree, foreverPaid

​
Why teams choose the open-source option

Your data never leaves your stack

MCP tool calls contain your users’ literal requests and arguments — the most sensitive product data you have. With mcpeye, Postgres, Redis, and your LLM key are all yours. Nothing egresses to a third party.

A build-next roadmap, not just dashboards

The Intent Gap Report surfaces the asks your tools couldn’t deliver and the capabilities agents wanted that no tool exists for yet — ranked, with the exact sessions behind each one.

Open source you can audit and extend

Read the code, self-host it, fork it, send a PR. No black box deciding what your agents’ data is worth.

One-line SDK, three languages

track(server, "id") in TypeScript, Python, or Ruby. The agent self-reports its intent inline, so capture is near-free and no LLM runs on the hot path.

​
Switching is one command

git clone https://github.com/mcpeye/mcpeye.git
cd mcpeye
cp .env.example .env        # optionally add OPENAI_API_KEY or ANTHROPIC_API_KEY
docker compose up
Then drop the SDK into your MCP server and your first Intent Gap Report builds within minutes.

Get started in five minutes

Self-host mcpeye and read your first Intent Gap Report.