agentgate

AgentGate MCP server provides a backend service that enables Claude Desktop and other agents to request human-in-the-loop approvals via a centralized policy-driven approval workflow. The MCP server integrates with the AgentGate ecosystem to surface requests, route them to the appropriate human channels (dashboard, Slack, Discord, or email), and record decisions for auditing. With the MCP server running, you can connect client agents or SDKs to initiate an approval flow, and the server will manage policy evaluation, human routing, and decision propagation back to the requester.

To use it, install and run the MCP server, then configure your client applications (agents) to send requests through the MCP API. The server supports live approval decisions, automated policies (auto-approve or auto-deny), and a human-in-the-loop pathway for complex or sensitive actions. Once connected, you can observe pending requests, approve/deny actions via the dashboard or notification channels, and rely on the built-in audit trail for traceability.

Prerequisites:

• Node.js (LTS) installed on your machine or server
• Access to the npm registry (public or private)

1. Install the MCP server package (AgentGate MCP) via npx or npm:

   • Quick start (temporary run): npm install -g @agentgate/mcp

   • Or run directly with npx (no global install): npx -y @agentgate/mcp

2. Initialize environment and configuration:

   • Set up any required environment variables (example placeholders): export AGENTGATE_API_KEY="your-api-key" export AGENTGATE_SERVER_URL="http://localhost:3000"

   • If the MCP server supports a config file, create a config file at the expected path (e.g., .agentgate/mcp.config.json) and populate as needed.

3. Start the MCP server:

   • If using npm/global install: agentgate-mcp start

   • If using npx in a local run (no persistent install): npx -y @agentgate/mcp start

4. Verify it's running by hitting the MCP endpoints or the provided health check route (e.g., http://localhost:3000/health).

5. Optional: run migrations or bootstrap steps if required by the stack (e.g., database setup, initial admin, or policy seeding) as documented in the project README.

Tips and caveats:

• Ensure your environment variables (API keys, server URLs) are correctly set before starting the MCP server.
• If you use Docker deployment, the MCP server can be containerized and wired with your database and message queues; follow Docker deployment guidelines in the repository.
• For production, enable proper logging, SSL termination, and access controls to protect approval flows.
• The MCP server integrates with the AgentGate SDKs and bots; ensure the SDK client is configured to point at the MCP server URL.
• If you encounter issues with dependencies, use a clean install (clear node_modules) and align Node.js version with the project's supported range.
• Review any roadmap notes around MCP routing (dashboard, Slack, Discord, email) to understand how approvals will appear to humans and how to customize policy routing.