MCP & AI Agent Integration

Hamsa
automation.

16 AI agent actions for Hamsa — callable from any MCP-compatible runtime, Claude, Cursor, or Cerebral OS workflow. Use Hamsa to manage subscribers, trigger campaigns, and personalize outreach at scale. Full governance, audit trail, and dry-run safety on every execution.

No credit card required
Live in production environments
<200ms median execution
Dry-run before production
Execution trace
live
16
actions
100%
governed
<200ms
latency
16
AI agent actions
8
Read operations
8
Write operations
2
High-risk actions (approval gated)
Marketing Hamsa is a Marketing integration — use it to automate email campaigns, audience management, and automation from any AI agent or MCP-compatible runtime.
Actions

What you can do
with Hamsa.

Every action below is available as an MCP tool and a verb in Cerebral OS — callable from any AI agent, Claude, Cursor, Windsurf, or your own runtime via the BYOA API. All executions are governed, audited, and dry-run safe.

Get Campaign
hamsa:get_campaign
Fetch a single campaign with its configuration and performance stats.
Read Low risk
Get Customer
hamsa:get_customer
Fetch a single customer profile with attributes and journey status.
Read Low risk
Get Journey
hamsa:get_journey
Fetch a single customer journey with its steps and performance stats.
Read Low risk
Get Segment
hamsa:get_segment
Fetch a single segment with its criteria and customer count.
Read Low risk
List Campaigns
hamsa:list_campaigns
List campaigns with optional filtering and performance stats.
Read Low risk
List Customers
hamsa:list_customers
List customers with optional filtering and pagination.
Read Low risk
List Journeys
hamsa:list_journeys
List customer journeys with optional filtering and performance stats.
Read Low risk
List Segments
hamsa:list_segments
List all segments with optional filtering.
Read Low risk
Add Customer To Segment
hamsa:add_customer_to_segment
Add a customer to a specific segment (only works with static segments).
Write Medium risk
Create Customer
hamsa:create_customer
Create a new customer profile in Hamsa.
Write Medium risk
Delete Customer
hamsa:delete_customer
Permanently delete a customer and all their associated data.
Write High risk
Pause Campaign
hamsa:pause_campaign
Pause an active or scheduled campaign.
Write Medium risk
Remove Customer From Segment
hamsa:remove_customer_from_segment
Remove a customer from a specific segment (only works with static segments).
Write High risk
Send Campaign
hamsa:send_campaign
Send or schedule a campaign to its target segment.
Write Medium risk
Track Event
hamsa:track_event
Track a custom event for a customer to trigger journeys and campaigns.
Write Medium risk
Update Customer
hamsa:update_customer
Update an existing customer profile in Hamsa.
Write Medium risk
MCP & Runtime API

Call Hamsa
from any AI agent.

Any AI agent — Claude, Cursor, LangChain, AutoGen, or your own — can call Hamsa actions through the Cerebral OS Runtime API. Governance, credentials, and audit trail fire automatically.

hamsa:get_campaign READ
# Call via Runtime API
curl
-X POST \
  "https://api.cerebralos.com/v1/runtime/actions/run"
  -H "X-API-Key: YOUR_KEY" \
  -d '{
    "verb": "hamsa:get_campaign",
    "args": {},
    "execution_id": "agent-001"
  }'
hamsa:add_customer_to_segment WRITE
# Dry-run first — no production risk
curl
-X POST \
  "https://api.cerebralos.com/v1/runtime/actions/run"
  -H "X-API-Key: YOUR_KEY" \
  -d '{
    "verb": "hamsa:add_customer_to_segment",
    "args": {},
    "execution_id": "agent-001",
    "metadata": {"dryRun": true}
  }'
Get your Runtime API key at app.cerebralos.com/signup — 1,000 free executions, no credit card required.
AI agent examples

What your AI agent
can do with Hamsa.

Real patterns your AI agent can execute via MCP or the Runtime API. Every action governed, dry-run safe, and fully audited.

Trigger
AI agent needs Hamsa data
Call hamsa:get_campaign via MCP or Runtime API
AI processes result and takes next action
Full execution logged to audit trail automatically
Trigger
Workflow needs to write to Hamsa
Dry-run validates hamsa:add_customer_to_segment before execution
Approval gate fires if risk level is high
Action executes with full governance — logged, audited, reversible
Trigger
Campaign or subscriber event
Segment audience
Trigger follow-up
Log metrics to dashboard
How it works

Every Hamsa action
governed end-to-end.

Cerebral OS isn't a connector. It's the execution layer that sits in front of Hamsa — adding governance, dry-run safety, and a full audit trail to every operation.

Governance first
Every verb carries a risk classification. High-risk writes require explicit approval gates before they execute in production.
Dry-run safe
Simulate any Hamsa action before it touches production. See exactly what would happen before a single real call is made.
Immutable audit trail
Every Hamsa action is logged — what ran, what changed, who approved it, when it happened. Full history on every verb, forever.
Connect with

Hamsa works best
alongside these.

Build multi-step workflows that connect Hamsa to the rest of your stack. All governed. All audited.

Hamsa integration

Start free.
No credit card required.

Start free with 1,000 runs — no credit card required. Connect Hamsa in minutes, dry-run every action before it touches production, full audit trail on everything.

Start free — 1,000 runs Browse all integrations →