Acemcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| ACEMCP_TOKEN | No | Authentication token | |
| ACEMCP_BASE_URL | No | API endpoint URL | |
| ACEMCP_BATCH_SIZE | No | Number of files to upload per batch | 10 |
| ACEMCP_MAX_LINES_PER_BLOB | No | Maximum lines per blob before splitting large files | 800 |
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 |
|---|---|
| search_contextA | Search for relevant code context based on a query within a specific project. This tool automatically performs incremental indexing before searching, ensuring results are always up-to-date. Returns formatted text snippets from the codebase that are semantically related to your query. IMPORTANT: Use forward slashes (/) as path separators in project_root_path, even on Windows. |
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 1 tool
With only one tool, there is no possibility of ambiguity or overlap with other tools. The tool's purpose is clearly defined as searching for code context within a project, making it distinct by default.
Since there is only one tool, naming consistency is inherently perfect. The tool name 'search_context' follows a clear verb_noun pattern, and there are no other tools to compare it against for inconsistency.
A single tool is generally too few for a server's purpose, as it limits functionality and suggests an incomplete or overly narrow scope. While the tool is well-defined, a typical MCP server should offer a broader set of operations to be useful for agents.
The server appears to focus on code context search, but with only one tool, it lacks essential operations like creating, updating, or deleting context, or even basic CRUD for projects. This creates significant gaps that will hinder agent workflows and limit utility.