Connapse
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
Connapse is a retrieval-augmented knowledge base with four primary tools:
container_list, search_knowledge, list_files, and get_document.
Routing rules for question-answering:
If the user's question (or the prior conversation) names a specific container, call
search_knowledgedirectly on that container. Do NOT callcontainer_listfirst — the container is already known.Only call
container_listwhen the relevant container is genuinely unknown and cannot be inferred from context. After it returns, callsearch_knowledgeon the chosen container.Use
list_filesonly for inventory questions ("what files are in X?", "list the docs under /folder"). Never uselist_filesas a substitute forsearch_knowledgewhen the user is asking about file CONTENT.Use
get_documentonly whensearch_knowledgehas returned a specificDocumentIdyou need to read in full, or when the user named an exact file by path.
Enumerating files and reading them one by one to answer content questions
will exceed context and produce worse answers than a single
search_knowledge call.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {} |
| logging | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| append_to_fileA | Add text to the end of an existing text file (.md, .txt, .log, ...) and reindex it. The text goes on exactly as given, so start it with a newline to put it on a new line. The file keeps its ID, path and added date; appends to one file through this server at once all land. |
| request_deletionsA | Ask your owner to approve several deletions at once: up to 50 items, each a file (kind "file", container, target = file id or path), a folder (kind "folder", container, target = folder path), an empty container (kind "container", container = its id or name), a memory space (kind "memory_space", container = the space's id or name) or a memory fact (kind "fact", target = the fact id), with a short reason the owner reads. Every item is checked now; if any can't be deleted nothing is asked, and the error names each bad item. Nothing is deleted yet: the owner approves all, some or none on the Approvals page, and Connapse then deletes the approved items itself, skipping any that are gone or changed since you asked. Call deletion_status with the returned id (and waitSeconds) to read each item's outcome; don't delete the items yourself. |
| list_filesA | Lists folder entries and document IDs at a path within a container (does NOT return file contents — for content questions, use |
| memory_forgetA | Delete a fact for good, with every earlier and later version of it from corrections. Nothing of it is kept. To record that a value changed, use memory_correct instead. If your token asks before deleting, nothing is deleted yet: the call returns a deletion batch that Connapse carries out itself once your owner approves it. Read the outcome with deletion_status; don't repeat the call. |
| search_knowledgeA | Search a container using semantic, keyword, or hybrid mode (Hybrid is the default and works well without tuning). Returns ranked passages with citations, scores, and document IDs. If the first query returns thin results, refine the query and call again. |
| memory_correctA | Replace a fact and keep the old one in history. kind="changed": the world changed, so the old fact ends on |
| memory_timelineA | A subject's facts in date order, ended and corrected ones included: how its values changed over time. Name a |
| container_describeA | Returns an agent-optimized description of a knowledge scope — container or source: its description and document statistics. Use this to understand what a scope covers before querying via search_knowledge, or when container_list output is insufficient to choose between them. The response also echoes the server's tool-routing instructions for clients that don't surface them on connect. |
| delete_fileA | Delete one file, or up to 100 with 'fileIds', and all their chunks and vectors. To update a file, delete it first then re-upload with upload_file. With 'fileIds' it returns per-file success/failure results. If your token asks before deleting, nothing is deleted yet: the call returns a deletion batch that Connapse carries out itself once your owner approves it. Read the outcome with deletion_status; don't repeat the call. A held batch holds at most 50 files. |
| code_referencesA | Find the files that use a symbol, best evidence first: files the code index links to it (a call, a base type, an import) with the lines, then files whose text names it. kind="calls" for callers only, "inherits" for subtypes only, "all" (default) for every use and mention. Name the symbol as for code_find_symbol ("Ledger.Post"); qualify it further when the name is common. |
| memory_rememberA | Store one fact in a memory space: a subject ("Halcyon"), an attribute ("database") and a value ("PostgreSQL 15"), with the date it became true and the documents you learned it from. Name a |
| memory_space_createA | Make a memory space to save facts in. Kind "personal" is yours alone: only you see its facts. Kind "team" is seen by everyone in this Connapse. Save to a personal space if it is about the user, their preferences or their own work; to a team space if it would be true and useful for others. If unsure, ask. Check memory_spaces first: no space is made for you, so make one only when none fits. Names are lowercase letters, numbers and hyphens. |
| container_createA | Create a new container for documents. Use when setting up a new knowledge domain or project. To make a place for memory facts, use |
| memory_recallA | Read facts from memory: what is true now, or on a past date with |
| container_deleteA | Delete a container. It must be emptied first, because deleting one deletes its stored files. External sources are not containers and cannot be deleted here. If your token asks before deleting, nothing is deleted yet: the call returns a deletion batch that Connapse carries out itself once your owner approves it. Read the outcome with deletion_status; don't repeat the call. |
| deletion_statusA | Check a batch of deletions, by its id: one you asked for with request_deletions, or one a held delete call returned. Pass |
| code_repo_mapA | A map of indexed code: the files the rest of the code refers to most, each with its main definitions and how many other files use each. Start here in an unfamiliar repository, or pass |
| code_impactA | What a change to a symbol could affect: the functions and types that call or inherit it, directly or through others, up to |
| container_listA | Lists every searchable knowledge scope with its description and document count. Each entry is kind=managed (storage Connapse owns, browsable with |
| upload_fileA | Upload one file, or up to 100 with 'files', to be parsed, chunked, embedded, and made searchable. For one file give 'fileName' and either 'content' (base64) or 'textContent' (raw text), not both. |
| container_statsA | Get container statistics: document counts, chunk count, storage size, and embedding model info. |
| get_documentA | Retrieve a document's full text by ID or path, or up to 50 documents' with 'files'. Returns extracted text for binary formats (PDF, DOCX, PPTX). Intended for use after |
| memory_spacesA | List the memory spaces you can use: your personal spaces (only you see them) and team spaces (everyone in this Connapse sees them). Each comes with its id, name, kind, description, whether you can add to it, and who sees it. Call this before saving to pick a |
| code_find_symbolA | Find where a function, method, class or other symbol is defined in indexed code (C#, Python, TypeScript). match="exact" (default) takes a name as far as you know it: "Post", "Ledger.Post" or "Acme.Billing.Ledger.Post". match="words" takes words that all appear in the qualified name ("ledger post"). match="meaning" takes a description ("where invoices are written to the ledger"). With follow=true, also returns what the first definition calls, constructs or inherits and the files defining those: the files to read to see how it works. Returns definitions with path, start and end line and signature, and ranked files. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 24 tools
Most tools are cleanly separated by resource+action (container_list vs memory_spaces vs list_files, code_find_symbol vs code_references vs code_impact), and descriptions explicitly cross-reference siblings to steer selection. Two soft overlaps remain: container_stats vs container_describe both return description/document statistics, and delete_file (which accepts up to 100 fileIds) vs request_deletions both delete in batch, forcing the agent to reason about which path applies.
A clear domain-prefix scheme is used for three of the five sub-areas (container_*, memory_*, code_*) with verb_noun forms inside each group. The document/deletion tools drop the prefix (upload_file, get_document, list_files, delete_file, search_knowledge) and deletion_status breaks into noun_noun, so it is readable and mostly predictable rather than uniform.
24 tools is at the heavy end, but the server spans four real sub-domains (containers, documents, memory facts, code index) plus an approvals flow, averaging roughly five tools each. Almost every tool earns its place, with the only redundancy being the container_stats/container_describe pair.
Lifecycle coverage is strong across every domain: containers (list/stats/describe/create/delete), documents (upload/get/list/append/delete), memory (spaces, create, remember, recall, correct, forget, timeline), code (map, find, references, impact), and async deletion with status polling. Remaining gaps are minor conveniences (container rename/update, file move/copy, direct memory_space_delete outside the approvals flow) that agents can work around.