Airweave Search vs Fetch

A side-by-side look at the Airweave Search and Fetch 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 declaredFetch logoFetchSearch & Data Extraction · Local subprocess (stdio)Web content fetching and conversion for efficient LLM usage.80ExcellentAuth: no auth required

Verdict: choose Airweave Search for search & data extraction work as a local process; choose Fetch for search & data extraction as a local process. 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

Fetch logoChoose Fetch when

  • You need dedicated capabilities in the Search & Data Extraction domain.
  • You prefer a local stdio subprocess transport.
  • Its auth model fits you: No auth required.
  • You want tools like fetch.
Explore Fetch

Feature & specification comparison

Rows where the two servers differ are marked.

SpecAirweave Search logoAirweave SearchFetch logoFetch
CategorySearch & Data ExtractionSearch & Data Extraction
Quality signal30/100 · Emerging80/100 · Excellent
Install commandConfirmedConfirmed
TransportLocal subprocess (stdio)Local subprocess (stdio)
AuthNot declaredNo auth required
PricingNot declaredFree
Required env varsNone listedNone listed
Verified ownerCommunity listing Verified
GitHub stars6,55691,487
Directory activity 1 views 0 installs 0 upvotes 5 views 0 installs 0 upvotes
ToolsNot listed1

Tools & capabilities

Airweave Search tools

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

Fetch tools 1

  • fetchFetches a URL from the internet and extracts its contents as markdown.

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"
      ]
    }
  }
}

Fetch

mcpServers (Claude Desktop / Cursor)
{
  "mcpServers": {
    "fetch": {
      "command": "uvx",
      "args": [
        "mcp-server-fetch"
      ]
    }
  }
}

Frequently asked questions

Airweave Search is categorized under Search & Data Extraction and uses a local stdio subprocess. Fetch belongs to Search & Data Extraction and uses a local stdio subprocess. Pick Airweave Search for search & data extraction work and Fetch 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. Fetch 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 airweave-search and fetch 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. Fetch has 80/100 (Excellent) with 5 views, 0 installs and 91,487 GitHub stars.