@agentrysh/mcp

MCP handoff to the Agentry skill for agent-native analytics and logging.

Source

npm

Version: 0.0.27

Version published: 3 months ago

Weekly downloads: 51

Maintainers: 1

Weekly downloads

Created: 4 months ago

Source

Agentry MCP Server

Agentry is agent-native analytics and logging for coding agents. It covers 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.

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: