findocs-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| DATABASE_URL | Yes | PostgreSQL connection string for the vector database |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| search_docsA | Semantic search over the indexed financial-docs corpus. Returns the top-k chunks with cosine similarity scores and source metadata. |
| answer_questionA | Retrieves relevant chunks, synthesizes a grounded answer with citations, and refuses with "not found" when retrieval confidence is below the configured floor. |
| ingest_docB | Chunk → embed → upsert a document into pgvector. Provide either a URL to fetch or raw text. Re-ingesting identical content is idempotent. |
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 3 tools
Each tool has a distinct purpose: ingestion, search, and question-answering. No functional overlap.
All tool names follow a consistent verb_noun pattern in snake_case: answer_question, ingest_doc, search_docs.
Three tools is well-scoped for a document Q&A server, each providing essential functionality without excess.
Core lifecycle (ingest, search, answer) is covered, but missing delete or update operations for documents is a minor gap.