enterprise-agent-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| API_KEY | No | API key used in production for REST API requests via X-API-Key. | |
| APP_ENV | No | Application environment. Set to production to enable production API key requirement for REST API. | |
| AGENT_MODE | No | Agent mode. Default is demo and requires no API key. Set to openai to use OpenAI Responses API. | demo |
| OPENAI_MODEL | No | OpenAI model used with the OpenAI planner, e.g. gpt-4.1-mini. | |
| OPENAI_API_KEY | No | OpenAI API key required when AGENT_MODE=openai. |
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 | {
"listChanged": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| search_enterprise_policyC | Search enterprise policies with hybrid retrieval. |
| search_enterprise_docsC | Search enterprise handbooks and runbooks. |
| run_enterprise_agentC | Run the governed Agent. High-risk actions return an approval id and never execute directly. |
| decide_enterprise_approvalC | Approve or reject a pending high-risk operation as a manager/admin. |
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
search_enterprise_policy and search_enterprise_docs both perform hybrid retrieval over enterprise content and differ only by content type (policies vs handbooks/runbooks), which an agent could easily confuse. The run/decide pair is clearly distinct, but the two search tools create meaningful overlap.
All four tools use consistent snake_case verb_noun structure with a shared 'enterprise' infix (search_enterprise_policy, search_enterprise_docs, run_enterprise_agent, decide_enterprise_approval), making the pattern highly predictable.
Four tools is on the thin side for a governed-agent workflow, and since the two search tools largely overlap, the effective surface is even smaller. It is not egregiously sparse but feels borderline for the stated scope.
The run/approve lifecycle is covered, but there is no tool to list or fetch pending approvals, so an agent receiving an approval id has no way to discover or inspect outstanding approval requests. Retrieval also lacks any get-by-id or fetch operation.