mcp-server-and-agent
mcp-server-and-agent
Status: work in progress. Scaffolded, not yet implemented. This README will carry generated numbers once the first results land.
A hand-written MCP server at the protocol level plus a LangGraph agent over it, with four topologies run against the same task set and their failure modes measured.
This repo answers one question:
What is each agent topology's failure rate, and does supervisor actually beat single-agent?
Everything here serves answering that. Features that do not help answer it are out of scope — deliberately.
Why this exists
Quickstart
uv sync --extra dev
uv run pytest -q
uv run python scripts/generate_results.pyResults
No results yet.
Design decisions
Limitations
Concepts covered
2C hand-written MCP server plus LangGraph agent (DO-8)
2C ReAct, plan-and-execute, reflection
2C topologies and their failure modes
2C tool design: schema clarity, granularity, errors as model feedback, idempotency, confirmation gates
2C MCP as a protocol: transports, discovery, resources, prompts, sampling, OAuth scope
2C state and memory, checkpointing, durable execution
…and 4 more (see
docs/inventory-coverage.md)
License
MIT
Latest Blog Posts
- Who's Calling? MCP Hosts Are an Identity Blind Spot (And the Spec Knows It)By Om-Shree-0709 on .mcpAgent IdentityOAuth 2.1
- Your AI Chatbot Just Exposed Your CEO's Salary to an InternBy Om-Shree-0709 on .Agent IdentityMCP SecurityOAuth Delegation
- Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)By Om-Shree-0709 on .Agentic AiPrompt InjectionWebAssembly
MCP directory API
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/moclamzw/mcp-server-and-agent'
If you have feedback or need assistance with the MCP directory API, please join our Discord server