Airweave Search
Let your coding agent query indexed docs and data in an Airweave collection with natural language instead of wiring a custom search API.
Overview
Airweave Search is an MCP server for the Build phase that lets agents run natural-language queries against a configured Airweave collection.
What is this MCP server?
- Natural-language search tools against a single Airweave collection per connection
- stdio npm package airweave-mcp-search v0.9.9 plus streamable-http remote at mcp.airweave.ai/mcp
- Auth via AIRWEAVE_API_KEY or X-API-Key header plus AIRWEAVE_COLLECTION or X-Collection-Readable-ID
- Optional AIRWEAVE_BASE_URL override defaulting to https://api.airweave.ai
- Server version 0.9.9
- 1 npm package with stdio transport
- 1 streamable-http remote endpoint
Community signal: 6.4k GitHub stars.
What problem does it solve?
Your agent needs answers from indexed knowledge, but bolting on a custom vector search API for every side project wastes ship time.
Who is it for?
Indie builders with an existing Airweave collection who want agent-side retrieval without writing search microservices.
Skip if: Teams with no Airweave account, no indexed collection yet, or needs for multi-tenant search orchestration outside one collection ID.
What do I get? / Deliverables
After registration, the agent can search your Airweave collection through MCP tools using your API key and collection ID.
- MCP tools callable by the agent for NL search over one collection
- Configured stdio or remote MCP entry in the agent manifest
Recommended MCP Servers
Journey fit
Canonical shelf is Build because you wire MCP after you have a product and a collection to search—not during early idea research. Integrations fits MCP transport, API key, and collection ID setup that connects agent context to external retrieval infrastructure.
How it compares
MCP retrieval bridge over Airweave collections, not a document-ingestion or embedding pipeline skill.
Common Questions / FAQ
Who is Airweave Search for?
Solo and indie developers using AI coding agents who already use Airweave and want natural-language search exposed as MCP tools.
When should I use Airweave Search?
Use it during Build when wiring agent context to private or project knowledge that lives in a specific Airweave collection.
How do I add Airweave Search to my agent?
Install the npm package airweave-mcp-search for stdio or add the remote https://mcp.airweave.ai/mcp with X-API-Key and X-Collection-Readable-ID, set AIRWEAVE_API_KEY and AIRWEAVE_COLLECTION for local runs, then restart the agent.