A side-by-side look at the Openapi To 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.
Verdict: choose Openapi To 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 block.
mcpServersRows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Developer Tools | Knowledge & Memory |
| Quality signal | 44/100 · Fair | 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 | 7 | 67 |
| Directory activity | 4 views 0 installs 0 upvotes | 18 views 12 installs 6 upvotes |
| Tools | Not listed | Not listed |
| Full listing | View Openapi To MCP | View Scrivener MCP |
No tool names declared yet. Check the project README from the listing page.
No tool names declared yet. Check the project README from the listing page.
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.
No confirmed install command for Openapi To MCP yet — follow the setup steps linked from its listing page rather than a guessed package name.
{
"mcpServers": {
"writerslogic-scrivener-mcp": {
"command": "npx",
"args": [
"-y",
"scrivener-setup"
]
}
}
}