Forage — Web Intelligence & Knowledge Graph vs Kindex

In-depth architectural comparison of the Forage — Web Intelligence & Knowledge Graph and Kindex 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.

Which MCP Server Should You Choose?

Choose Forage — Web Intelligence & Knowledge Graph 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 Forage — Web Intelligence & Knowledge Graph Details

Choose Kindex 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 Kindex Details

Feature & Specification Comparison

Specification	Forage — Web Intelligence & Knowledge Graph Developer Tools	Kindex Developer Tools
Summary	Web intelligence, verified B2B contacts, and a persistent knowledge graph for AI agents.	Persistent knowledge graph and MCP server for AI workflows with git-tracked project context.
Category & Scope	Developer Tools	Developer Tools

Tools & Capabilities Breakdown

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

{
  "mcpServers": {
    "forage-web-intelligence-knowledge-graph": {
      "command": "npx",
      "args": [
        "-y",
        "@anthropic/mcp-proxy",
        "https://ernesta-labs--forage.apify.actor/mcp"
      ]
    }
  }
}

{
  "mcpServers": {
    "kindex": {
      "command": "uvx",
      "args": [
        "--from"
      ]
    }
  }
}

Related MCP Server Comparisons