Self-hosted knowledge backend for AI agents with hybrid search and MCP tools
Self-hosted knowledge backend for AI agents with hybrid search and MCP tools. Exposed over MCP by the connapse mcp server, that capability becomes something an assistant can invoke while it works, not something you go and do afterwards.
Stop losing context between AI sessions. Give your agents persistent, searchable memory.
Everything the assistant can do here goes through one of these:
Database — PostgreSQL 17 + pgvector for vector embeddingsBackend — ASP.NET Core 10 Minimal APIsFrontend — Blazor Server (interactive mode)Embeddings — Ollama (default), OpenAI, Azure OpenAI (configurable)LLM — Ollama, OpenAI, Azure OpenAI, Anthropic (configurable)Search — Hybrid vector + keyword with convex combination fusionConnectors — Managed Storage (MinIO default), Filesystem, Amazon S3, Azure Blob Storagev0.4.0 — Communication connectors (Slack, Discord)v0.5.0 — Knowledge platform connectors (Notion, Confluence, GitHub)v1.0.0 — Production-ready stable releasecontainer_create — Create a new container for organizing filescontainer_list — List all containers with document countsYou will need 3 environment variables: CONNAPSE_ADMIN_EMAIL, CONNAPSE_ADMIN_PASSWORD, YOUR_API_KEY. 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.
Being a remote server, there is no local install. You register the endpoint with your client, authorise it once, and the tools appear.
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. Connapse's toolset — Database, Backend, Frontend and 11 more — is a fair guide to whether it matches your workflow. It is maintained by Destrayon; worth a glance at recent repository activity before you build anything load-bearing on it.
This entry was verified against Connapse's own documentation before publication; SyncDev keeps the directory reviewed rather than auto-generated.
| Tool | What it does |
|---|---|
| Database | PostgreSQL 17 + pgvector for vector embeddings |
| Backend | ASP.NET Core 10 Minimal APIs |
| Frontend | Blazor Server (interactive mode) |
| Embeddings | Ollama (default), OpenAI, Azure OpenAI (configurable) |
| LLM | Ollama, OpenAI, Azure OpenAI, Anthropic (configurable) |
| Search | Hybrid vector + keyword with convex combination fusion |
| Connectors | Managed Storage (MinIO default), Filesystem, Amazon S3, Azure Blob Storage |
| v0.4.0 | Communication connectors (Slack, Discord) |
| v0.5.0 | Knowledge platform connectors (Notion, Confluence, GitHub) |
| v1.0.0 | Production-ready stable release |
| container_create | Create a new container for organizing files |
| container_list | List all containers with document counts |
| container_delete | Delete a container |
| container_stats | Get container statistics (documents, chunks, storage, embeddings) |
| Variable | Description | Required |
|---|---|---|
| CONNAPSE_ADMIN_EMAIL | Configuration value read at startup. | Optional |
| CONNAPSE_ADMIN_PASSWORD | Configuration value read at startup. | Optional |
| YOUR_API_KEY | Credential the server authenticates with. | Yes |
Build a programmable telecommunications stack for connecting telephony services with the Internet via a cloud-based utility.
Search built for AI, not humans — semantic web search that returns model-ready content, plus code context.
Answers, not links — delegate questions to Perplexity's search-grounded models and get cited responses back.
Give your assistant a voice — text-to-speech, voice cloning and audio tools from the ElevenLabs API.
Give your assistant a real code sandbox — isolated cloud VMs for actually running the code it writes.
The ML hub in your context window — search models, datasets, papers and run Spaces from the official server.