Infrawise vs Scrivener MCP

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

InfrawiseCloud Platforms · Local subprocess (stdio)Cloud infrastructure analysis for AI coding assistants — detects IaC drift, missing indexes, security gaps, and performance anti-patterns across AWS services and databases. 13 tools, works with Claude Code and Cursor.64GoodAuth: api key required

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 Infrawise for cloud platforms work as a local process; 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?

Choose Infrawise when

You need dedicated capabilities in the Cloud Platforms domain.
You prefer a local stdio subprocess transport.
Its auth model fits you: API key required.
You want tools like get_infra_overview, get_graph_summary, get_table_schema.

Explore Infrawise

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.

Explore Scrivener MCP

Feature & specification comparison

Rows where the two servers differ are marked.

Spec	Infrawise	Scrivener MCP
Category	Cloud Platforms	Knowledge & Memory
Quality signal	64/100 · Good	61/100 · Good
Install command	Confirmed	Confirmed
Transport	Local subprocess (stdio)	Local subprocess (stdio)
Auth	API key required	No auth required
Pricing	Free	Free
Required env vars	None listed	None listed
Verified owner	Community listing	Community listing
GitHub stars	22	67
Directory activity	3 views 0 installs 0 upvotes	18 views 12 installs 6 upvotes
Tools	22	Not listed
Full listing	View Infrawise	View Scrivener MCP

Tools & capabilities

Infrawise tools 22

get_infra_overviewComplete snapshot — services, counts, high-severity findings, `configured` flag (data age and per-source status ride the `dataHealth` block on every response)
get_graph_summaryFull infrastructure graph — all nodes, edges, and findings
get_table_schemaColumn-level schema for named tables/collections — types, PKs, FKs, indexes, DynamoDB keys/billing mode, cost signal (no row data)
analyze_functionIssues in a specific function — scans, missing indexes, N+1, trigger event shapes, missing IAM permissions; returns every same-named file as a separate match, or bind to one with the optional `file` input; names refused Lambda links and why (`unresolvedLambdas`)
suggest_gsiExact GSI config for a DynamoDB table + attribute — names the existing index instead when one already covers it
postgres_index_suggestionsExact `CREATE INDEX` SQL for your actual table
suggest_mongo_indexExact `createIndex` command for a MongoDB collection + field
mysql_index_suggestionsExact `ALTER TABLE ADD INDEX` SQL for your MySQL table
get_queue_detailsSQS queues — DLQ status, encryption, FIFO type, visibility timeout, message counts
get_api_routesAPI Gateway APIs (REST, HTTP, WebSocket) — routes, HTTP methods, paths, and Lambda integrations
get_topic_detailsSNS topics — subscription counts, protocols, and filter policies (required message attributes per subscription)
get_secrets_overviewSecrets Manager — names, rotation status, and key names inferred from code (values never included)
+10 more on 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.

Infrawise

mcpServers (Claude Desktop / Cursor)

{
  "mcpServers": {
    "sidd27-infrawise": {
      "command": "npx",
      "args": [
        "-y",
        "infrawise"
      ]
    }
  }
}

Scrivener MCP

mcpServers (Claude Desktop / Cursor)

{
  "mcpServers": {
    "writerslogic-scrivener-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "scrivener-setup"
      ]
    }
  }
}

Frequently asked questions

Infrawise is categorized under Cloud Platforms and uses a local stdio subprocess. Scrivener MCP belongs to Knowledge & Memory and uses a local stdio subprocess. Pick Infrawise for cloud platforms 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.

Infrawise is listed as free. Auth: api key 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 sidd27-infrawise and writerslogic-scrivener-mcp as separate keys in the same mcpServers object, and your assistant will call tools from either one.

On AllMCPs, Infrawise has a quality signal of 64/100 (Good) with 3 views, 0 installs and 22 GitHub stars. Scrivener MCP has 61/100 (Good) with 18 views, 12 installs and 67 GitHub stars.