Cursor10x MCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
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 |
|---|---|
| generateBannerB | Generates a banner containing memory system statistics and status |
| checkHealthB | Checks the health of the memory system and its database |
| initConversationC | Initializes a conversation by storing the user message, generating a banner, and retrieving context in one operation |
| endConversationA | Ends a conversation by storing the assistant message, recording a milestone, and logging an episode in one operation |
| storeUserMessageC | Stores a user message in the short-term memory |
| storeAssistantMessageB | Stores an assistant message in the short-term memory |
| trackActiveFileC | Tracks an active file being accessed by the user |
| getRecentMessagesB | Retrieves recent messages from the short-term memory |
| getActiveFilesC | Retrieves active files from the short-term memory |
| storeMilestoneC | Stores a project milestone in the long-term memory |
| storeDecisionC | Stores a project decision in the long-term memory |
| storeRequirementC | Stores a project requirement in the long-term memory |
| recordEpisodeC | Records an episode (action) in the episodic memory |
| getRecentEpisodesC | Retrieves recent episodes from the episodic memory |
| getComprehensiveContextC | Retrieves comprehensive context from all memory systems |
| getMemoryStatsB | Retrieves statistics about the memory system |
| manageVectorC | Unified tool for managing vector embeddings with operations for store, search, update, and delete |
| diagnoseVectorsB | Run diagnostics on the vector storage system to identify issues |
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 18 tools
Most tools have distinct purposes, but there is some overlap between 'storeAssistantMessage'/'storeUserMessage' and 'endConversation'/'initConversation', which bundle similar operations. The 'manageVector' tool is broad but clearly defined, while others like 'getRecentEpisodes' and 'getRecentMessages' target different memory types, reducing confusion.
Naming is mixed with camelCase (e.g., 'checkHealth') and snake_case (e.g., 'store_assistant_message'), though most tools use a verb_noun pattern. Inconsistencies like 'diagnoseVectors' vs. 'manageVector' and variations in verb usage (e.g., 'get', 'store', 'record') detract from a uniform convention.
With 18 tools, the count is slightly high but reasonable for a memory system server covering health, diagnostics, conversation management, and multiple memory types (short-term, episodic, long-term). It avoids being overwhelming by grouping related operations, though some tools could be consolidated.
The tool set comprehensively covers the memory system domain, including initialization, conversation handling, message storage, episode recording, milestone/requirement/decision tracking, vector management, health checks, diagnostics, and context retrieval. There are no obvious gaps, supporting full lifecycle operations for memory management.