NameWheel vs Omnicord
A side-by-side look at the NameWheel and Omnicord MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
N
NameWheelCommunicationFair random picks with the wheel in your chat: pick names, split teams, run certified draws.53GoodAuth: api key requiredVerdict: choose NameWheel for communication work; choose Omnicord for communication as a local process. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
NChoose NameWheel when
- You need dedicated capabilities in the Communication domain.
- Its auth model fits you: API key required.
- You want tools like
spin_wheel, make_teams, open_wheel_link.
Choose Omnicord when
- You need dedicated capabilities in the Communication domain.
- You prefer a local stdio subprocess transport.
- Its auth model fits you: API key required.
- You have the keys it needs:
DISCORD_TOKEN. - You want tools like
get_rate_limit_status, get_bot_info, run_setup_check.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | N NameWheel | |
|---|---|---|
| Category | Communication | Communication |
| Quality signal | 53/100 · Good | 65/100 · Great |
| Install command | Not confirmed yet | Confirmed |
| Transport | — | Local subprocess (stdio) |
| Auth | API key required | API key required |
| Pricing | Free | Free |
| Required env vars | None listed | DISCORD_TOKEN |
Tools & capabilities
NameWheel tools 8
spin_wheelPick one or more winners at random from a list of names or options, and show the wheel spinning to the result in the chat. Use it whenever the person wants something chosen at random: a student to answer, who goes first, where to eat, a raffle winner among friends. Works without an account. The pick is fair (a cryptographic random number generator), but it is not a certified record; when other people need to be able to check the result later, use certified_draw instead.make_teamsSplit a list of names into random teams or groups of even size, and show them as cards in the chat. Use it for class groups, project teams, game sides, rotations. Give either how many teams or how many people per team. Works without an account.open_wheel_linkMake a namewheel.org link that opens the full NameWheel wheel with these names already loaded, for spinning on a projector, a stream or a shared screen with sound, modes and themes. Works without an account. Commas inside a name become spaces in the link.certified_drawRun a TrueSpin certified draw on NameWheel: the winner is sealed by NameWheel's server before it is revealed, randomness from this connection is added, and the result is published on a permanent public proof page (namewheel.org/v/CODE) that anyone can check, with a button that recomputes the draw. Use it when the result must be provable to other people: a class prize, a team decision, a draw announced to a group. IMPORTANT: the title, every entry and the winner become public on the proof page, so only use names the person is happy to publish, and tell them so. Needs a connected NameWheel account (free). To draw against a list locked earlier with freeze_list, pass frozen_code instead of entries.freeze_listLock a list of entries in public before a draw, at namewheel.org/f/CODE, with a fingerprint and the exact time. Nobody can add or remove a name after that, and when certified_draw later uses this list (frozen_code), the frozen page links to the result. Use it when entries close before the draw happens. The title and every entry are public. Needs a connected NameWheel account (free).verify_drawCheck whether a NameWheel certified draw is genuine, from its code or its namewheel.org/v/ link: recomputes the winner from the published secret, the added randomness and the entries, checks the commitment made before the spin, and checks NameWheel's Ed25519 signature on the record. Also says how many draws the host ran on this exact list. Use it when someone asks whether a draw or a giveaway result was real. Works without an account.
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.
NameWheel
No confirmed install command for NameWheel yet — follow the setup steps linked from its listing page rather than a guessed package name.
Omnicord
{
"mcpServers": {
"orygnscode-omnicord": {
"command": "npx",
"args": [
"-y",
"@orygn/omnicord"
],
"env": {
"DISCORD_TOKEN": "YOUR_DISCORD_TOKEN_HERE"
}
}
}
}
Frequently asked questions
NameWheel is categorized under Communication and uses an install path we have not confirmed yet. Omnicord belongs to Communication and uses a local stdio subprocess. Pick NameWheel for communication work and Omnicord 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. NameWheel has no confirmed install command yet — follow its own setup instructions.
NameWheel is listed as free. Auth: api key required. Omnicord is listed as free. Auth: api key required. 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 namewheel and orygnscode-omnicord as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, NameWheel has a quality signal of 53/100 (Good) with 0 views, 0 installs and 0 GitHub stars. Omnicord has 65/100 (Great) with 9 views, 0 installs and 8 GitHub stars.