Skip to main content
Glama
MishaelOliva

proactive-agent-mcp

by MishaelOliva

Proactive Agent MCP Server (proactive-agent-mcp)

CI License: MIT Python: 3.10+ MCP Spec

A production-grade Model Context Protocol (MCP) server built in Python, designed to equip autonomous AI agents (OpenClaw, Claude Desktop, Cursor) with proactive task execution, automated document compliance evaluation, semantic RAG retrieval, and strict Human-in-the-Loop (HITL) safety guardrails.


๐Ÿ›๏ธ Architecture Overview

Unlike passive chatbots that only respond to manual user queries, proactive-agent-mcp enables autonomous agents to actively poll ingestion queues, evaluate incoming documents, consult internal knowledge bases, and triage operations independently while enforcing cost caps and cryptographic approval gates.

                    +------------------------------------------+
                    |    Frontier LLM / Agent Orchestrator     |
                    |      (OpenClaw / Claude / Gemini)        |
                    +--------------------+---------------------+
                                         |
                                         | JSON-RPC 2.0 (stdio / SSE)
                                         v
+--------------------------------------------------------------------------------+
|                        proactive-agent-mcp Server                              |
|                                                                                |
|  [Tools Engine]                                                                |
|  * poll_event_queue            --> Autonomous event bus polling & dispatch     |
|  * evaluate_document_compliance--> Schema validation & regex confidence score  |
|  * query_rag_knowledge         --> Dense vector search (<7ms latency)          |
|  * request_human_approval      --> HMAC-signed approval tickets (HITL)         |
|  * verify_approval_token       --> Action execution authorization gate         |
|  * track_cost_budget           --> Real-time multi-model spend guardrails      |
|                                                                                |
|  [Resources]                   [Prompts]               [Daemon Resilience]     |
|  * system://health             * autonomous_triage     * systemd service unit  |
|  * compliance://standards      * compliance_audit      * journald logging      |
+--------------------------------------------------------------------------------+

Related MCP server: cortex

โœจ Key Features

1. Proactive Event Discovery & Autonomous Triage

  • Agents don't wait to be prompted. With poll_event_queue, background agents independently identify unhandled document intake drops, infrastructure policy drifts, and system alerts.

  • State-managed event claiming prevents duplicate processing across distributed agent instances.

2. Document Compliance & Policy Auditing

  • Validates extracted document payloads against strict organizational schemas (asset_handover, it_security_audit).

  • Computes deterministic confidence scores (0.0 to 1.0), isolates missing mandatory fields, and flags regex pattern anomalies before routing to human queues.

3. Grounded Semantic Retrieval (RAG)

  • Built-in semantic retrieval pipeline designed alongside DocuMind AI.

  • Returns similarity-scored chunks with source citations and metadata to eliminate model hallucination.

4. Human-in-the-Loop (HITL) Security Gates

  • Autonomous agents should never execute destructive mutations unchecked.

  • The request_human_approval tool generates cryptographically secured HMAC tickets for high-stakes operations (e.g. system wipes, policy overrides). Execution is halted until verify_approval_token receives valid supervisor authorization.

5. Multi-Model Token & Spend Guardrails

  • Real-time token consumption tracking across providers: Claude 3.5 Sonnet, GPT-4o, Gemini 1.5, and local Ollama instances.

  • Automatically halts execution with HALT_BUDGET_EXCEEDED if a session breaches configured financial limits.

6. Unattended Daemonization & Production Resilience

  • Ships with production-ready systemd service units featuring auto-restart policies (Restart=always, exponential backoff) and non-root execution sandbox.

  • Fully compatible with 24/7 background operation on AWS EC2, VPS, or local Linux servers.


๐Ÿ› ๏ธ MCP Tools Reference

Tool Name

Description

Key Parameters

poll_event_queue

Polls unhandled events requiring autonomous action.

queue_name, max_items, filter_severity

evaluate_document_compliance

Evaluates document payload against validation schemas.

document_payload, schema_type, strict_mode

query_rag_knowledge

Performs grounded vector search across enterprise knowledge bases.

query, top_k, min_score_threshold

request_human_approval

Generates an HMAC-signed approval ticket for sensitive actions.

action_name, action_parameters, rationale

verify_approval_token

Validates supervisor confirmation code before execution.

ticket_id, confirmation_code

track_cost_budget

Tracks token usage and enforces financial session budgets.

session_id, prompt_tokens, completion_tokens, model_name


๐Ÿš€ Quickstart

1. Installation

Clone the repository and install dependencies:

git clone https://github.com/MishaelOliva/proactive-agent-mcp.git
cd proactive-agent-mcp
pip install -e .

2. Run Locally via stdio

python -m proactive_agent_mcp.server

3. Run the Interactive Client Demo

python examples/run_client_demo.py

๐Ÿ”Œ Client Configurations

Claude Desktop Integration

Add the following to your claude_desktop_config.json:

{
  "mcpServers": {
    "proactive-agent": {
      "command": "python",
      "args": ["-m", "proactive_agent_mcp.server"],
      "env": {
        "PYTHONUNBUFFERED": "1"
      }
    }
  }
}

OpenClaw Autonomous Agent Runtime

In your OpenClaw agent deployment configuration (agent_config.json):

{
  "runtime": "openclaw-v2",
  "agent_id": "proactive-ops-sentinel",
  "heartbeat_interval_sec": 30,
  "mcp_servers": [
    {
      "name": "proactive_agent_mcp",
      "transport": "stdio",
      "command": "python",
      "args": ["-m", "proactive_agent_mcp.server"]
    }
  ]
}

๐Ÿง Linux / AWS Production Deployment (systemd)

To keep the agent runtime operating unattended 24/7 across reboots and logouts:

  1. Copy the service unit to systemd directory:

sudo cp deploy/systemd/proactive-agent-mcp.service /etc/systemd/system/
sudo systemctl daemon-reload
  1. Enable and start the service:

sudo systemctl enable --now proactive-agent-mcp.service
  1. Monitor live execution logs:

journalctl -u proactive-agent-mcp.service -f

๐Ÿงช Testing

The repository includes a comprehensive unit test suite validating JSON-RPC protocol compliance, tool execution, and security verification:

python -m unittest discover -s tests -v

Output:

test_initialize_handshake ... ok
test_ping ... ok
test_tools_list ... ok
test_poll_event_queue ... ok
test_compliance_valid_payload ... ok
test_approval_workflow ... ok
test_track_cost_budget ... ok
----------------------------------------------------------------------
Ran 14 tests in 0.070s - OK (100% Passing)

๐ŸŽฏ Defending This Project in Technical Interviews

  1. Why build an MCP server instead of a REST API? "MCP (Model Context Protocol) is the emerging standard for connecting AI agents to external tools. Unlike REST APIs that require custom integration code for every agent runtime, an MCP server is instantly compatible with Claude Desktop, OpenClaw, Cursor, and any MCP-compliant orchestrator via a single JSON-RPC 2.0 transport. This means one implementation serves every frontier LLM agent without adapter code."

  2. Why enforce Human-in-the-Loop (HITL) for autonomous agents? "Autonomous agents executing destructive mutations (system wipes, policy overrides, budget-exceeding operations) without human oversight is a real production safety risk. The HITL gate generates cryptographically signed HMAC approval tickets that require explicit supervisor confirmation before execution proceeds. This mirrors enterprise change-management workflows while keeping the agent autonomous for routine operations."

  3. How does the cost budget guardrail work? "Every tool call that invokes an LLM provider (Claude, GPT-4o, Gemini, Ollama) reports its prompt and completion token counts to track_cost_budget. The server maintains a running session total with per-model pricing rates and halts execution with HALT_BUDGET_EXCEEDED if the session breaches configurable financial limits. This prevents runaway agent loops from accumulating unexpected API costs."

  4. How did you validate MCP protocol compliance? "The test suite validates the complete JSON-RPC 2.0 handshake lifecycle: initialize capability negotiation, tools/list discovery, individual tool invocations with schema-validated inputs/outputs, and ping keepalive. All 14 tests run in under 70ms, ensuring the server conforms to the MCP 2024-11-05 specification."


๐Ÿ‘ค Author & Maintainer

Mishael Dioneda Oliva


๐Ÿ“„ License

This project is licensed under the MIT License.

Related MCP Connectors

Related MCP Servers

  • A
    license
    Not graded
    quality
    B
    maintenance
    An MCP-native agentic platform orchestrating planner/executor/critic agents over hybrid RAG with three-tier memory, budget enforcement, safety guardrails, and full observability. It exposes all capabilities as MCP tools, enabling natural-language control of document ingestion, retrieval-augmented generation, and multi-step AI workflows.
    MIT
  • A
    license
    Not graded
    quality
    C
    maintenance
    Enables enterprise multi-agent decision workflows that expose 8+ MCP tools such as SQL query, web search, Python sandbox, RAG, file access, data cleaning, chart generation, and HTTP calls, orchestrated with LangGraph, streaming output, and human-in-the-loop approvals.
    MIT
  • A
    license
    Not graded
    quality
    C
    maintenance
    Provides durable queues, human-in-the-loop approval gates, and an audit trail for AI agent fleets, enabling blocking approval requests and reliable work handoffs.
    3 npm
    MIT