Server comparison
| Server | Tools | Default mode | Multi-user | Docker | Language | License |
|---|---|---|---|---|---|---|
mcp-core |
— | (foundation lib) | — | — | TypeScript + Python | Apache-2.0 |
wet |
4 + 2 | local-relay |
yes (relay) | GHCR | Python | Apache-2.0 |
mnemo |
5 + 2 | local-relay |
yes (relay) | GHCR | Python | Apache-2.0 |
crg |
5 + 2 | local-relay |
yes (relay) | GHCR | Python | Apache-2.0 |
imagine-mcp † |
4 + 2 | local-relay |
yes (relay) | GHCR | Python | Apache-2.0 |
telegram |
6 + 2 | remote-relay |
yes (relay+OAuth) | GHCR | Python | Apache-2.0 |
notion |
7 + 2 | remote-oauth |
yes (relay+OAuth) | GHCR | TypeScript | Apache-2.0 |
email |
6 + 2 | remote-relay |
yes (relay+OAuth) | GHCR | TypeScript | Apache-2.0 |
better-godot-mcp † |
19 + 2 | stdio |
no | GHCR | TypeScript | Apache-2.0 |
workspace |
11 + 2 | stdio |
yes (OAuth) | GHCR | TypeScript | Apache-2.0 |
(† archived — docs kept for reference, project no longer maintained.)
(N + 2 = N domain tools plus the universal help and config tools — see tool layout standard.)
At a glance
Section titled “At a glance”- Most servers default to
local-relay— single-user browser flow, simplest first-run UX. - Notion / Email / Telegram default to remote — team-shared deploy is the common scenario for these.
- Godot defaults to
stdio— no credentials needed, just a Godot-engine spawn. - Workspace defaults to
stdio— you bring your own Google OAuth client, and the first run consents through a loopback redirect. Its HTTP mode is self-host only; there is no hosted instance. - mcp-core is not a server — it’s the shared library every other server consumes (transport, OAuth AS, lifecycle, multi-user primitives).
Which to install first?
Section titled “Which to install first?”For most users:
- wet — search the web. Useful in any agent context.
- mnemo — give the agent a long-term memory. Pairs with wet for “what did we discuss last week?” queries.
- crg — for code-aware workflows; provides token-efficient code-review context in agent calls.
For specific workflows:
- Coding in unfamiliar repo →
crg - Drafting docs/blog →
notion - Image / video tasks →
imagine-mcp - Telegram bot work →
telegram - Email triage →
email - Godot game dev →
better-godot-mcp - Google Docs / Drive / Calendar / Gmail →
workspace
Versioning
Section titled “Versioning”Each server cuts independent releases (vMAJOR.MINOR.PATCH). All servers depend on mcp-core — major version bumps in mcp-core propagate as bumps to all consumers. See each server’s CHANGELOG.
workspace is still pre-1.0: it publishes beta artifacts only (0.1.0-beta.x on npm, :beta on the registries), with no stable tag yet.
License
Section titled “License”Every repo in the stack is Apache-2.0. Several started out MIT and keep the original terms alongside in a LICENSE-MIT file, as the MIT license requires; LICENSE is the one that governs. workspace has been Apache-2.0 from the start, because it vendors Apache-2.0 code from gemini-cli-extensions/workspace and keeps that license for the whole repo.
Forks and self-host welcome — no license fees, no telemetry phoning home.