LensHub vs Scrivener MCP

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

L
LensHubKnowledge & Memory
Team knowledge from 20 connectors, served to any MCP agent — classified, scored, access-controlled.38FairAuth: not declared
Scrivener MCP logoScrivener 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-mcp65GreatAuth: no auth required

Verdict: choose LensHub for knowledge & memory 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?

L
Choose LensHub when

  • You need dedicated capabilities in the Knowledge & Memory domain.
Explore LensHub

Scrivener MCP logoChoose 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.
Explore Scrivener MCP

Feature & specification comparison

Rows where the two servers differ are marked.

Spec
L
LensHub
Scrivener MCP logoScrivener MCP
CategoryKnowledge & MemoryKnowledge & Memory
Quality signal38/100 · Fair65/100 · Great
Install commandNot confirmed yetConfirmed
Transport—Local subprocess (stdio)
AuthNot declaredNo auth required
PricingNot declaredFree
Required env varsNone listedNone listed
Verified ownerCommunity listingCommunity listing
GitHub stars—68
Directory activity 0 views 0 installs 0 upvotes 20 views 12 installs 6 upvotes
ToolsNot listedNot listed

Tools & capabilities

LensHub 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.

LensHub

No confirmed install command for LensHub yet — follow the setup steps linked from its listing page rather than a guessed package name.

Scrivener MCP

mcpServers (Claude Desktop / Cursor)
{
  "mcpServers": {
    "writerslogic-scrivener-mcp": {
      "command": "npx",
      "args": [
        "scrivener-mcp"
      ]
    }
  }
}

Frequently asked questions

LensHub is categorized under Knowledge & Memory and uses an install path we have not confirmed yet. Scrivener MCP belongs to Knowledge & Memory and uses a local stdio subprocess. Pick LensHub for knowledge & memory 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. LensHub has no confirmed install command yet — follow its own setup instructions.

LensHub 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.

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

On AllMCPs, LensHub has a quality signal of 38/100 (Fair) with 0 views, 0 installs and 0 GitHub stars. Scrivener MCP has 65/100 (Great) with 20 views, 12 installs and 68 GitHub stars.