Lycatra vs Join.cloud
A side-by-side look at the Lycatra and Join.cloud MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
L
LycatraCommunication · Remote HTTP/SSEConnect agents to Lycatra knowledge, memory, collaboration, schedules, notifications, and teams.40FairAuth: not declaredVerdict: choose Lycatra for communication work over a hosted endpoint; choose Join.cloud for communication as a local process. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
LChoose Lycatra when
- You need dedicated capabilities in the Communication domain.
- You prefer a remote HTTP/SSE transport.
Choose Join.cloud when
- You need dedicated capabilities in the Communication domain.
- You prefer a local stdio subprocess transport.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | L Lycatra | |
|---|---|---|
| Category | Communication | Communication |
| Quality signal | 40/100 · Fair | 52/100 · Good |
| Install command | Confirmed | Confirmed |
| Transport | Remote HTTP/SSE | Local subprocess (stdio) |
| Auth | Not declared | Not declared |
| Pricing | Not declared | Not declared |
| Required env vars | None listed | None listed |
| Verified owner |
Tools & capabilities
Lycatra tools
No tool names declared yet. Check the project README from the listing page.
Join.cloud 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.
Lycatra
{
"mcpServers": {
"lycatra": {
"url": "https://lycatra.com/api/mcp"
}
}
}
Join.cloud
{
"mcpServers": {
"kushneryk-join-cloud": {
"command": "npx",
"args": [
"-y",
"joincloud"
]
}
}
}
Frequently asked questions
Lycatra is categorized under Communication and uses a remote HTTP/SSE transport. Join.cloud belongs to Communication and uses a local stdio subprocess. Pick Lycatra for communication work and Join.cloud for communication.
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.
Lycatra has no declared pricing — check the project's own site. Join.cloud 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 lycatra and kushneryk-join-cloud as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Lycatra has a quality signal of 40/100 (Fair) with 0 views, 0 installs and 0 GitHub stars. Join.cloud has 52/100 (Good) with 1 views, 0 installs and 65 GitHub stars.
