What is the key difference between Servicegraph and Weav?

Servicegraph belongs to the Developer Tools category with local stdio execution, while Weav belongs to the Developer Tools category with local stdio execution.

How do I install Servicegraph or Weav in Claude Desktop or Cursor?

Copy the mcpServers JSON configuration snippet provided on this page into your claude_desktop_config.json or ~/.cursor/mcp.json file and restart your AI client.

Are Servicegraph and Weav free or paid?

Servicegraph operates under a Free / Open Source model (No auth required). Weav operates under a Free / Open Source model (No auth required).

Which MCP server has more tools and community activity?

Servicegraph lists 0 tools with 0 views and 62 GitHub stars. Weav lists 0 tools with 0 views and 0 GitHub stars.

Can I use both Servicegraph and Weav together in the same MCP host?

Yes! MCP hosts like Claude Desktop, Cursor, Windsurf, Cline, and VS Code support configuring multiple servers under the mcpServers object simultaneously.

Side-by-Side Model Context Protocol Comparison

Servicegraph vs Weav

In-depth architectural comparison of the Servicegraph and Weav 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

Servicegraph

Developer Tools · Local stdio

Quality: 45/100 (Fair) | Auth: No auth required

Weav

Developer Tools · Local stdio

Quality: 32/100 (Emerging) | Auth: No auth required

Verdict Summary: Choose Servicegraph if you need specialized Developer Tools tools running via a local process. Choose Weav if your workspace requires Developer 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 Servicegraph when:

You need dedicated capabilities in the Developer Tools domain.
You prefer local stdio subprocess transport architecture.
Your security boundary fits: No auth required (Free / Open Source).

Explore Servicegraph Details

Choose Weav when:

You need dedicated capabilities in the Developer Tools domain.
You prefer local stdio subprocess transport architecture.
Your security boundary fits: No auth required (Free / Open Source).

Explore Weav Details

Feature & Specification Comparison

Specification	Servicegraph Developer Tools	Weav Developer Tools
Summary	Search 100k+ US professional-services firms by industry, services, location, size, ratings.	Connect AI tools to Weav with MCP. Search conversations, reply to customers, and manage knowledge.
Category & Scope	Developer Tools	Developer Tools
Quality signal

Tools & Capabilities Breakdown

Servicegraph Tools (0)

No explicit tool names declared in metadata yet. Check project README on main listing page.

Weav Tools (0)

No explicit tool names declared in metadata yet. Check project README on main listing page.

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

Servicegraph Configuration

mcpServers (Claude Desktop / Cursor)

{
  "mcpServers": {
    "servicegraph": {
      "command": "npx",
      "args": [
        "-y",
        "skills"
      ]
    }
  }
}

Weav Configuration

mcpServers (Claude Desktop / Cursor)

{
  "mcpServers": {
    "weav": {
      "command": "npx",
      "args": [
        "-y",
        "mcp-remote"
      ]
    }
  }
}

Frequently Asked Questions

Servicegraph is categorized under Developer Tools and uses a local stdio subprocess. In contrast, Weav belongs to Developer Tools using local stdio subprocess. Select Servicegraph when you need capabilities focused on developer tools and Weav when you require tools for developer tools.

More alternatives to Servicegraph More alternatives to Weav Developer Tools category hub