Notion MCP Server vs FluxDown
A side-by-side look at the Notion MCP Server and FluxDown MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose Notion MCP Server for other tools and integrations work as a local process; choose FluxDown for other tools and integrations over a hosted endpoint. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
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.
Choose FluxDown when
- You need dedicated capabilities in the Other Tools and Integrations domain.
- You prefer a remote HTTP/SSE transport.
- Its auth model fits you: No auth required.
- You want tools like
download_add, download_list, download_get.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Other Tools and Integrations | Other Tools and Integrations |
| Quality signal | 71/100 · Great | 64/100 · Good |
| Install command | Confirmed | Confirmed |
| Transport | Local subprocess (stdio) | Remote HTTP/SSE |
| Auth | API key required | No auth required |
| Pricing | Free | Free |
| Required env vars | NOTION_TOKEN | None listed |
| Verified owner | Community listing | Community listing |
| GitHub stars | 179 | 4,962 |
| Directory activity | 7 views 0 installs 0 upvotes | 10 views 0 installs 0 upvotes |
| Tools | 3 | 10 |
| Full listing | View Notion MCP Server | View FluxDown |
Tools & capabilities
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.
FluxDown tools 10
download_addCreate a download task (HTTP/HTTPS, FTP, magnet, BitTorrent)download_listList tasks with progress/speed/status, optional status filterdownload_getGet a single task by IDdownload_pausePause / resume one taskdownload_pause_allPause / resume all tasksdownload_removeRemove a task, optionally deleting downloaded filesqueue_listList named queues and their configurationrss_listList RSS subscriptions with their configuration and runtime staterss_addSubscribe to an RSS feed and start polling it on a schedulerss_removeDelete an RSS subscription and the items it collected
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.
Notion MCP Server
{
"mcpServers": {
"awkoy-notion-mcp-server": {
"command": "npx",
"args": [
"-y",
"notion-mcp-server"
],
"env": {
"NOTION_TOKEN": "YOUR_NOTION_TOKEN_HERE"
}
}
}
}
FluxDown
{
"mcpServers": {
"zerx-lab-fluxdown": {
"url": "http://127.0.0.1:17800/mcp"
}
}
}
Frequently asked questions
Notion MCP Server is categorized under Other Tools and Integrations and uses a local stdio subprocess. FluxDown belongs to Other Tools and Integrations and uses a remote HTTP/SSE transport. Pick Notion MCP Server for other tools and integrations work and FluxDown 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.
Notion MCP Server is listed as free. Auth: api key required. FluxDown is listed as free. Auth: no auth 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 awkoy-notion-mcp-server and zerx-lab-fluxdown as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Notion MCP Server has a quality signal of 71/100 (Great) with 7 views, 0 installs and 179 GitHub stars. FluxDown has 64/100 (Good) with 10 views, 0 installs and 4,962 GitHub stars.