chore: version packages

.doc-bridge/capabilities.json

@@ -7,7 +7,7 @@
     "name": "AgentsKit",
     "root": "."
   },
-  "contentHash": "38a4b61ecbad8f1dfebda378eb40982e0a3a7415f05cb15030c1a998c2135d8e",
+  "contentHash": "c878f166fb291e94a157ccd5817b91568c86796330c4368cd27d22d3b3060d31",
   "artifacts": {
     "index": ".doc-bridge/index.json",
     "llmsTxt": "llms.txt"

.doc-bridge/index.json

@@ -1,8 +1,8 @@
 {
   "schemaVersion": 1,
-  "contentHash": "38a4b61ecbad8f1dfebda378eb40982e0a3a7415f05cb15030c1a998c2135d8e",
+  "contentHash": "c878f166fb291e94a157ccd5817b91568c86796330c4368cd27d22d3b3060d31",
   "contentHashAlgo": "sha256-normalized-v1",
-  "generatedAt": "2026-08-12T23:34:15.267Z",
+  "generatedAt": "2026-08-13T00:09:29.294Z",
   "project": {
     "name": "AgentsKit",
     "root": "."
@@ -82,7 +82,7 @@
       "title": "mcp",
       "path": "apps/docs-next/content/docs/for-agents/mcp.mdx",
       "description": "Serve AgentsKit tools to any MCP host. A thin bridge over `@agentskit/tools/mcp` (`createMcpServer` + `createStdioTransport`).",
-      "body": "Purpose Serve AgentsKit tools to any MCP host. A thin bridge over @agentskit/tools/mcp ( createMcpServer + createStdioTransport ). Install Primary exports - createAgentsKitMcpServer({ tools, serverInfo?, onEvent?, transport? }) — expose ToolDefinition[] as an MCP server. Defaults to stdio over the current process; pass transport to override (tests / custom hosts). - processStdio() — adapt the Node process into the StdioLikeProcess the transport expects (server receives on stdin, sends on stdout). - createAgentTool({ id, description, systemPrompt, adapter, maxSteps? }) — wrap a whole agent as one MCP tool. The host calls it with a task ; the agent runs server-side on the given adapter and returns the result (\"agents as MCP tools\"). - fetchAgentSkill(id, fetchImpl?) — fetch a registry agent's runnable skill (hosted index, raw-GitHub fallback); null for tool-composing agents. An optional third argument controls abort, timeout, and response-byte limits. Bin agentskit-mcp — npx -y @agentskit/mcp@0.3.4 --tools fetch,search . Expose whole agents with --agents <ids --provider <p (any of ~20 providers + catalog OpenAI-compatible). Flags: --tools , --fs-root , --sqlite , --allow-shell , --model , --max-steps , --api-key , --base-url . Unknown, duplicate, or valueless flags fail closed. stdout is the JSON-RPC channel; diagnostics and help go to stderr. Pinned coding-agent configs and their evidence levels live in the . Host config fixtures cover Codex, Claude Code/Desktop, Cursor, Cline, and Continue. The local-build and published-package smoke scripts both initialize the shared STDIO path and require the tool list to equal fetch url,web search . Beta boundaries - Tool names are unique and follow the current MCP 1–128 character interoperability grammar. - Server configuration and agent-tool configuration fail with typed AgentsKit diagnostics. - Published tool definitions are snapshotted; observer failures cannot alter protocol behavior. - Agent tasks, step counts, prompts, descriptions, registry IDs, request time, and response bytes are bounded. - Registry source is treated as data and never executed. - The built-in surface is the MCP tools subset over stdio or an injected transport. HTTP/WebSocket, resources, prompts, sampling, auth, rate limiting, and persistence are host responsibilities. Minimal example Related packages - — the tools you expose + the MCP primitives. - — the ToolDefinition contract. Source - npm: https://www.npmjs.com/package/@agentskit/mcp - repo: https://github.com/AgentsKit-io/agentskit/tree/main/packages/mcp - contract:"
+      "body": "Purpose Serve AgentsKit tools to any MCP host. A thin bridge over @agentskit/tools/mcp ( createMcpServer + createStdioTransport ). Install Primary exports - createAgentsKitMcpServer({ tools, serverInfo?, onEvent?, transport? }) — expose ToolDefinition[] as an MCP server. Defaults to stdio over the current process; pass transport to override (tests / custom hosts). - processStdio() — adapt the Node process into the StdioLikeProcess the transport expects (server receives on stdin, sends on stdout). - createAgentTool({ id, description, systemPrompt, adapter, maxSteps? }) — wrap a whole agent as one MCP tool. The host calls it with a task ; the agent runs server-side on the given adapter and returns the result (\"agents as MCP tools\"). - fetchAgentSkill(id, fetchImpl?) — fetch a registry agent's runnable skill (hosted index, raw-GitHub fallback); null for tool-composing agents. An optional third argument controls abort, timeout, and response-byte limits. Bin agentskit-mcp — npx -y @agentskit/mcp@0.3.5 --tools fetch,search . Expose whole agents with --agents <ids --provider <p (any of ~20 providers + catalog OpenAI-compatible). Flags: --tools , --fs-root , --sqlite , --allow-shell , --model , --max-steps , --api-key , --base-url . Unknown, duplicate, or valueless flags fail closed. stdout is the JSON-RPC channel; diagnostics and help go to stderr. Pinned coding-agent configs and their evidence levels live in the . Host config fixtures cover Codex, Claude Code/Desktop, Cursor, Cline, and Continue. The local-build and published-package smoke scripts both initialize the shared STDIO path and require the tool list to equal fetch url,web search . Beta boundaries - Tool names are unique and follow the current MCP 1–128 character interoperability grammar. - Server configuration and agent-tool configuration fail with typed AgentsKit diagnostics. - Published tool definitions are snapshotted; observer failures cannot alter protocol behavior. - Agent tasks, step counts, prompts, descriptions, registry IDs, request time, and response bytes are bounded. - Registry source is treated as data and never executed. - The built-in surface is the MCP tools subset over stdio or an injected transport. HTTP/WebSocket, resources, prompts, sampling, auth, rate limiting, and persistence are host responsibilities. Minimal example Related packages - — the tools you expose + the MCP primitives. - — the ToolDefinition contract. Source - npm: https://www.npmjs.com/package/@agentskit/mcp - repo: https://github.com/AgentsKit-io/agentskit/tree/main/packages/mcp - contract:"
     },
     {
       "id": "memory",

apps/docs-next/content/docs/for-agents/mcp.mdx

@@ -11,7 +11,7 @@ Serve AgentsKit tools to any MCP host. A thin bridge over `@agentskit/tools/mcp`
 ## Install
 
 ```bash
-npm install @agentskit/mcp@0.3.4
+npm install @agentskit/mcp@0.3.5
 ```
 
 ## Primary exports
@@ -30,7 +30,7 @@ npm install @agentskit/mcp@0.3.4
 
 ## Bin
 
-`agentskit-mcp` — `npx -y @agentskit/mcp@0.3.4 --tools fetch,search`. Expose whole agents
+`agentskit-mcp` — `npx -y @agentskit/mcp@0.3.5 --tools fetch,search`. Expose whole agents
 with `--agents <ids> --provider <p>` (any of ~20 providers + catalog OpenAI-compatible). Flags: `--tools`,
 `--fs-root`, `--sqlite`, `--allow-shell`, `--model`, `--max-steps`, `--api-key`,
 `--base-url`. Unknown, duplicate, or valueless flags fail closed. stdout is the

apps/docs-next/content/docs/reference/recipes/coding-agent-mcp.mdx

@@ -35,7 +35,7 @@ host application's UI, login, or trust prompt.
 Add the server with the CLI:
 
 ```bash
-codex mcp add agentskit -- npx -y @agentskit/mcp@0.3.4 --tools fetch,search
+codex mcp add agentskit -- npx -y @agentskit/mcp@0.3.5 --tools fetch,search
 codex mcp list
 ```
 
@@ -44,7 +44,7 @@ Or commit a project-scoped `.codex/config.toml` in a trusted project:
 ```toml
 [mcp_servers.agentskit]
 command = "npx"
-args = ["-y", "@agentskit/mcp@0.3.4", "--tools", "fetch,search"]
+args = ["-y", "@agentskit/mcp@0.3.5", "--tools", "fetch,search"]
 default_tools_approval_mode = "prompt"
 ```
 
@@ -56,7 +56,7 @@ Use `/mcp` to inspect the connected server.
 Create a project-scoped server:
 
 ```bash
-claude mcp add --scope project --transport stdio agentskit -- npx -y @agentskit/mcp@0.3.4 --tools fetch,search
+claude mcp add --scope project --transport stdio agentskit -- npx -y @agentskit/mcp@0.3.5 --tools fetch,search
 claude mcp list
 ```
 
@@ -68,7 +68,7 @@ The equivalent `.mcp.json` is:
     "agentskit": {
       "type": "stdio",
       "command": "npx",
-      "args": ["-y", "@agentskit/mcp@0.3.4", "--tools", "fetch,search"]
+      "args": ["-y", "@agentskit/mcp@0.3.5", "--tools", "fetch,search"]
     }
   }
 }
@@ -89,7 +89,7 @@ Create `.cursor/mcp.json`:
     "agentskit": {
       "type": "stdio",
       "command": "npx",
-      "args": ["-y", "@agentskit/mcp@0.3.4", "--tools", "fetch,search"]
+      "args": ["-y", "@agentskit/mcp@0.3.5", "--tools", "fetch,search"]
     }
   }
 }
@@ -109,7 +109,7 @@ edits `%APPDATA%\Claude\claude_desktop_config.json`.
   "mcpServers": {
     "agentskit": {
       "command": "npx",
-      "args": ["-y", "@agentskit/mcp@0.3.4", "--tools", "fetch,search"]
+      "args": ["-y", "@agentskit/mcp@0.3.5", "--tools", "fetch,search"]
     }
   }
 }
@@ -128,7 +128,7 @@ Open MCP Servers, choose Configure MCP Servers, and add:
   "mcpServers": {
     "agentskit": {
       "command": "npx",
-      "args": ["-y", "@agentskit/mcp@0.3.4", "--tools", "fetch,search"],
+      "args": ["-y", "@agentskit/mcp@0.3.5", "--tools", "fetch,search"],
       "env": {},
       "disabled": false,
       "autoApprove": []
@@ -151,15 +151,15 @@ Create `.continue/mcpServers/agentskit.yaml`:
 
 ```yaml
 name: AgentsKit MCP
-version: 0.3.4
+version: 0.3.5
 schema: v1
 mcpServers:
   - name: agentskit
     type: stdio
     command: npx
     args:
       - "-y"
-      - "@agentskit/mcp@0.3.4"
+      - "@agentskit/mcp@0.3.5"
       - "--tools"
       - "fetch,search"
 ```
@@ -174,7 +174,7 @@ server arguments rather than changing host-specific code:
 
 ```bash
 OPENROUTER_API_KEY=your-key \
-  npx -y @agentskit/mcp@0.3.4 \
+  npx -y @agentskit/mcp@0.3.5 \
   --tools fetch,search \
   --agents code-review \
   --provider openrouter \