agent-link-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| OPENAI_API_KEY | No | OpenAI API key, required if using the Aider agent. | |
| AGENT_LINK_CONFIG | No | Override the default configuration path (~/.agent-link/config.json). | |
| ANTHROPIC_API_KEY | No | Anthropic API key, required if using the Aider agent. |
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 |
|---|---|
| spawn_agentA | Spawn an AI agent to work on a task. Returns a question if the agent needs clarification, or a result when done. |
| spawn_agentsA | Spawn multiple AI agents in parallel. Each agent runs independently and results are returned together. Great for getting multiple opinions, parallel code reviews, or distributing subtasks. |
| replyA | Reply to an agent that is waiting for clarification. Continues the conversation until the agent returns a result or asks another question. |
| kill_agentA | Terminate an active agent session and clean up its resources. |
| list_agentsA | List all known agents and their availability on this system. |
| get_statusA | Get the status of all active agent sessions. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
| collaborate | Generate a collaboration prompt for asking another agent for help |
| debug-with-agent | Ask another agent to help debug an error |
| code-review | Request a code review from another agent |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| agents | List of all configured agents and their availability |
| config | Current agent-link configuration |
TDQS
Scored across 6 tools
Each tool has a clear, distinct purpose: spawn, spawn multiple, list, get status, reply to clarification, kill. No overlap between get_status and list_agents, and spawn_agent vs spawn_agents are differentiated by number of agents.
Most tools follow verb_noun pattern (e.g., get_status, kill_agent, list_agents, spawn_agent, spawn_agents). 'reply' is a verb-only exception, but it's a common pattern for interactive tools and does not cause confusion.
6 tools is well within the optimal 3-15 range, covering the core operations for managing AI agent sessions without being bloated or sparse.
The tool surface covers the full agent lifecycle: spawning (solo and parallel), listing, status checking, interactive dialogue (reply), and termination. Minor gaps like retrieving results from completed agents are handled by spawn/reply outputs, so no critical missing functionality.