@protolabsai/proto 0.18.4 → 0.19.0
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/bundled/qc-helper/docs/features/mcp.md +18 -0
- package/cli.js +208 -323
- package/package.json +2 -2
|
@@ -147,6 +147,24 @@ CLI:
|
|
|
147
147
|
qwen mcp add --transport sse sseServer http://localhost:8080/sse --timeout 30000
|
|
148
148
|
```
|
|
149
149
|
|
|
150
|
+
## Server instructions
|
|
151
|
+
|
|
152
|
+
MCP servers can return an `instructions` string in their [initialize response](https://spec.modelcontextprotocol.io/specification/2024-11-05/basic/lifecycle/#initialization) (part of the MCP spec). When a server provides instructions, proto automatically appends them to the system prompt at session start under a labelled block:
|
|
153
|
+
|
|
154
|
+
```
|
|
155
|
+
# MCP Server Instructions
|
|
156
|
+
|
|
157
|
+
## MCP Server: <server-name>
|
|
158
|
+
|
|
159
|
+
<instructions text from the server>
|
|
160
|
+
```
|
|
161
|
+
|
|
162
|
+
This lets server authors embed usage guidance — which tool to call, how to format queries, what the server's constraints are — directly into the model's context without requiring any user-side `AGENTS.md` configuration. Instructions from multiple servers are each appended in their own block.
|
|
163
|
+
|
|
164
|
+
> [!tip]
|
|
165
|
+
>
|
|
166
|
+
> If you're building an MCP server and want the model to use your tools effectively, implement the `instructions` field in your initialize response. See the [fff example](https://github.com/dmtrKovalenko/fff.nvim#mcp) for a well-structured server instructions block.
|
|
167
|
+
|
|
150
168
|
## Safety and control
|
|
151
169
|
|
|
152
170
|
### Trust (skip confirmations)
|