PocketMCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| API_BIND | No | API server bind address | 127.0.0.1 |
| API_PORT | No | Web API server port | 5174 |
| MODEL_ID | No | Hugging Face model for embeddings | Xenova/all-MiniLM-L6-v2 |
| NODE_ENV | No | Environment mode | development |
| WATCH_DIR | No | Directory to watch for file changes | |
| CHUNK_SIZE | No | Target chunk size in characters | 1000 |
| SQLITE_PATH | No | Path to SQLite database file | ./data/index.db |
| DEBUG_DOTENV | No | Enable dotenv debug output | false |
| CHUNK_OVERLAP | No | Overlap between chunks in characters | 120 |
| VERBOSE_LOGGING | No | Enable detailed logs | false |
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 | {} |
| resources | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| searchB | Search for similar content using semantic search |
| upsert_documentsC | Insert or update documents with text content |
| delete_documentsC | Delete documents by ID or external ID |
| list_documentsC | List all documents with pagination |
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 4 tools
Each tool has a clearly distinct purpose with no overlap: delete_documents removes documents, list_documents retrieves them, search finds similar content, and upsert_documents inserts or updates. An agent can easily tell them apart based on their specific actions.
All tool names follow a consistent verb_noun pattern (e.g., delete_documents, list_documents, upsert_documents), with 'search' as a slight deviation that still fits semantically. The naming is predictable and readable throughout.
With 4 tools, the server is well-scoped for document management, covering core operations like listing, searching, upserting, and deleting. Each tool earns its place without being too sparse or bloated.
The tool set provides strong coverage for basic document CRUD and search operations, but lacks explicit tools for actions like retrieving a single document by ID or updating metadata, which could be minor gaps agents might need to work around.