Coda MCP vs Ritoko
A side-by-side look at the Coda MCP and Ritoko MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose Coda MCP for workplace & productivity work as a local process; choose Ritoko for workplace & productivity as a local process. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
Choose Coda MCP when
- You need dedicated capabilities in the Workplace & Productivity domain.
- You prefer a local stdio subprocess transport.
- Its auth model fits you: API key required.
- You have the keys it needs:
API_KEY. - You want tools like
coda_list_documents, coda_list_pages, coda_create_page.
Choose Ritoko when
- You need dedicated capabilities in the Workplace & Productivity domain.
- You prefer a local stdio subprocess transport.
- You have the keys it needs:
RITOKO_BROWSER.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Workplace & Productivity | Workplace & Productivity |
| Quality signal | 59/100 · Good | 36/100 · Fair |
| Install command | Confirmed | Confirmed |
| Transport | Local subprocess (stdio) | Local subprocess (stdio) |
| Auth | API key required | Not declared |
| Pricing | BYOK (pay the provider) | Not declared |
| Required env vars | API_KEY | RITOKO_BROWSER |
Tools & capabilities
Coda MCP tools 19
coda_list_documentsList or search available documentscoda_list_pagesList pages in the current document with paginationcoda_create_pageCreate a page in the current documentcoda_get_page_contentGet the content of a page as markdowncoda_peek_pagePeek into the beginning of a page and return a limited number of linescoda_replace_page_contentReplace the content of a page with new markdown contentcoda_append_page_contentAppend new markdown content to the end of a pagecoda_duplicate_pageDuplicate a page in the current documentcoda_rename_pageRename a page in the current documentcoda_resolve_linkResolve metadata given a browser link to a Coda objectcoda_list_tablesList tables in a documentcoda_list_columnsList columns in a table- +7 more on the listing page
Ritoko 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.
Coda MCP
{
"mcpServers": {
"orellazi-coda-mcp": {
"command": "npx",
"args": [
"-y",
"coda-mcp@latest"
],
"env": {
"API_KEY": "YOUR_API_KEY_HERE"
}
}
}
}
Ritoko
{
"mcpServers": {
"ritoko": {
"command": "npx",
"args": [
"--yes",
"--prefer-online",
"ritoko@latest"
],
"env": {
"RITOKO_BROWSER": "YOUR_RITOKO_BROWSER_HERE"
}
}
}
}
Frequently asked questions
Coda MCP is categorized under Workplace & Productivity and uses a local stdio subprocess. Ritoko belongs to Workplace & Productivity and uses a local stdio subprocess. Pick Coda MCP for workplace & productivity work and Ritoko for workplace & productivity.
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.
Coda MCP is bring-your-own-key: usage is billed by the API provider you supply a key for. Auth: api key required. Ritoko 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 orellazi-coda-mcp and ritoko as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Coda MCP has a quality signal of 59/100 (Good) with 2 views, 0 installs and 63 GitHub stars. Ritoko has 36/100 (Fair) with 0 views, 0 installs and 1 GitHub stars.
