agency-mcp-server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| AGENCY_REPO_URL | No | Git repo to clone templates from. Point at your fork | https://github.com/msitarzewski/agency-agents.git |
| AGENCY_AGENTS_PATH | No | Path to agent templates. Set this to use your own templates instead of auto-cloning | ~/.cache/agency-mcp-server/agency-agents |
| AGENCY_AUTO_UPDATE | No | Set to false to disable automatic pulls | true |
| AGENCY_UPDATE_INTERVAL | No | Hours between update checks | 24 |
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": true
} |
| prompts | {
"listChanged": true
} |
| resources | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| agency_searchA | Find and launch a specialized agent for any task. Search agent templates by keyword. Returns matching agents with file paths and a spawn template. Call this before spawning any agency subagent.
|
| agency_browseA | Browse all agent divisions and their agents. Explore the agent registry when you want to see what's available. Use agency_search instead if you already know what kind of agent you need. Call with no arguments to see all divisions. Pass a division name to list its agents. |
| agency_statusA | Check the current status of the agent index — last update time, whether an update is available, and agent count. |
| agency_updateA | Pull latest agent templates from git (if applicable) and rebuild the search index. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
| use-agent | Find the best agent for a task and get spawn instructions |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| agents | Full index of all agent templates with names, descriptions, divisions, and file paths |
| divisions | List of all agent divisions with counts and examples |
TDQS
Scored across 4 tools
Each tool has a clearly distinct purpose: browse lists divisions/agents, search finds agents by keyword with spawn templates, status checks index health, update refreshes the index. No overlap.
All tools follow a consistent 'agency_' + verb in snake_case pattern (browse, search, status, update), making it predictable and easy to understand.
With 4 tools, the server is slightly on the minimal side but still well-scoped for agent registry operations. Each tool serves a distinct purpose without redundancy.
The tool surface covers the core workflows: browsing, searching, status checking, and updating. Minor gap is the lack of a direct spawn tool, but search provides a template for spawning.