[Feature] File Based Configs -- Namespaces/Endpoints/Created MCP Servers

[danieliser]

IDEA: Would be great to be able to quickly import/export file based configs in standard format.

This way we can generate the configs, or even one day dynamically update them on the fly etc.

I mean this project is for AI Agents, YET AI Agents can't help you manage your service 😱

Concept:

• Add quick import / export for each to from JSON, similar to what you do for the Import/Export of defined MCP servers.
• Allow loading them from a folder.
  • Allow enabling hot-loading via ENV flag.

This makes MetaMCP much less tedious to setup/maintain. Very tired of ticking tool toggles one-by-one.

This is a much more scalable & dynamic solution.

---

I'm happy to contribute, midway doing a massive launch ourselves, but love this tool concept and it has been a huge lifesaver in terms of WordPress MCP hell, given a WP site can serve hundreds of useless tools in its current state.

If you point me in the right direction I can probably work it into a PR, otherwise it would be a great addition in the near future for power users.

[zhjch05]

Do you think a CLI/SDK variant of metamcp makes more sense for this purpose? Btw you can checkout fastmcp for your request, it may help. For agent use, I am thinking that we need more strong infra than current version, robust, scalable and performant, program API access. I am thinking a better fastmcp in rust/go may make more sense in this usage.

[danieliser]

Sorry for the delay.

Maybe I don't understand the question, but I think simply allowing file based configs on the existing infra would be huge improvement.

If you want to rebuild it on different stack as a pure CLI/SDK that would be cool and something easily deployable for a team at scale.

I'm working within the bounds of what exists ;p.

That said I could write a custom option, did that when I wanted CodeMode that CF described, but before they had it available: https://github.com/danieliser/codemode-unified, but if your can do what I need for now with simple to add improvements then even better (for my actual time cost).

Also consider simply backing up or migrating data from one server to another. It fully relies on docker processes and data mappings, no portability. This allows that too I would think.

If I can do it over HTTP API or via an exposed set of MCP tools even better.

I mean in an ideal world there would be a way to feed the Agent 1 mcp that was capable of switching toolkits based on context alone. but thats another issue/pr haha.