BlockDex MCP vs Scrivener MCP
A side-by-side look at the BlockDex MCP and Scrivener MCP MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
B
BlockDex MCPDeveloper ToolsBlockDex: Search shadcn-compatible components across public registries.24EmergingAuth: no auth requiredVerdict: choose BlockDex MCP for developer tools work; choose Scrivener MCP for knowledge & memory as a local process. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
BChoose BlockDex MCP when
- You need dedicated capabilities in the Developer Tools domain.
- Its auth model fits you: No auth required.
Choose Scrivener MCP when
- You need dedicated capabilities in the Knowledge & Memory domain.
- You prefer a local stdio subprocess transport.
- Its auth model fits you: No auth required.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | B BlockDex MCP | |
|---|---|---|
| Category | Developer Tools | Knowledge & Memory |
| Quality signal | 24/100 · Emerging | 61/100 · Good |
| Install command | Not confirmed yet | Confirmed |
| Transport | — | Local subprocess (stdio) |
| Auth | No auth required | No auth required |
| Pricing | Free | Free |
| Required env vars | None listed | None listed |
| Verified owner | Community listing | Community listing |
| GitHub stars | 0 | 67 |
| Directory activity | 0 views 0 installs 0 upvotes | 18 views 12 installs 6 upvotes |
| Tools | Not listed | Not listed |
| Full listing | View BlockDex MCP | View Scrivener MCP |
Tools & capabilities
BlockDex MCP tools
No tool names declared yet. Check the project README from the listing page.
Scrivener MCP 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.
BlockDex MCP
No confirmed install command for BlockDex MCP yet — follow the setup steps linked from its listing page rather than a guessed package name.
Scrivener MCP
{
"mcpServers": {
"writerslogic-scrivener-mcp": {
"command": "npx",
"args": [
"-y",
"scrivener-setup"
]
}
}
}
Frequently asked questions
BlockDex MCP is categorized under Developer Tools and uses an install path we have not confirmed yet. Scrivener MCP belongs to Knowledge & Memory and uses a local stdio subprocess. Pick BlockDex MCP for developer tools work and Scrivener MCP for knowledge & memory.
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. BlockDex MCP has no confirmed install command yet — follow its own setup instructions.
BlockDex MCP is listed as free. Auth: no auth required. Scrivener MCP 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 blockdex-mcp and writerslogic-scrivener-mcp as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, BlockDex MCP has a quality signal of 24/100 (Emerging) with 0 views, 0 installs and 0 GitHub stars. Scrivener MCP has 61/100 (Good) with 18 views, 12 installs and 67 GitHub stars.
