Skip to main content
Glama

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault

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:

  1. If the user's question (or the prior conversation) names a specific container, call search_knowledge directly on that container. Do NOT call container_list first — the container is already known.

  2. Only call container_list when the relevant container is genuinely unknown and cannot be inferred from context. After it returns, call search_knowledge on the chosen container.

  3. Use list_files only for inventory questions ("what files are in X?", "list the docs under /folder"). Never use list_files as a substitute for search_knowledge when the user is asking about file CONTENT.

  4. Use get_document only when search_knowledge has returned a specific DocumentId you 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

CapabilityDetails
tools
{}
logging
{}

Tools

Functions exposed to the LLM to take actions

NameDescription
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 search_knowledge). Intended for inventory requests such as 'what files exist in X' or when the user named a specific filename. Large listings return a soft error directing you to search_knowledge; override with confirmLarge: true or paginate with limit. Each file shows when it was added and, if since changed, when it was updated. For the newest N entries of a folder, pass sort: "newest" and limit: N, then read them all with get_documents.

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 validFrom and the new value starts there (validFrom required). kind="wrong": the old fact was never right, so it is marked superseded and the new value takes its dates; a date you pass replaces the old one, except one where another version of the fact starts or ends. Subject and attribute default to the old fact's. A fact with versions you cannot see (another user's private ones) cannot be corrected; remember a new fact instead.

memory_timelineA

A subject's facts in date order, ended and corrected ones included: how its values changed over time. Name a space to read one space, or leave it out to read every space you can see; each fact says which space it is in. With from/to, only the facts that started or ended in that window ("what changed between A and B"). Reading one named space without from, to or attribute returns the newest facts first a page at a time, each page in date order, with nextCursor when older facts remain: pass it back as cursor.

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 space that exists: memory_spaces lists yours, and memory_space_create makes one if none fits. No space is made for you. 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. Cite the document IDs that search_knowledge or get_document gave you: a fact citing sources is shown only to people who can read all of them. The answer says who can see what you saved. When a value you stored before has changed, call memory_correct instead. If the answer lists facts already current with the same subject and attribute, and you meant to replace one, correct it instead of leaving both.

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_space_create instead.

memory_recallA

Read facts from memory: what is true now, or on a past date with asOf. Name a space to read one space, or leave it out to read every space you can see. Filter by subject or attribute, or pass a question as query. Each fact comes with its space, whether it is personal (only you see it) or team, its dates, author and sources. Use includeHistory to also get ended and corrected facts (for "which ticket changed X" or "when did X change"). Reading one named space without asOf or attribute returns nextCursor when there are more facts: pass it back as cursor for the next page.

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 waitSeconds (up to 50) to wait while it is pending or running. state is pending, expired, denied, running or done; each item's state is deleted, skipped (gone or changed since you asked), failed, not_approved or denied, and its outcome says why. message says what to do next.

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 path to map one folder.

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 depth hops, with the files that hold them and which of those are tests. For a type, what uses its members counts too. Only links the code index resolved are followed; a call it could not resolve is missed, so check code_references for the full list of mentions.

container_listA

Lists every searchable knowledge scope with its description and document count. Each entry is kind=managed (storage Connapse owns, browsable with list_files) or kind=source (an external system Connapse mirrors read-only — searchable, but it has no file listing). Memory spaces are not listed here: memory_spaces lists them. Use to discover what exists when the target is unknown; if the user already named one, call search_knowledge on it directly instead.

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 search_knowledge returns a DocumentId worth reading in entirety, or when the user has named an exact file. With 'files' each document comes under its own header in the order asked; a file that can't be read gets an error line and doesn't stop the others, and past 2,000,000 characters in all, the rest get one too. Pair 'files' with list_files sort "newest" and limit to read the newest entries of a folder in two calls.

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 space for memory_remember; if none fits, make one with memory_space_create. At most 100 are returned; pass name to find others.

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

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

TDQS

A4.2/5.0

Scored across 24 tools

Disambiguation4/5

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.

Naming Consistency4/5

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.

Tool Count4/5

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.

Completeness5/5

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.

Maintenance

ActivityActive
ResponsivenessUsually handled