Lspace MCP Server
OfficialServer Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| OPENAI_API_KEY | Yes | Your OpenAI API key for LLM operations | |
| REPO_BASE_PATH | No | Directory where GitHub repositories will be cloned, defaults to 'cloned-github-repos' if not specified | cloned-github-repos |
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
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| lspace_list_repositoriesB | đ SETUP: List all repositories currently managed by Lspace. |
| lspace_get_repository_infoB | âšī¸ SETUP: Get detailed configuration for a specific repository. |
| lspace_add_contentA | đ CREATE: Add content for automatic knowledge base generation. This is the PRIMARY tool for adding ANY content to lspace. Example: repositoryId='b3fcb584-5fd9-4098-83b8-8c5d773d86eb', inputType='text_snippet', content='My documentation text', title='New Guide' |
| lspace_search_knowledge_baseA | đ SEARCH: Query the knowledge base using natural language. Automatically syncs with remote before searching to ensure latest content. Example: repositoryId='b3fcb584-5fd9-4098-83b8-8c5d773d86eb', queryText='What are the testing procedures?' |
| lspace_browse_knowledge_baseA | đ BROWSE: Read existing knowledge base files/directories (read-only). Automatically syncs with remote before browsing to ensure latest content. Example: To list files in 'Lspace Official Docs' root, use repositoryId='b3fcb584-5fd9-4098-83b8-8c5d773d86eb', operation='list_directory', path='.' |
| lspace_list_knowledge_base_historyA | đ HISTORY: List all changes made to the knowledge base in human-friendly format. Shows both file uploads and knowledge base generations separately. Example: repositoryId='b3fcb584-5fd9-4098-83b8-8c5d773d86eb' |
| lspace_undo_knowledge_base_changesA | đ UNDO: Revert knowledge base changes using human-friendly commands. Can undo file uploads, KB generations, or both. Examples: 'undo changes for test.txt', 'undo last 3 changes', 'remove test.txt completely' |
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 7 tools
Each tool has a distinct purpose with clear boundaries: add_content for creation, browse for reading files, get_repository_info for configuration, list_history for change tracking, list_repositories for setup, search for querying, and undo for reverting changes. No overlap exists between these functions, making tool selection straightforward.
All tools follow a consistent 'lspace_verb_noun' pattern with snake_case throughout (e.g., lspace_add_content, lspace_browse_knowledge_base). This uniformity makes the tool set predictable and easy to navigate, with no deviations in naming conventions.
With 7 tools, the server is well-scoped for managing a knowledge base system. This count covers core operations like CRUD (add, browse, undo), setup (list repositories, get info), and advanced features (search, history) without being overwhelming or insufficient for the domain.
The tool set provides comprehensive coverage for knowledge base management, including creation, reading, searching, history tracking, and undo functionality. A minor gap exists in direct update or delete operations for specific content, but agents can work around this using undo or re-adding content.