Trieve MCP Server

Trieve MCP server is a locally run integration for AI assistants that speak the Model Context Protocol. TypeScript SDK for Mintlify Search.

What you get

Sign Up (1k chunks free) | PDF2MD | Hacker News Search Engine | Documentation | Meet a Maintainer | Discord | Matrix

• 🔒 Self-Hosting in your VPC or on-prem — We have full self-hosting guides for AWS, GCP, Kubernetes generally, and docker compose available on our documentation page here
• 🧠 Semantic Dense Vector Search — Integrates with OpenAI or Jina embedding models and Qdrant to provide semantic vector search
• 🔍 Typo Tolerant Full-Text/Neural Search — Every uploaded chunk is vector'ized with naver/efficient-splade-VI-BT-large-query for typo tolerant, quality neural sparse-vector search
• 🖊️ Sub-Sentence Highlighting — Highlight the matching words or sentences within a chunk and bold them on search to enhance UX for your users. Shout out to the simsearch crate!
• 🌟 Recommendations — Find similar chunks (or files if using grouping) with the recommendation API. Very helpful if you have a platform where users' favorite, bookmark, or upvote content
• 🤖 Convenient RAG API Routes — We integrate with OpenRouter to provide you with access to any LLM you would like for RAG. Try our routes for fully-managed RAG with topic-based memory management or select your own context RAG

What the assistant can call

Once Trieve is connected, these are the calls the assistant has available:

• MacOS — The MacOS tool exposed by this server

Setting it up

@smithery/cli on npm is all you need. Most clients run it directly, so configuration is a few lines and a restart.

Configuration and credentials

You will need 5 environment variables: OPENAI_API_KEY, LLM_API_KEY, PAGEFIND_CDN_BASE_URL, GROQ_API_KEY, STRIPE_WEBHOOK_SECRET. The server will not start without them, which is usually why the tools fail to appear on a first run. Keep credentials in your client's env block or a secrets manager rather than in a file you might commit.

Choosing this one

Among the AI and media services options, the useful question is rarely "what can it do" but "what does it cost you to run" — permissions, credentials, and how much of your context its toolset consumes. Trieve's toolset — MacOS — is a fair guide to whether it matches your workflow. It is maintained by trieve; worth a glance at recent repository activity before you build anything load-bearing on it.

SyncDev reviews every entry in this directory against the project's own documentation before publishing, and revisits them as servers change.

Before you rely on it

• It runs with your machine's permissions. That is convenient and also the reason to think about what you point it at before you approve a tool call.
• Missing credentials fail quietly in some clients — if no tools show up, check the environment block first.
• MCP clients confirm each tool call by default. Leave that on until you have watched what the trieve mcp server does with a few real requests.