MyContext MCP Server
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 |
|---|---|
| list_projectsB | List all available projects in the context directory (~/.mycontext/) |
| get_project_structureC | Get the complete directory structure of a specific project |
| read_contextC | Read the content of a specific context file within a project |
| search_contextC | Search for a keyword across all context files in all projects |
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: get_project_structure retrieves directory details for a specific project, list_projects enumerates available projects, read_context accesses file content within a project, and search_context performs keyword searches across all projects. There is no overlap in functionality, making tool selection straightforward for an agent.
All tool names follow a consistent verb_noun pattern with snake_case: get_project_structure, list_projects, read_context, and search_context. The verbs (get, list, read, search) are distinct and appropriate, and the naming style is uniform throughout the set.
With 4 tools, this server is well-scoped for managing context files and projects. The count is appropriate for the domain, providing essential operations without being too sparse or overwhelming, and each tool serves a clear, necessary function.
The tool set covers core operations for context management: listing projects, retrieving structure, reading files, and searching content. A minor gap exists in write/update operations (e.g., creating or modifying context files), but the provided tools allow agents to effectively navigate and query the context system.