Lynxprompt MCP vs Longhorn MCP
A side-by-side look at the Lynxprompt MCP and Longhorn MCP MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose Lynxprompt MCP for cloud platforms work as a local process; choose Longhorn MCP for cloud platforms as a local process. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
Choose Lynxprompt MCP when
- You need dedicated capabilities in the Cloud Platforms domain.
- You prefer a local stdio subprocess transport.
- Its auth model fits you: API key required.
- You have the keys it needs:
LYNXPROMPT_URL, LYNXPROMPT_TOKEN, LISTEN_ADDR, MCP_AUTH_TOKEN, TRANSPORT. - You want tools like
create_blueprint, create_hierarchy, delete_blueprint.
Choose Longhorn MCP when
- You need dedicated capabilities in the Cloud Platforms domain.
- You prefer a local stdio subprocess transport.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Cloud Platforms | Cloud Platforms |
| Quality signal | 63/100 · Good | 43/100 · Fair |
| Install command | Confirmed | Confirmed |
| Transport | Local subprocess (stdio) | Local subprocess (stdio) |
| Auth | API key required | Not declared |
| Pricing | Free | Not declared |
| Required env vars | LYNXPROMPT_URLLYNXPROMPT_TOKENLISTEN_ADDRMCP_AUTH_TOKENTRANSPORT | None listed |
| Verified owner | Community listing | Community listing |
| GitHub stars | 2 | 0 |
| Directory activity | 3 views 0 installs 0 upvotes | 0 views 0 installs 0 upvotes |
| Tools | 6 | Not listed |
| Full listing | View Lynxprompt MCP | View Longhorn MCP |
Tools & capabilities
Lynxprompt MCP tools 6
create_blueprintCreate a new blueprint in LynxPromptcreate_hierarchyCreate a new hierarchy in LynxPromptdelete_blueprintDelete a blueprint from LynxPromptdelete_hierarchyDelete a hierarchy from LynxPromptsearch_blueprintsSearch the public LynxPrompt blueprint marketplaceupdate_blueprintUpdate an existing blueprint in LynxPrompt
Longhorn MCP tools
No tool names declared yet. Check the project README from the listing page.
Ready-to-paste client configs
Paste either block (or both) into your client config, e.g. claude_desktop_config.json or ~/.cursor/mcp.json. We only show a config when the install command is confirmed.
Lynxprompt MCP
{
"mcpServers": {
"geiserx-lynxprompt-mcp": {
"command": "npx",
"args": [
"-y",
"lynxprompt-mcp"
],
"env": {
"LYNXPROMPT_URL": "YOUR_LYNXPROMPT_URL_HERE",
"LYNXPROMPT_TOKEN": "YOUR_LYNXPROMPT_TOKEN_HERE",
"LISTEN_ADDR": "YOUR_LISTEN_ADDR_HERE",
"MCP_AUTH_TOKEN": "YOUR_MCP_AUTH_TOKEN_HERE",
"TRANSPORT": "YOUR_TRANSPORT_HERE"
}
}
}
}
Longhorn MCP
{
"mcpServers": {
"longhorn-mcp": {
"command": "npx",
"args": [
"-y",
"longhorn-mcp"
]
}
}
}
Frequently asked questions
Lynxprompt MCP is categorized under Cloud Platforms and uses a local stdio subprocess. Longhorn MCP belongs to Cloud Platforms and uses a local stdio subprocess. Pick Lynxprompt MCP for cloud platforms work and Longhorn MCP for cloud platforms.
Copy the mcpServers block from the config section on this page into your client's config (for example claude_desktop_config.json or ~/.cursor/mcp.json), then fully restart the client.
Lynxprompt MCP is listed as free. Auth: api key required. Longhorn MCP has no declared pricing — check the project's own site. If a server needs environment variables such as API keys, define them under the env key in your client's MCP config.
Yes. MCP clients support multiple servers: add geiserx-lynxprompt-mcp and longhorn-mcp as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Lynxprompt MCP has a quality signal of 63/100 (Good) with 3 views, 0 installs and 2 GitHub stars. Longhorn MCP has 43/100 (Fair) with 0 views, 0 installs and 0 GitHub stars.