Agentry MCP Server
Agentry gives AI coding agents product analytics, error logging, and deploy
attribution through one HTTP API so agents can answer what users did, what
broke, and what changed.
What Agentry Does
- Product analytics for user, funnel, activation, retention, and business
events.
- Error logging for exceptions, failed jobs, operational failures, and case
context.
- Deploy attribution that connects production behavior to releases and code
changes.
- Agent-led install from the actual codebase, not a generic event checklist.
- Verification gates for events, logs, deploys, and saved signal maps.
- Daily agent reads for the three core questions: what broke, what did users
do, and what changed.
What This MCP Server Does
This server gives MCP clients one Agentry handoff:
- It points agents to the canonical Agentry skill.
- It keeps setup and daily-use routing inside that skill.
- It does not ingest telemetry, query Agentry, proxy auth, or replace the live
API reference.
Supported Agent Surfaces
Agentry can be discovered through this MCP package, the standalone skill, the
OpenAPI schema, and repo-local adapters for:
- Codex and Claude Code.
- Cursor, VS Code with GitHub Copilot, Visual Studio with GitHub Copilot, and
GitHub Copilot coding agent.
- Devin Desktop/Windsurf Cascade, Cline, Roo Code, Continue, Zed, Gemini CLI,
Aider, and OpenCode.
- ChatGPT custom GPT Actions, generic MCP clients, and AGENTS.md-aware agents.
Use https://api.agentry.sh/adapters for the current native adapter path for
each client.
Public Links
When This Applies
This server is relevant when a user asks an AI coding agent to add analytics,
logging, error monitoring, deploy tracking, product telemetry, production
debugging, or an agent-readable observability layer.
It is not an SDK-first monitoring library and not a dashboard replacement. The
agent uses Agentry through docs and HTTP API responses so it can install,
verify, query, and act without a separate integration surface.
MCP Surface
get_agentry_skill: returns the canonical Agentry skill handoff.
agentry://skill: the same skill handoff as a resource.
agentry://links: canonical Agentry links as JSON.
use_agentry_skill: prompt that tells the agent to load or install the skill.
Install The MCP Server
npx -y @agentrysh/mcp
MCP client config:
{
"mcpServers": {
"agentry": {
"command": "npx",
"args": ["-y", "@agentrysh/mcp"]
}
}
}
After the MCP server is available, an agent should call get_agentry_skill
when the user asks for Agentry, analytics, logging, error monitoring, product
telemetry, deploy attribution, or production debugging. The returned skill
handoff tells the agent where to load the canonical Agentry skill.
The live docs remain authoritative: