@maind-dev/mcp-bridge 0.81.0 → 0.83.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/README.md CHANGED
@@ -2,7 +2,7 @@
2
2
 
3
3
  A tiny local MCP wrapper that pins your [maind](https://maind.dev) API key to
4
4
  a single device. The bridge speaks MCP over stdio to your IDE (Claude Code,
5
- Cursor, Windsurf, …) and forwards every request to `https://mcp.maind.dev/mcp`
5
+ Cursor, Windsurf, GitHub Copilot in VS Code, …) and forwards every request to `https://mcp.maind.dev/mcp`
6
6
  with an `X-Maind-Device-Id` header, so the server can refuse calls from any
7
7
  other machine that tries to reuse the same key.
8
8
 
@@ -61,6 +61,28 @@ using the bridge transport, add a client marker via env:
61
61
  }
62
62
  ```
63
63
 
64
+ **VS Code (GitHub Copilot agent mode)** reads a different file in a different
65
+ shape: `servers` instead of `mcpServers`, with `"type": "stdio"` on every
66
+ entry — an `mcpServers` key is ignored without a word. `npx -y @maind-dev/mcp-bridge install --client copilot`
67
+ writes the user-profile `mcp.json` (`~/Library/Application Support/Code/User/mcp.json`,
68
+ `%APPDATA%\Code\User\mcp.json`, `$XDG_CONFIG_HOME/Code/User/mcp.json`) in that
69
+ shape, keeping your comments; for a workspace-level file, put this in
70
+ `.vscode/mcp.json` instead:
71
+
72
+ ```json
73
+ {
74
+ "servers": {
75
+ "maind": {
76
+ "type": "stdio",
77
+ "command": "npx",
78
+ "args": ["-y", "@maind-dev/mcp-bridge"],
79
+ "env": {
80
+ "MAIND_CLIENT_FAMILY": "copilot"
81
+ }
82
+ }
83
+ }
84
+ }
85
+ ```
64
86
  Restart the MCP client. The first invocation walks you through the device
65
87
  flow; subsequent ones are silent (you should never see the verification code
66
88
  again unless you re-pair).