Trace MCP vs Scrivener MCP — MCP Server Comparison | AllMCPs
Side-by-Side Model Context Protocol Comparison
Trace MCP vs Scrivener MCP
In-depth architectural comparison of the Trace MCP and Scrivener MCP MCP servers. Compare execution transports, security boundaries, tool capabilities, quality scores, and ready-to-paste client installation snippets for Claude, Cursor, Windsurf, and VS Code.
At a Glance & Executive Verdict
Trace MCP
Knowledge & Memory · Remote HTTP/SSE
Quality: 63/100 (Good) | Auth: No auth required
Scrivener MCP
Knowledge & Memory · Local stdio
Quality: 61/100 (Good) | Auth: No auth required
Verdict Summary: Choose Trace MCP if you need specialized Knowledge & Memory tools running via a hosted cloud SSE transport. Choose Scrivener MCP if your workspace requires Knowledge & Memory integration with local subprocess execution. Both servers can be configured concurrently in your client's mcpServers manifest.
Which MCP Server Should You Choose?
Choose Trace MCP when:
You need dedicated capabilities in the Knowledge & Memory domain.
You prefer remote streaming HTTP/SSE transport architecture.
Your security boundary fits: No auth required (Free / Open Source).
Primary tools included: Cross-language dependency graph indexing, Framework-aware understanding of routes, ORM, DI, and rendering, Incremental updates to keep the graph fresh.
Framework-aware code intelligence that indexes source code into a cross-language dependency graph. Understands framework semantics — routes, ORM relations, component rendering, DI trees — for navigation, impact analysis, call graphs, refactoring, security scanning, and cross-session memory.
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-mcp
Tools & Capabilities Breakdown
Trace MCP Tools (6)
Cross-language dependency graph indexing
Framework-aware understanding of routes, ORM, DI, and rendering
Incremental updates to keep the graph fresh
Supports code and markdown vaults with unified graph model
Provides APIs for impact analysis, usage search, and refactoring
Ships with a GPU-accelerated desktop graph explorer app
Scrivener MCP Tools (6)
Ready-to-Paste Client Configurations
Paste either (or both) of these JSON server blocks into your client config file (e.g. claude_desktop_config.json or ~/.cursor/mcp.json).
Trace MCP is categorized under Knowledge & Memory and uses a remote streaming HTTP/SSE transport. In contrast, Scrivener MCP belongs to Knowledge & Memory using local stdio subprocess. Select Trace MCP when you need capabilities focused on knowledge & memory and Scrivener MCP when you require tools for knowledge & memory.