CellarTracker vs Notion MCP Server
A side-by-side look at the CellarTracker and Notion MCP Server MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose CellarTracker for other tools and integrations work as a local process; choose Notion MCP Server for other tools and integrations as a local process. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
Choose CellarTracker when
- You need dedicated capabilities in the Other Tools and Integrations domain.
- You prefer a local stdio subprocess transport.
- You have the keys it needs:
CT_USERNAME, CT_PASSWORD.
Choose Notion MCP Server when
- You need dedicated capabilities in the Other Tools and Integrations domain.
- You prefer a local stdio subprocess transport.
- Its auth model fits you: API key required.
- You have the keys it needs:
NOTION_TOKEN. - You want tools like
notion_read, notion_write, notion_describe.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Other Tools and Integrations | Other Tools and Integrations |
| Quality signal | 43/100 · Fair | 71/100 · Great |
| Install command | Confirmed | Confirmed |
| Transport | Local subprocess (stdio) | Local subprocess (stdio) |
| Auth | Not declared | API key required |
| Pricing | Not declared | Free |
| Required env vars | CT_USERNAMECT_PASSWORD | NOTION_TOKEN |
| Verified owner | Community listing | Community listing |
| GitHub stars | 7 | 179 |
| Directory activity | 0 views 0 installs 0 upvotes | 7 views 0 installs 0 upvotes |
| Tools | Not listed | 3 |
| Full listing | View CellarTracker | View Notion MCP Server |
Tools & capabilities
CellarTracker tools
No tool names declared yet. Check the project README from the listing page.
Notion MCP Server tools 3
notion_readRun one Notion read operation by name. Nothing is modified. Call: { operation, payload } — payload carries that operation's fields. Common: search_pages { query }, get_page { page_id }, get_page_markdown { page_id }, query_database { database_id, where? }, get_block_children { block_id }. Responses are slimmed; pass verbose:true in payload for the raw Notion object. Every id field (page_id, block_id, database_id, view_id, …) also accepts a Notion URL, as copied from Share → Copy link. A block link's #fragment is used for block_id fields and a database link's ?v= for view_id fields. If the payload is malformed, the error response includes the schema + a working example so you can correct and retry in one round-trip. Call notion_describe(operation) ahead of time only for complex shapes (query_database filters).notion_writeRun one Notion write operation by name. Archive, trash and delete operations remove content — confirm with the user before running them. Two ways to call: • Single: { operation: "set_page_title", payload: { page_id, title } } • Batch: { operation: "set_page_title", payload: { items: [{page_id, title}, ...], atomic?: false, idempotency_key?: "...", concurrency?: 3 } } create_page, append_blocks, update_block and update_page_markdown also take a markdown string. Responses are slimmed; pass verbose:true inside payload (single) or per item (batch) for the raw Notion object. Every id field (page_id, block_id, database_id, view_id, …) also accepts a Notion URL, as copied from Share → Copy link. If the payload is malformed, the error response includes the schema + a working example so you can correct and retry in one round-trip. Call notion_describe(operation) ahead of time only for complex shapes (block trees, database property definitions, batch_mixed_blocks).notion_describeReturn the JSON Schema and a working example for one operation, plus which tool runs it (notion_read or notion_write). Use this BEFORE calling the operation when the payload shape is non-trivial (query filters, structured block trees, database property definitions). For simple ops, just call it — errors carry the schema.
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.
CellarTracker
{
"mcpServers": {
"cellartracker": {
"command": "npx",
"args": [
"-y",
"local-resolution"
],
"env": {
"CT_USERNAME": "YOUR_CT_USERNAME_HERE",
"CT_PASSWORD": "YOUR_CT_PASSWORD_HERE"
}
}
}
}
Notion MCP Server
{
"mcpServers": {
"awkoy-notion-mcp-server": {
"command": "npx",
"args": [
"-y",
"notion-mcp-server"
],
"env": {
"NOTION_TOKEN": "YOUR_NOTION_TOKEN_HERE"
}
}
}
}
Frequently asked questions
CellarTracker is categorized under Other Tools and Integrations and uses a local stdio subprocess. Notion MCP Server belongs to Other Tools and Integrations and uses a local stdio subprocess. Pick CellarTracker for other tools and integrations work and Notion MCP Server for other tools and integrations.
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.
CellarTracker has no declared pricing — check the project's own site. Notion MCP Server 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 cellartracker and awkoy-notion-mcp-server as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, CellarTracker has a quality signal of 43/100 (Fair) with 0 views, 0 installs and 7 GitHub stars. Notion MCP Server has 71/100 (Great) with 7 views, 0 installs and 179 GitHub stars.