Docs MCP vs NameWheel
A side-by-side look at the Docs MCP and NameWheel 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 Docs MCP for communication work over a hosted endpoint; choose NameWheel for communication. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
Choose Docs MCP when
- You need dedicated capabilities in the Communication domain.
- You prefer a remote HTTP/SSE transport.
- Its auth model fits you: No auth required.
- You have the keys it needs:
DOCS_REPO. - You want tools like
search_cometchat_docs, fetch_cometchat_doc_page, get_cometchat_implementation_bundle.
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.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | N NameWheel | |
|---|---|---|
| Category | Communication | Communication |
| Quality signal | 83/100 · Excellent | 53/100 · Good |
| Install command | Confirmed | Not confirmed yet |
| Transport | Remote HTTP/SSE | — |
| Auth | No auth required | API key required |
| Pricing | Free | Free |
| Required env vars | DOCS_REPO | None listed |
Tools & capabilities
Docs MCP tools 4
search_cometchat_docsSearches CometChat documentation including SDK guides (JavaScript, React, iOS, Android, Flutter, React Native), UI Kit references, REST API documentation, integration tutorials, and OpenAPI specs. Returns ranked snippets with titles and direct links to source pages. Pages for the current version of each SDK and UI Kit are preferred over older versions, and each result reports its version label and whether it is current. To reach older docs, pass the `version` filter with that version's label.fetch_cometchat_doc_pageFetches the full content of a single CometChat documentation page by URL or path. Returns the page content as markdown along with title and section metadata. Path can be passed as a full https://www.cometchat.com/docs URL or as a relative path such as '/sdk/javascript/overview'.get_cometchat_implementation_bundleReturns a curated implementation bundle for a named CometChat integration scenario. Each bundle includes prerequisites, install commands, configuration, working code examples, and common pitfalls. Available bundles cover common integration patterns across React, Flutter, iOS, Android, React Native, and the JavaScript SDK.list_cometchat_bundlesLists every available CometChat implementation bundle with its identifier, title, target framework, and last-verified date.
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.
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.
Docs MCP
{
"mcpServers": {
"cometchat-docs-mcp": {
"url": "https://mcp.cometchat.com/mcp"
}
}
}
NameWheel
No confirmed install command for NameWheel yet — follow the setup steps linked from its listing page rather than a guessed package name.
Frequently asked questions
Docs MCP is categorized under Communication and uses a remote HTTP/SSE transport. NameWheel belongs to Communication and uses an install path we have not confirmed yet. Pick Docs MCP for communication work and NameWheel 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.
Docs MCP is listed as free. Auth: no auth required. NameWheel 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 cometchat-docs-mcp and namewheel as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Docs MCP has a quality signal of 83/100 (Excellent) with 3 views, 0 installs and 109 GitHub stars. NameWheel has 53/100 (Good) with 0 views, 0 installs and 0 GitHub stars.