Building in public · Week 1 of 6

Your MCP servers slow your agents down. You don't know which.

Analytics for MCP servers in Claude Code, Codex, and Cursor. Spot noisy servers, wasted calls, and context bloat.

We email you when we launch. No spam, unsubscribe anytime.

~/projects/mcpinsight

$ mcpinsight top

SERVER         CALLS   HEALTH   WASTE
filesystem     2,843      87    low
postgres         847      42    high  ←
github           312      91    none
playwright        28      18    high  ←

The problem

The invisible layer of your AI coding setup

Your agent calls the same server 40 times per session. You never see it.

That MCP server you installed 3 weeks ago — still eating context. Do you use it?

Every tool call is logged. Nothing reads those logs — until now.

The solution

MCPInsight reads the logs you already have

Find what drags

Spot the 3 servers that drag every session down.

Kill the deadweight

Kill the 7 servers you haven't touched in 30 days.

Per-tool attribution

See which tools actually saved you tokens — per server, per session.

Multi-client

Compare Claude Code, Codex, and Cursor side by side.

Runs locally. Your data never leaves your machine.

Build in public

Shipping weekly. Follow the build.

Code, roadmap, and commit log are public from day one. Starring the repo is the cheapest way to keep tabs.

Week 1 Now

Landing + waitlist

Week 2

Parser + CLI top

Week 3

Dashboard + Codex parser

Week 4

Licensing + telemetry

Week 5

Launch + State of MCP

Week 6

Team tier + Cursor

Follow the build, not just the launch.

Code is public. Commits are weekly. Stars help. Shares help more.

Star on GitHub Share on X