kitsune-mcp 0.15.0 → 0.18.1

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
Files changed (2) hide show
  1. package/README.md +22 -0
  2. package/package.json +1 -1
package/README.md CHANGED
@@ -243,6 +243,28 @@ Works with Claude Desktop, Claude Code, Cursor, Cline, OpenClaw, Continue.dev, Z
243
243
  | Cline / Continue.dev | VS Code settings / `~/.continue/config.json` |
244
244
  | OpenClaw | MCP config in OpenClaw settings |
245
245
 
246
+ ### Using Kitsune alongside existing servers
247
+
248
+ You can add Kitsune to a config that already has other servers — it works without touching anything else. For the cleanest setup (Kitsune as your sole gateway), `setup()` can extract API keys from your existing server configs into `~/.kitsune/.env` and register those servers so `shapeshift()` can reach them on demand.
249
+
250
+ **Kitsune never deletes or modifies your existing configs without explicit confirmation.** Config changes are always backed up and reversible with `setup(restore=True)`.
251
+
252
+ ### Run Kitsune and standard MCP side-by-side (Claude Code)
253
+
254
+ Claude Code supports per-project MCP configs that override the global one. This means you can run a Kitsune session and a standard multi-server session **simultaneously, with no config changes**:
255
+
256
+ ```bash
257
+ # Terminal A — Kitsune-only project (5 tools, clean context)
258
+ mkdir ~/projects/kitsune-session
259
+ echo '{"mcpServers":{"kitsune":{"command":"kitsune-mcp"}}}' > ~/projects/kitsune-session/.claude/mcp.json
260
+ cd ~/projects/kitsune-session && claude
261
+
262
+ # Terminal B — standard workflow (all your configured servers)
263
+ cd ~/projects/any-other-project && claude # uses global ~/.claude/mcp.json
264
+ ```
265
+
266
+ Both sessions run in parallel. The Kitsune terminal sees 5 tools; the standard terminal sees everything in your global config. No restarts, no toggling, no risk to either session. This makes it easy to compare workflows or run specialised agent tasks in one terminal while using familiar tools in another.
267
+
246
268
  ---
247
269
 
248
270
  ## Server Sources
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "kitsune-mcp",
3
- "version": "0.15.0",
3
+ "version": "0.18.1",
4
4
  "description": "The shape-shifting MCP hub — shapeshift() into 10,000+ MCP servers at runtime. One entry point, no restarts, 7 registries.",
5
5
  "mcpName": "io.github.kaiser-data/kitsune-mcp",
6
6
  "bin": {