@meldocio/mcp-stdio-proxy 1.0.3 → 1.0.4
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 +46 -1
- package/package.json +1 -1
package/README.md
CHANGED
|
@@ -107,9 +107,11 @@ echo '{"jsonrpc":"2.0","id":1,"method":"tools/list"}' | \
|
|
|
107
107
|
- ✅ JSON-RPC 2.0 protocol
|
|
108
108
|
- ✅ Single and batch requests
|
|
109
109
|
- ✅ Proper error handling with JSON-RPC error codes
|
|
110
|
-
- ✅ Request timeout handling (
|
|
110
|
+
- ✅ Request timeout handling (25 seconds)
|
|
111
111
|
- ✅ Network error recovery
|
|
112
112
|
- ✅ Line-by-line processing for streaming
|
|
113
|
+
- ✅ Automatic support for all MCP tools (including `server_info`)
|
|
114
|
+
- ✅ Metadata (`_meta`) in responses for better context
|
|
113
115
|
|
|
114
116
|
## JSON-RPC Error Codes
|
|
115
117
|
|
|
@@ -122,6 +124,49 @@ The proxy uses standard JSON-RPC 2.0 error codes:
|
|
|
122
124
|
- `-32603`: Internal error (network errors, timeouts, etc.)
|
|
123
125
|
- `-32000`: Server error (HTTP 4xx/5xx responses)
|
|
124
126
|
|
|
127
|
+
## Available Tools
|
|
128
|
+
|
|
129
|
+
The proxy automatically supports all tools provided by the meldoc MCP API, including:
|
|
130
|
+
|
|
131
|
+
- **`server_info`** - Get information about the server configuration, available projects, and token capabilities
|
|
132
|
+
- **`docs_list`** - List available documentation
|
|
133
|
+
- **`docs_get`** - Get specific documentation content
|
|
134
|
+
- And other tools as provided by the API
|
|
135
|
+
|
|
136
|
+
### Example: Using `server_info`
|
|
137
|
+
|
|
138
|
+
You can get server information using the `server_info` tool:
|
|
139
|
+
|
|
140
|
+
```bash
|
|
141
|
+
echo '{"jsonrpc":"2.0","id":1,"method":"tools/call","params":{"name":"server_info","arguments":{}}}' | \
|
|
142
|
+
MELDOC_MCP_TOKEN=your_token_here npx @meldocio/mcp-stdio-proxy
|
|
143
|
+
```
|
|
144
|
+
|
|
145
|
+
The response includes:
|
|
146
|
+
- Server name (from token)
|
|
147
|
+
- Token description (if provided)
|
|
148
|
+
- Available projects with IDs, names, and aliases
|
|
149
|
+
- Token capabilities (read, update, create, delete)
|
|
150
|
+
- Usage hints
|
|
151
|
+
|
|
152
|
+
### Response Metadata
|
|
153
|
+
|
|
154
|
+
All tool responses now include a `_meta` field with contextual information:
|
|
155
|
+
|
|
156
|
+
```json
|
|
157
|
+
{
|
|
158
|
+
"items": [...],
|
|
159
|
+
"_meta": {
|
|
160
|
+
"server": "My Token",
|
|
161
|
+
"projects": ["Frontend Docs", "Backend API"],
|
|
162
|
+
"capabilities": ["read"],
|
|
163
|
+
"hint": "Read permission required for this operation"
|
|
164
|
+
}
|
|
165
|
+
}
|
|
166
|
+
```
|
|
167
|
+
|
|
168
|
+
This metadata helps AI assistants understand the context and limitations of the current token.
|
|
169
|
+
|
|
125
170
|
## Troubleshooting
|
|
126
171
|
|
|
127
172
|
### Error: MELDOC_MCP_TOKEN environment variable is required
|