Airweave Search vs ApeRAG

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

Airweave Search logoAirweave SearchSearch & Data Extraction · Local subprocess (stdio)MCP server for searching Airweave collections with natural language queries.30EmergingAuth: not declaredApeRAG logoApeRAGSearch & Data Extraction · Remote HTTP/SSEProduction-ready RAG platform combining Graph RAG, vector search, and full-text search. Best choice for building your own Knowledge Graph and for Context Engineering55GoodAuth: api key required

Verdict: choose Airweave Search for search & data extraction work as a local process; choose ApeRAG for search & data extraction over a hosted endpoint. You can also run both side by side in one mcpServers block.

Which MCP server should you choose?

Airweave Search logoChoose Airweave Search when

  • You need dedicated capabilities in the Search & Data Extraction domain.
  • You prefer a local stdio subprocess transport.
Explore Airweave Search

ApeRAG logoChoose ApeRAG when

  • You need dedicated capabilities in the Search & Data Extraction domain.
  • You prefer a remote HTTP/SSE transport.
  • Its auth model fits you: API key required.
  • You have the keys it needs: APERAG_API_KEY.
Explore ApeRAG

Feature & specification comparison

Rows where the two servers differ are marked.

SpecAirweave Search logoAirweave SearchApeRAG logoApeRAG
CategorySearch & Data ExtractionSearch & Data Extraction
Quality signal30/100 · Emerging55/100 · Good
Install commandConfirmedConfirmed
TransportLocal subprocess (stdio)Remote HTTP/SSE
AuthNot declaredAPI key required
PricingNot declaredFree
Required env varsNone listedAPERAG_API_KEY
Verified ownerCommunity listingCommunity listing
GitHub stars6,5561,322
Directory activity 1 views 0 installs 0 upvotes 3 views 0 installs 0 upvotes
ToolsNot listedNot listed

Tools & capabilities

Airweave Search tools

No tool names declared yet. Check the project README from the listing page.

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

Airweave Search

mcpServers (Claude Desktop / Cursor)
{
  "mcpServers": {
    "airweave-search": {
      "command": "uvx",
      "args": [
        "airweave-sdk"
      ]
    }
  }
}

ApeRAG

mcpServers (Claude Desktop / Cursor)
{
  "mcpServers": {
    "apecloud-aperag": {
      "url": "http://localhost:8000/mcp/"
    }
  }
}

Frequently asked questions

Airweave Search is categorized under Search & Data Extraction and uses a local stdio subprocess. ApeRAG belongs to Search & Data Extraction and uses a remote HTTP/SSE transport. Pick Airweave Search for search & data extraction work and ApeRAG for search & data extraction.

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.

Airweave Search has no declared pricing — check the project's own site. ApeRAG is listed as free. Auth: api key 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 airweave-search and apecloud-aperag as separate keys in the same mcpServers object, and your assistant will call tools from either one.

On AllMCPs, Airweave Search has a quality signal of 30/100 (Emerging) with 1 views, 0 installs and 6,556 GitHub stars. ApeRAG has 55/100 (Good) with 3 views, 0 installs and 1,322 GitHub stars.