Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
git clone --depth 1 https://github.com/airweave-ai/airweaveWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/rules/airweave-ai/airweave/mcp-server)<a href="https://agentmods.dev/rules/airweave-ai/airweave/mcp-server"><img src="https://agentmods.dev/badge/rules/airweave-ai/airweave/mcp-server/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/rules/airweave-ai/airweave/mcp-server"><img src="https://agentmods.dev/badge/rules/airweave-ai/airweave/mcp-server.svg" alt="Reviewed on agentmods" width="80" height="20"></a>What it costs to keep this loaded
Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.00000 | $0.02027 |
| Opus 5.5 | $0.00000 | $0.00811 |
| Sonnet 5.5 | $0.00000 | $0.00405 |
| Haiku 4.5 | $0.00000 | $0.00203 |
Grade A, and why
mcp-server scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 1mo ago.
A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.
Nothing flagged
None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.
How it starts
The opening of the file, as written. The whole thing — 176 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Airweave MCP Server Architecture
Overview
The Airweave MCP Server provides search capabilities for AI assistants through the Model Context Protocol (MCP). It supports both local desktop clients and cloud-based AI platforms, with API key and OAuth 2.0 authentication.
Deployment Modes
1. Local Mode (Desktop AI Clients)
- Transport: stdio (standard input/output)
- Target: Claude Desktop, Cursor, VS Code
- Entry Point:
src/index.ts - Installation:
npx airweave-mcp-search - Architecture: Single-tenant, one server instance per user
- Authentication: API key from environment variables
2. Hosted Mode (Cloud AI Platforms)
- Transport: Streamable HTTP (MCP 2025-03-26)
- Target: OpenAI Agent Builder, Cursor (remote), any HTTP MCP client
- Entry Point:
src/index-http.ts - Deployment: Azure Kubernetes Service
- URL:
https://mcp.airweave.ai/mcp - Architecture: Fully stateless — a fresh McpServer + transport is created per request
- Authentication: API key (via headers) or OAuth 2.0 (via Auth0)
Architecture Components
Core Server (src/server.ts)
- McpServer: MCP server factory —
createMcpServer(config)returns an isolated instance - Tool Registration: Dynamic tool creation based on collection (
search-{collection},get-config) - Airweave Client: API client for search operations (
src/api/airweave-client.ts)
Streamable HTTP Server (src/index-http.ts)
- Express App: HTTP server with health checks and info endpoints
- Streamable HTTP Transport: MCP 2025-03-26 transport, stateless (no sessions)
- Request Handling: POST
/mcp— creates fresh McpServer per request - Dual Auth:
resolveAuthmiddleware resolves API key vs OAuth per request - OAuth Router:
mcpAuthRouterfrom MCP SDK handles OAuth protocol endpoints when enabled
Authentication (src/auth/)
resolveAuth middleware (in index-http.ts)
Priority-based auth resolution per request:
X-API-Keyheader present → API key auth, no JWT checkAuthorization: Bearer <token>with OAuth enabled → attempt JWT verification viaAuth0OAuthProvider.verifyAccessToken; if valid → OAuth path (req.authset); if invalid → fallback to API key- No credential → 401
What this file has done since we first saw it
Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.
- 1mo ago First seen · 176 lines · 2,027 tokens per session scan A 35196c6056e7
mcp-server is a cursor rule published in the GitHub repository airweave-ai/airweave (6,556 stars, last pushed 4mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 2,027 tokens. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other cursor rules, from other repositories
gateway
Messenger gateway architecture, session store, and the Telegram and Pachca adapter conventions.
provider-devin
Devin transport framing, identity, and response semantics.
backend-rules
A Cursor rule named backend-rules covering backend development, project structure, technology choices, runtime environment, and main process. Cursor is a coding editor with rules that guide how an agent works in a project.
ddd-design-guide
Apply when designing or refactoring domain models, services, stores, or discussing DDD (Domain-Driven Design) architecture. Also apply when working on business logic layers, API modules, or planning domain boundaries and migrations.
backend-python
Cursor rule "backend-python" from coeusyk/inference-x, covering backend python rules, stack assumptions, code style, fastapi conventions and schema conventions.
pn-rust-backend
Rust backend style, env, and error handling. Use for API and server code (Actix-web, Axum).