Ops Agent settings and MCP integrations

​

Overview

• Ops Agent LLM Controls — persona, model selection, sampling hyper-parameters, and cognitive governance toggles.
• Integrations & MCP — built-in OS integrations, custom webhooks, and Model Context Protocol (MCP) servers, each with a live connection test.

• Make the Ops Agent more deterministic or more creative for a given workload.
• Set a fallback model so runs survive a primary model outage.
• Register an external webhook or mount an MCP server as an agent tool source.
• Verify that an integration handshake works before relying on it in a workflow.

​

Ops Agent LLM controls

​

Identity and tone

​

Model and sampling

​

Cognitive governance

• Anti-Passivity Mandate (Zero Refusal Gate) — the agent must attempt the task rather than deflect or defer.
• Multi-Step Chain-of-Thought DAG Planning — the agent decomposes work into a multi-step plan before executing.
• Quality Flywheel Auto-Evaluation & Scoring — the agent scores its own output and feeds the score back into future runs.

​

Secrets vault

• Normalizes the provider name to its canonical environment key. For example, hubspot, hubspot_pat, and hubspot_access_token all map to HUBSPOT_PAT; unrecognized providers map to the uppercased provider name.
• Stores only a masked preview of the value, in the form sk_1••••••••e0a1. Values of 8 characters or fewer show as a fully masked placeholder.
• Increments the secret’s version each time you update an existing provider.

​

Automatic provider sync

​

Integrations & MCP hub

​

Built-in OS integrations

​

Add a custom webhook

{
  "name": "Mercury Bank Webhook",
  "type": "webhook",
  "config": {
    "endpoint": "https://api.mercury.com/v1/webhooks",
    "apiKey": "sec_test_123"
  },
  "status": "active"
}

​

Mount an MCP server

• Server Identifier Name — a label like Postgres-MCP.
• Transport Protocol — sse (Server-Sent Events URL) or stdio (local command).
• Endpoint or command — an SSE URL such as https://mcp.agent-lab.tech/sse, or a CLI command such as npx -y @modelcontextprotocol/server-postgres for stdio.
• Capabilities — comma-separated list, for example tools,resources.
• Authorization Token / API Key — optional.

{
  "name": "PostgreSQL MCP",
  "type": "mcp",
  "config": {
    "transport": "sse",
    "endpoint": "https://mcp.agent-lab.tech/sse",
    "capabilities": ["tools", "resources"]
  },
  "status": "active"
}

​

Integration status

​

Test a connection

1. Provider-verified checks. Integrations whose name matches a known provider are validated against that provider’s live API using the credentials configured in the environment or secrets vault:
   • Instantly verifies the outbound connection over REST API v2 (Instantly Outbound) using INSTANTLY_API_KEY.
   • ElevenLabs (names containing elevenlabs or pamela) calls the ElevenLabs user endpoint with ELEVENLABS_API_KEY.
   • HubSpot queries the CRM contacts endpoint with HUBSPOT_PAT (also accepting HUBSPOT_ACCESS_TOKEN, HUBSPOT_DEVELOPER_API_KEY, or HUBSPOT_API_KEY).
   If the required key is missing, the test fails with a message naming the key, for example ELEVENLABS_API_KEY is not configured in environment or vault.
2. Live HTTP ping. If the integration config includes an http:// or https:// endpoint URL, the test sends a HEAD request with a 5-second timeout and reports the actual HTTP status and measured roundtrip latency.
3. Local fallback. Integrations with no reachable URL are verified as a local profile and report Local Plugin / Runtime Hook (or Model Context Protocol v1.0 (stdio) for MCP).

{
  "success": true,
  "latencyMs": 34,
  "protocol": "Model Context Protocol v1.0 (SSE/stdio)",
  "message": "HTTP 200 OK from https://mcp.agent-lab.tech/sse (34ms roundtrip).",
  "timestamp": "2026-09-07T20:06:13.000Z"
}