Repository navigation
mcp-slim: Zero-dependency MCP stdio proxy for AutoGen (-50% to -98% schema tokens, $ref inlining, SecretGuard) #8473
Replies: 2 comments
|
Salyyy (@SalyyS1) The $ref inlining at the proxy layer is the key differentiator here. Most LLM parsers struggle with deep $defs chains, often forcing fallbacks to generic string types or failing validation entirely. By resolving these references before the payload hits the agent, you prevent the LLM from wasting context window capacity parsing schema definitions it never needs to execute. This isn't just about token count; it's about reducing the cognitive load on the model to interpret static metadata repeatedly across turns. The cumulative stats tracking for wire bytes effectively quantifies this overhead reduction, which is often invisible in standard benchmarks but critical for high-frequency agent loops. |
|
Dheiver Francisco Santos (@dheiver2) Spot on. In multi-agent AutoGen loops, unresolved In |
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
Hi everyone,
When connecting
StdioServerParams/mcp_server_toolsin AutoGen (autogen-ext) to enterprise MCP servers, two bottlenecks frequently surface:tools/listschema catalog (often 8k-15k tokens) plus verbose JSON tool outputs.strict=True/$refschema errors:mcp_server_toolsor downstream OpenAI/Anthropic/Gemini validators fail when MCP servers emit$defs/$refpointer chains, rootanyOf, or nullable["string", "null"]type arrays.We built mcp-slim, a zero-dependency Python 3.10+ stdio proxy that sits transparently inside
StdioServerParams:Repository & benchmarks: https://github.com/SalyyS1/mcp-slim
If this helps your AutoGen MCP workflows, please consider starring SalyyS1/mcp-slim on GitHub!
All reactions