locus-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| LOCUS_URL | No | Base URL of the Locus API | http://localhost:8000 |
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 |
|---|---|
| list_spacesA | List all dataspaces in Locus |
| create_spaceA | Create a new dataspace in Locus |
| delete_spaceA | Delete a dataspace and all its documents from Locus |
| list_documentsB | List all documents in a Locus dataspace |
| ingest_documentA | Ingest a document into a Locus dataspace. Provide either file_path (preferred, reads file locally without loading content into context) or text. |
| get_documentA | Retrieve the full text of a document by its ID from a Locus dataspace |
| delete_documentA | Delete a document by its ID from a Locus dataspace |
| searchA | Semantic search over documents in a Locus dataspace using natural language |
| health_checkA | Check if the Locus service is healthy and reachable |
| get_settingsA | Get the current Locus settings (Ollama URL and embedding model) |
| update_settingsA | Update Locus settings (Ollama URL and/or embedding model). Only works if settings are not locked via environment variables. |
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 11 tools
Each tool targets a distinct resource and action: spaces, documents, search, settings, and health. Even closely related tools like list_documents and search are clearly differentiated by listing all versus semantic retrieval.
Tool names consistently follow a clear verb_noun pattern such as list_spaces, create_space, delete_document, and update_settings. The use of ingest_document instead of create_document is still intuitive and does not break the overall pattern.
With 11 tools, the server is well-scoped for managing dataspaces, documents, search, settings, and health. Each tool serves a clear purpose without redundancy or bloat.
The tool surface covers core lifecycle operations for spaces and documents, plus search, settings, and health checks. Minor gaps exist, such as no update/rename for spaces and no replace/update operation for documents, but these are unlikely to block the primary workflows.