kitsune-mcp 0.8.3 → 0.8.5
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.
- package/README.md +4 -3
- package/package.json +1 -1
package/README.md
CHANGED
|
@@ -8,6 +8,7 @@
|
|
|
8
8
|
[](https://pypi.org/project/kitsune-mcp/)
|
|
9
9
|
[](https://pypi.org/project/kitsune-mcp/)
|
|
10
10
|
[](https://github.com/kaiser-data/kitsune-mcp/actions)
|
|
11
|
+
[](https://codecov.io/gh/kaiser-data/kitsune-mcp)
|
|
11
12
|
[](LICENSE)
|
|
12
13
|
[](https://smithery.ai/server/@kaiser-data/kitsune-mcp)
|
|
13
14
|
[](https://discord.gg/EYgcf7EX)
|
|
@@ -322,7 +323,7 @@ call("create_issue", arguments={"owner": "…", "repo": "…", "title": "…"})
|
|
|
322
323
|
Kitsune MCP re-reads `.env` on every call — which means adding a key instantly activates it. That convenience comes with a responsibility: **`.env` is the single place all your API keys live**. A few practices worth following:
|
|
323
324
|
|
|
324
325
|
- Add `.env` to `.gitignore` — never commit real keys
|
|
325
|
-
- Use project-level `.env` for project-specific keys; `~/.
|
|
326
|
+
- Use project-level `.env` for project-specific keys; `~/.kitsune/.env` for personal global keys
|
|
326
327
|
- Prefer minimal OAuth scopes and fine-grained tokens (e.g. GitHub fine-grained tokens with per-repo permissions)
|
|
327
328
|
- Rotate keys that get exposed; Kitsune MCP picks up the new value immediately without restart
|
|
328
329
|
|
|
@@ -334,7 +335,7 @@ Kitsune MCP re-reads `.env` on every call — which means adding a key instantly
|
|
|
334
335
|
|
|
335
336
|
**"What about MCP Inspector?"** — MCP Inspector is a standalone web UI that connects to one server and lets you inspect schemas and call tools manually. It's useful for basic debugging but isolated from real AI workflows. Kitsune MCP tests servers inside actual Claude or Cursor sessions — how an AI really uses them. It adds `test()` scoring, `bench()` latency numbers, side-by-side server comparison, and `craft()` for live endpoint prototyping. It also discovers and installs servers on demand; Inspector requires you to already have one running.
|
|
336
337
|
|
|
337
|
-
**"What about `mcp-dynamic-proxy`?"** — It hides tools behind `call_tool("brave", "web_search", {...})` — always a wrapper. After `
|
|
338
|
+
**"What about `mcp-dynamic-proxy`?"** — It hides tools behind `call_tool("brave", "web_search", {...})` — always a wrapper. After `shapeshift("mcp-server-brave-search")`, Kitsune MCP gives you a real native `brave_web_search` with the actual schema. It also can't discover or install packages at runtime.
|
|
338
339
|
|
|
339
340
|
**"Can FastMCP do this natively?"**
|
|
340
341
|
|
|
@@ -380,7 +381,7 @@ Get a free key at [smithery.ai/account/api-keys](https://smithery.ai/account/api
|
|
|
380
381
|
**Frictionless credentials** — Kitsune MCP re-reads `.env` on every `inspect()`, `shapeshift()`, and `call()`. Add a key mid-session and it takes effect immediately — no restart:
|
|
381
382
|
|
|
382
383
|
```
|
|
383
|
-
# .env (CWD, ~/.env, or ~/.
|
|
384
|
+
# .env (CWD, ~/.env, or ~/.kitsune/.env — all checked, CWD wins)
|
|
384
385
|
BRAVE_API_KEY=your-key
|
|
385
386
|
GITHUB_TOKEN=ghp_...
|
|
386
387
|
```
|
package/package.json
CHANGED
|
@@ -1,6 +1,6 @@
|
|
|
1
1
|
{
|
|
2
2
|
"name": "kitsune-mcp",
|
|
3
|
-
"version": "0.8.
|
|
3
|
+
"version": "0.8.5",
|
|
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": {
|