Agentic 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
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| pingA | Responds with a pong acknowledgement and timestamp to verify connectivity. |
| fs-readerA | Reads files relative to the project root with a 5MB size cap. |
| plan-managerA | Lists, reads, and writes .plan.json files under docs/archive. |
| code-searchA | Performs regex or text searches over project files, excluding node_modules and .git. |
| git-observerA | Provides read-only git status, log, and diff information. |
| atomic-writerB | Writes file content with automatic backup creation and path safety validation. |
| terminal-runnerA | Executes allow-listed shell commands (npm, node, tsc) with enforced timeout and captured output. |
| project-topologyA | Produces a directory tree snapshot rooted at the project base, excluding ignored directories. |
| doc-fetcherA | Fetches allow-listed documentation URLs and returns Markdown-formatted content. |
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 9 tools
Each tool targets a distinct concern: connectivity, file reading, planning, search, git inspection, writing, command execution, project structure, and documentation fetching. There is no meaningful overlap that would cause an agent to select the wrong tool.
Most names follow a consistent lowercase hyphenated compound pattern like fs-reader, git-observer, and terminal-runner. The lone ping is a minor deviation, but overall the style is predictable and readable.
Nine tools is well-scoped for an agentic coding assistance server. Each tool earns its place and the set is neither bloated nor too thin.
The tool set covers the core agent loop: reading, writing, searching, executing, inspecting git state, planning, and fetching docs. Minor gaps like file deletion/rename and git write operations are present, but they are not critical for many workflows.