In-depth architectural comparison of the Networkx MCP Server and Growthbook 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
Networkx MCP Server
Data Science Tools · Local stdio
Quality: 53/100 (Good) | Auth: No auth required
Growthbook MCP
Data Science Tools · Local stdio
Quality: 67/100 (Great) | Auth: API Key required
Verdict Summary: Choose Networkx MCP Server if you need specialized Data Science Tools tools running via a local process. Choose Growthbook MCP if your workspace requires Data Science Tools integration with local subprocess execution. Both servers can be configured concurrently in your client's mcpServers manifest.
Which MCP Server Should You Choose?
Choose Networkx MCP Server when:
You need dedicated capabilities in the Data Science Tools domain.
You prefer local stdio subprocess transport architecture.
Your security boundary fits: No auth required (Free / Open Source).
Primary tools included: NetworkX graph creation and editing, Citation analysis through CrossRef, Centrality, PageRank, and community algorithms.
The first NetworkX integration for Model Context Protocol, enabling graph analysis and visualization directly in AI conversations. Supports 13 operations including centrality algorithms, community detection, PageRank, and graph visualization.
Tools for creating and interacting with GrowthBook feature flags and experiments.
Category & Scope
Tools & Capabilities Breakdown
Networkx MCP Server Tools (6)
NetworkX graph creation and editing
Citation analysis through CrossRef
Centrality, PageRank, and community algorithms
PNG graph visualization
CSV import and JSON export
BibTeX citation export
Growthbook MCP Tools (4)
growthbook_api_read
Make an authenticated GET request to the GrowthBook REST API. Use path (+ optional query string) exactly as shown in skill workflows that mention gb-call GET. Paths typically start with /api/v1/ or /api/v2/. Returns the raw response body on success. Queries the GrowthBook REST API — see https://docs.growthbook.io/api (OpenAPI: https://api.growthbook.io/api/v1/openapi.yaml).
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).
Networkx MCP Server is categorized under Data Science Tools and uses a local stdio subprocess. In contrast, Growthbook MCP belongs to Data Science Tools using local stdio subprocess. Select Networkx MCP Server when you need capabilities focused on data science tools and Growthbook MCP when you require tools for data science tools.
Make an authenticated mutating request (POST, PUT, PATCH, or DELETE) to the GrowthBook REST API. Use method + path (+ optional JSON body) exactly as shown in skill workflows that mention gb-call with those methods. Paths typically start with /api/v1/ or /api/v2/. Returns the raw response body on success. Mutates the GrowthBook REST API — see https://docs.growthbook.io/api (OpenAPI: https://api.growthbook.io/api/v1/openapi.yaml).
growthbook_list_skills
List available GrowthBook agent skills (name + description). Use growthbook_read_skill to load the full workflow for a skill before acting. Skills encode how to accomplish GrowthBook tasks well; use growthbook_api_read / growthbook_api_write to execute the REST calls they describe.
growthbook_read_skill
Return the full markdown content of a GrowthBook skill by name (from growthbook_list_skills). Follow the skill's workflow; when it shows `gb-call <METHOD> <PATH> [body]`, use growthbook_api_read for GET and growthbook_api_write for POST/PUT/PATCH/DELETE.