Kitsune Mcp
Mount one MCP hub and shapeshift into other servers from seven registries without restarting your agent.
Overview
Kitsune MCP is a MCP server for the Build phase that acts as a shape-shifting hub, letting agents shapeshift() into 10,000+ registry servers at runtime without restarts.
What is this MCP server?
- Shape-shifting MCP hub with shapeshift() into 10,000+ servers at runtime
- No agent restarts required when changing effective MCP surface
- 7 integrated registries for discovery and mounting
- Smithery-backed access with SMITHERY_API_KEY (3,000+ verified servers per server.json copy)
- Published as kitsune-mcp on npm and PyPI (version 0.9.0)
- 7 registries referenced in catalog description
- 10,000+ servers and 3,000+ Smithery-verified servers cited in metadata
What problem does it solve?
Static MCP configs force constant restarts and YAML churn whenever you want another tool from a different registry.
Who is it for?
Power users juggling many MCP sources who want runtime server switching inside one stdio connection.
Skip if: Builders who run a single MCP server year-round and want the simplest possible config.
What do I get? / Deliverables
After adding Kitsune, one hub entry can morph into many MCP servers on demand across seven registries.
- Single MCP entry that can assume other servers via shapeshift()
- Access path to multi-registry catalogs including Smithery-verified servers
- Reduced MCP config churn across project phases
Recommended MCP Servers
Journey fit
Integrations are the canonical shelf for a meta-MCP router you configure once during product build, then reuse across later phases. Runtime shapeshift into thousands of tools is fundamentally an integration-layer problem, not a single launch or analytics task.
How it compares
MCP aggregation hub, not a single-purpose domain MCP or Claude skill markdown pack.
Common Questions / FAQ
Who is Kitsune MCP for?
Kitsune is for agent users who need flexible access to large MCP catalogs across multiple registries without restarting the client.
When should I use Kitsune MCP?
Use Kitsune when you frequently swap MCP capabilities mid-workflow or want Smithery and other registries behind one shapeshift() interface.
How do I add Kitsune MCP to my agent?
Install kitsune-mcp via npm or PyPI stdio config, set SMITHERY_API_KEY for Smithery-backed servers, then register the hub and invoke shapeshift() per Kitsune documentation.