An MCP server that writes its own tools from how it gets used
View on GitHub ↗An MCP server that writes its own tools from how it gets used.
It watches the calls its callers make. When they keep reaching the same outcome the same way, it adds that outcome to itself as a single new tool. Tools nobody uses get dropped again. No human writes any of them.
Someone asks an agent to open the file that sets up the database connection. Against a normal filesystem MCP server, the agent has to go and find it:
Three round trips, and 660 tokens of directory listing sit in the model's context forever, so that it could pick one path out of them.
After this server has seen that happen a few times, it has written itself a tool:
One call. The listing is never fetched, because nothing needed it except the reasoning that already happened, and that reasoning is now sitting in the route as a constant.
Another caller found the same file a completely different way, by listing seven directories one at a time instead of taking the tree in one go. Eight calls rather than three, different tools entirely. It produces the same route, and the two merge into one tool backed by both.
Collapsing three calls into one saves a couple of hundred tokens of call syntax. That would not be worth building anything for.
The saving is that the intermediate results never enter the model's context at all. The directory listing, the schema dump, the thirty issues you fetched to pick one number out of. A route consumes those inside the server and throws them away.
From the project README.
Add the radar badge to your README — it shows your project was picked up by MCP Radar and links to this page:
[](https://mcp.liqiwa.com/s/anshulforyou--evolving-mcp.html)
ChatGPT thinks. Codex works. Use ChatGPT as the planning brain while keeping the Codex harness.
shinthink/blitzstrike⚡ Blitz Strike — a universal MCP penetration-testing toolbelt. Structured methodology: reconnaissance & attack-surface mapping, source-to-sink analysis, and live validation. 57 escalation chains, 130-
0xwilliamortiz/openclaude-improvedruns anywhere. uses anything
halofyai/halofyHalofy is the open access and governance layer for AI agents across your organization. Identity, policy, provenance, audit, and signed erasure.
CaptureGrubEnchant/SolidWorksSolidWorks MCP Server connects an AI assistant to a running SolidWorks instance. Sketch, extrude, fillet, export STEP/STL, generate macros.
arielshad/3d-asset-server3d assets api and mcp
The top new MCP servers of the week, every Monday. No spam, unsubscribe anytime.