pdf-knowledge-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| PDF_KNOWLEDGE_STORE_PATH | No | Path to the knowledge base index JSON file. If not set, defaults to the project's default location. | data/pdf-knowledge-index.json |
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 |
|---|---|
| ingest_documentA | Ingest a PDF development experience document into the local RAG knowledge base. The server chunks, vectorizes, indexes, and persists the content locally. |
| search_knowledgeA | Search the local PDF development knowledge base with semantic-style TF-IDF vector retrieval and return ranked chunks with source references. |
| ask_pdf_expertB | Answer a PDF development question by retrieving relevant local knowledge first and returning an answer with citations. |
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 serves a distinct purpose: ingest for adding documents, search for retrieval, and ask for QA with citations. No overlapping functionality.
All tools follow a consistent verb_noun pattern in snake_case (ask_pdf_expert, ingest_document, search_knowledge), making their roles clear.
Three tools is a minimal but reasonable set for a knowledge base server, covering the core operations of ingestion, retrieval, and question answering.
The server covers the essential CRUD-like operations for a RAG system (ingest, search, QA). Missing delete or update, but these are less critical for the domain.