<picture> <source media="(prefers-color-scheme: light)" srcset="static/litmus-logo-light.svg" /> <source media="(prefers-color-scheme: dark)"
Most developer tooling work still happens through a UI a human drives. Litmus MCP server moves it into the conversation instead. .
The server publishes 3 tools. What each one is for:
Category — Function NameServer — get_mcp_server_infoWindsurf — The Windsurf tool exposed by this serverBecause this one is hosted, setup is mostly authentication — you point your client at the endpoint and approve access. Nothing runs on your machine, so there is no runtime to keep patched.
Configuration is passed through the environment: EDGE_URL, EDGE_API_CLIENT_ID, EDGE_API_CLIENT_SECRET, NATS_SOURCE, NATS_PORT, NATS_PASSWORD, INFLUX_HOST, INFLUX_PORT. Treat anything key-shaped as a real credential — scope it to the minimum the server needs, and rotate it if it ever lands in a shared config.
Among the developer tooling options, the useful question is rarely "what can it do" but "what does it cost you to run" — permissions, credentials, and how much of your context its toolset consumes. Litmus's toolset — Category, Server, Windsurf — is a fair guide to whether it matches your workflow. It is maintained by litmusautomation; worth a glance at recent repository activity before you build anything load-bearing on it.
This entry was verified against Litmus's own documentation before publication; SyncDev keeps the directory reviewed rather than auto-generated.
| Tool | What it does |
|---|---|
| Category | Function Name |
| Server | get_mcp_server_info |
| Windsurf | The Windsurf tool exposed by this server. |
{
"mcpServers": {
"litmus": {
"command": "npx",
"args": ["-y", "@modelcontextprotocol/inspector"],
"env": {
"EDGE_URL": "your-value",
"EDGE_API_CLIENT_ID": "your-value",
"EDGE_API_CLIENT_SECRET": "your-value",
"NATS_SOURCE": "your-value",
"NATS_PORT": "your-value",
"NATS_PASSWORD": "your-value",
"INFLUX_HOST": "your-value",
"INFLUX_PORT": "your-value"
}
}
}
}Add to claude_desktop_config.json, then restart Claude Desktop.
| Variable | Description | Required |
|---|---|---|
| EDGE_URL | Endpoint or connection string the server talks to. | Yes |
| EDGE_API_CLIENT_ID | Configuration value read at startup. | Optional |
| EDGE_API_CLIENT_SECRET | Credential the server authenticates with. | Yes |
| NATS_SOURCE | Configuration value read at startup. | Optional |
| NATS_PORT | Configuration value read at startup. | Optional |
| NATS_PASSWORD | Configuration value read at startup. | Optional |
| INFLUX_HOST | Endpoint or connection string the server talks to. | Optional |
| INFLUX_PORT | Configuration value read at startup. | Optional |
Kill hallucinated APIs — version-accurate, up-to-date library documentation injected straight into context.
Microsoft's official browser automation server — drive a real browser through the accessibility tree, no screenshots needed.
GitHub's official server — repos, issues, pull requests, Actions and code security, straight from your assistant.
Issue tracking at the speed of conversation — Linear's official hosted server with OAuth and zero install.
Local repository surgery — status, diffs, commits, branches and history for any repo on disk.
Timezone sanity for AI — current time anywhere and correct conversions, without the model doing date math.