SidClaw GovernanceMCPServer
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| SIDCLAW_API_KEY | Yes | Your SidClaw API key, used to authenticate the agent with the governance platform. | |
| SIDCLAW_API_URL | No | The base URL of the SidClaw API. Defaults to the hosted cloud version. | https://api.sidclaw.com |
| SIDCLAW_AGENT_ID | Yes | The unique identifier for the agent being governed in the SidClaw dashboard. |
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 | {} |
| prompts | {} |
| resources | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| governance_proxyA | SidClaw MCP Governance Proxy — wraps any upstream MCP server with policy evaluation, human-in-the-loop approval, and tamper-evident audit trails. Configure SIDCLAW_API_KEY, SIDCLAW_AGENT_ID, and SIDCLAW_UPSTREAM_CMD to connect to your upstream server. See https://docs.sidclaw.com/docs/integrations/mcp for setup instructions. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 1 tool
With only a single tool available, there is zero risk of an agent confusing it with another tool or selecting the wrong one. The tool's purpose as a proxy wrapper is distinct by default.
The single tool uses clear snake_case formatting (governance_proxy). With only one tool in the set, it is trivially consistent with itself and follows a readable noun_noun pattern.
One tool is borderline thin for a 'Governance' server, which typically implies multiple concerns (policy management, audit review, configuration). While the proxy mechanism is functional, the surface feels minimal for the stated scope.
Major gaps exist for the governance domain: there are no tools to configure policies, retrieve audit trails, check approval queue status, or manage the governance lifecycle. The server only provides the proxy wrapper without exposing its own governance data or settings to agents.