"Understanding Call Hierarchy in Software Development or Programming" matching MCP servers:

Graph-based tool retrieval for LLM agents. Builds a tool graph from OpenAPI/MCP specs and retrieves multi-step workflows via hybrid search (BM25 + graph traversal + embedding), recovering accuracy from 12% to 82% with 79% fewer tokens. Also works as an MCP Proxy to aggregate multiple servers behind 3 meta-tools.

Enables Codex to rank available tools and skills, rerank code and documentation search results, and triage saved output artifacts using Jev-based relevance scoring while leaving final decisions to Codex.

An MCP relay that adds a use_jev tool to every connected server, letting the Jev model autonomously select and execute tool calls while the calling model supplies any required text values. It enables agents to delegate multi-step tool use across all configured MCP servers through a single unified interface.

A Model Context Protocol server that enables seamless integration between Claude AI and development tools like VSCode, Augment, Vercel, Airtable, and Square.

Enables Codex to manage a local Claude Code companion through MCP, implementing a dual-agent workflow where Codex handles reasoning and review while Claude Code performs engineering tasks.

Enables users to generate complete, production-ready software projects from simple ideas by coordinating 8 specialized AI agents through the Model Context Protocol.

Enables local opencode agents to control a live Chrome browser via MCP tools, including tab management, JavaScript execution, clicking, form filling, page reading, screenshots, and console log retrieval.

Enables deterministic repair of malformed tool-call schemas and guards parameter projections for AI agents, ensuring reliable JSON-RPC interactions via MCP.

Enables Claude Code, Codex, Devin, or any MCP client to control Chrome/Edge through the repository's browser extensions, with Claude-style visual tools or Codex-style text-first tools.

Enables autonomous agents and MCP-compatible clients to enforce policy-approved actions using risk tiers, reversible checkpoints, and token approval bounds.

A Model Context Protocol server for the resQ emergency response system that integrates with digital twin simulations and coordination engines. It allows users to trigger simulations, generate deployment strategies, and monitor real-time drone status for incident response analysis.

Declarative MCP runtime over IDF artifacts. Tool descriptions carry invariants, lifecycle, irreversibility, and role scopes.

Enables AI assistants to query and analyze AI agent sessions from observability providers like Shepherd (AIOBS) and Langfuse, allowing users to debug agent runs, compare sessions, track performance, and analyze LLM usage patterns.

Enables AI agents to execute provider tools through a self-hostable gateway with scoped keys, permissions, and accounting reservations.

A git-backed MCP server that centrally manages AI agent skills, tools, and knowledge with role-based access, change requests, and a remote OAuth 2.1 endpoint.

Enables AI agents to respond to users with live, persistent, interactive web apps served at a single URL that evolve in place as the conversation continues. It exposes UI generation and evolution tools over MCP so agent responses can include clickable buttons and streaming interfaces alongside chat replies.

The coordination layer for AI agent networks, providing persistent memory, task management, inter-agent messaging, and human oversight through native MCP tools.

MCP server that lets Claude control multiple persistent browser tabs inside VS Code, with tools for navigation, clicking, typing, snapshotting pages, and reading console output.

Enables remote control of the Cursor AI agent via chat platforms like GitHub Issues or Telegram, allowing users to start sessions and receive summaries and prompts in a chat thread.

MCP server for AgentDNS that allows Claude or any MCP client to register a persona, discover and call other agents, and handle incoming messages with human-in-the-loop approval.