Dark-Alex-17/coyote
1
0
Fork 0
Code Issues Pull Requests Actions 2 Packages Projects Releases Wiki Activity

docs: corrected a typo in Claude Desktop vs Claude Code MCP compatibility

Alex Clarke
2026-05-22 18:45:39 -06:00
parent 687b0abb32
commit d3a9331127
1 changed files with 12 additions and 5 deletions
Download Patch File Download Diff File Expand all files Collapse all files
MCP-Servers.md
+12 -5
@@ -24,9 +24,15 @@ this directory using the following command:
loki --info | grep functions_dir | awk '{print $2}' loki --info | grep functions_dir | awk '{print $2}'
``` ```
The syntax for the `functions/mcp.json` file is compatible with MCP server configurations for Claude Desktop. The syntax for the `functions/mcp.json` file matches [Claude Code's `.mcp.json` configuration format](https://docs.claude.com/en/docs/claude-code/mcp),
So any time you're looking to add a new server, look at the docs for it and find the configuration example for with one small difference: the `type` field is **always required** in Loki, even for stdio servers (Claude Code
Claude Desktop. You should be able to use the exact same configuration in your `functions/mcp.json` file. allows it to be omitted and infers `stdio` from the presence of a `command`). So any time you're looking to add
a new server, look at its docs and find the Claude Code configuration example. You should be able to use the
exact same configuration in your `functions/mcp.json` file. Just make sure every entry has an explicit `type`.
**Note:** Loki does not support Claude Code's `"streamable-http"` alias (use `"http"` instead), nor extras
like `oauth` or `envFile`. For secrets, use [Loki Vault](Vault) interpolation rather than Claude Code's `${VAR}`
shell-style expansion.
Every server entry **must** include a `"type"` field set to one of: `"stdio"`, `"http"`, or `"sse"`. Every server entry **must** include a `"type"` field set to one of: `"stdio"`, `"http"`, or `"sse"`.
@@ -38,7 +44,7 @@ Loki supports three MCP transport types:
|---------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------| |---------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------|
| `stdio` | Spawns a local subprocess and communicates over stdin/stdout | | `stdio` | Spawns a local subprocess and communicates over stdin/stdout |
| `http` | Connects to a remote server via [Streamable HTTP](https://modelcontextprotocol.io/docs/concepts/transports#streamable-http) | | `http` | Connects to a remote server via [Streamable HTTP](https://modelcontextprotocol.io/docs/concepts/transports#streamable-http) |
| `sse` | Connects to a remote server via the legacy [HTTP+SSE](https://modelcontextprotocol.io/docs/concepts/transports#http-with-sse) transport (Claude Desktop format) | | `sse` | Connects to a remote server via the legacy [HTTP+SSE](https://modelcontextprotocol.io/docs/concepts/transports#http-with-sse) transport (deprecated in the MCP spec; prefer `http` where the server supports it) |
## Stdio Servers ## Stdio Servers
@@ -91,7 +97,8 @@ For remote MCP servers that support the Streamable HTTP transport:
## SSE Servers ## SSE Servers
For remote MCP servers that use the legacy HTTP+SSE transport (the format used by Claude Desktop): For remote MCP servers that use the legacy HTTP+SSE transport (deprecated in the MCP spec;
prefer `http` where the server supports it):
```json ```json
{ {