MCP

MCP servers are stdio-only black boxes. MCP Lens proxies the JSON-RPC stream, captures every frame, and serves a local inspector at localhost:4040.

The second half of our agent tooling release: distribution, validation, and ergonomics layered on top of the first six. Six small CLIs, one through-line.

Ten private tools shipped overnight - observability, skills, hooks, prompts, and evals - aimed at the agent infrastructure gap small teams keep falling into.

From Claude Opus 4.7 and GPT-5.5 to Andrej-karpathy-skills and EvoMap - the AI dev tools actually shipping the last 30 days, with commands, links, and pricing.

MCP server directory and ranking site. Tracks weekly downloads, GitHub stars, and build status across 5,000+ servers.

Pythonic framework for building MCP servers. Decorators for tools, resources, and prompts. Officially incorporated into the Python SDK.

Bridge that exposes stdio MCP servers over HTTP/SSE, or vice versa. Run a local server remotely, or connect to a remote server as if it were local.

Configure model, effort, tools, MCP servers, and invocation scope.

Configure model, tools, MCP, skills, memory, and scoping.

Route specific MCP servers only to specific subagents.

Fires when an MCP server requests input from the user.

Connect external tools and data sources via the open MCP standard.

Local, project, user, and plugin-level MCP configurations.

Deferred tool loading reduces context overhead for large MCP suites.

Pre-configured or dynamic OAuth for remote MCP servers.

Reference and read resources exposed by MCP servers.

Execute MCP prompts as commands via the slash menu.

Receive push messages from MCP servers via channels.

Admin-controlled allow and deny lists for MCP servers.

Most MCP servers are noise. After shipping 24 apps with Claude Code, these are the five I reach for every time.