Agentskillupdategate MCP

What agentskillupdategate-mcp MCP server does

The agentskillupdategate-mcp MCP server provides a hosted control point for Claude Code skill update workflows. Its tool set covers five stages of that workflow: evaluating whether an update can proceed, comparing skill manifests, recording an update receipt, assigning a responsible owner, and exporting the resulting update log.

The service is intended for teams that need more than an informal change process. Structured receipts and reviewer-ready evidence can help document what happened during a skill update, while ownership assignment identifies who is responsible for the skill. The available material does not define the exact fields, validation rules, or response formats for each tool, so those details should be confirmed through the service’s published documentation or server card.

How it works

The agentskillupdategate-mcp MCP server is delivered as a paid, hosted remote service rather than as source code that runs from this repository. Its public MCP endpoint is:

https://agentskillupdategate.clauxel.com/mcp

Clients communicate with the endpoint using MCP over Streamable HTTP. Production calls must include a bearer token in the request header:

Authorization: Bearer <token>

The service also publishes a server card at https://agentskillupdategate.clauxel.com/server-card.json. The registry name listed for the service is com.clauxel.agentskillupdategate/agentskillupdategate-mcp.

A typical workflow can use check_skill_update_gate before a change, compare_skill_manifest to inspect differences, and issue_update_receipt after an approved update. assign_skill_owner can associate responsibility with a skill, while export_skill_update_log can produce a record for later review. The source material names these operations but does not specify whether the tools must be called in that order.

Setup and configuration

The agentskillupdategate-mcp MCP server requires an account or plan from the product website and an API token for production access. Setup consists of these steps:

1. Open the product website and select a plan.
2. Create or request an API token.
3. Add the remote endpoint to an MCP client that supports Streamable HTTP servers.
4. Configure the client to send the token as a bearer authorization header.

The repository does not document local installation, a package to run, or environment variables. It is a documentation and directory-submission reference for the hosted service, not the private production implementation.

Tools and capabilities

The agentskillupdategate-mcp MCP server exposes these tools:

• check_skill_update_gate — checks the update gate for a skill change.
• compare_skill_manifest — compares skill manifests.
• issue_update_receipt — issues a receipt for an update.
• assign_skill_owner — assigns ownership of a skill.
• export_skill_update_log — exports the skill update log.

Together, these names indicate support for gate decisions, change comparison, evidence creation, accountability, and log export. Exact input schemas, output schemas, error behavior, and retention rules are not included in the provided material.

Limitations and notes

The service is paid and hosted remotely, so it depends on network access, an active plan, and a valid bearer token. Unauthenticated browser requests to /mcp return a JSON error rather than internal service details; that behavior does not replace authenticated MCP configuration.

The repository does not contain the production source code. It also does not describe offline operation, local deployment, client-specific setup, token expiration, data retention, or the precise contents of receipts and exported logs. Teams evaluating it should verify those operational details before adopting it for regulated or long-term audit workflows.