What is the main functional difference between Commonspecs and Scrivener MCP?

Commonspecs 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 Commonspecs for developer tools work and Scrivener MCP for knowledge & memory.

How do I install Commonspecs or Scrivener MCP in Claude Desktop, Cursor, or Windsurf?

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. Commonspecs has no confirmed install command yet — follow its own setup instructions.

Are Commonspecs and Scrivener MCP free to use, or do they require API keys?

Commonspecs has no declared pricing — check the project's own site. 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.

Can I run both Commonspecs and Scrivener MCP at the same time in my AI client?

Yes. MCP clients support multiple servers: add commonspecs and writerslogic-scrivener-mcp as separate keys in the same mcpServers object, and your assistant will call tools from either one.

Which MCP server has higher directory engagement and quality ratings?

On AllMCPs, Commonspecs has a quality signal of 37/100 (Fair) with 0 views, 0 installs and 0 GitHub stars. Scrivener MCP has 61/100 (Good) with 18 views, 12 installs and 67 GitHub stars.

Commonspecs vs Scrivener MCP

A side-by-side look at the Commonspecs and Scrivener MCP MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.

CommonspecsDeveloper ToolsProduct and service specs with per-field confidence, plus dated price offers.37FairAuth: not declared

Scrivener MCPKnowledge & Memory · Local subprocess (stdio)Connect Scrivener 3 writing projects to Claude and other AI assistants. 47 tools for document management, writing analysis, semantic search, character/plot memory, and content enhancement. Progressive skill loading, relationship engine with HMS triplets, and JS fallback for offline semantic search. npm i -g scrivener-mcp61GoodAuth: no auth required

Verdict: choose Commonspecs 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.

Spec	C Commonspecs	Scrivener MCP
Category	Developer Tools	Knowledge & Memory
Quality signal	37/100 · Fair	61/100 · Good
Install command	Not confirmed yet	Confirmed
Transport	—	Local subprocess (stdio)
Auth	Not declared	No auth required
Pricing	Not declared	Free
Required env vars	None listed	None listed
Verified owner	Community listing	Community listing
GitHub stars	—	67
Directory activity	0 views 0 installs 0 upvotes	18 views 12 installs 6 upvotes
Tools	Not listed	Not listed
Full listing	View Commonspecs	View Scrivener MCP

Commonspecs vs Scrivener MCP

Which MCP server should you choose?

Choose Commonspecs when

Choose Scrivener MCP when

Feature & specification comparison

Tools & capabilities

Commonspecs tools

Scrivener MCP tools

Ready-to-paste client configs

Commonspecs

Scrivener MCP

Frequently asked questions