MCP & AI Agent Integration

Heylibby
automation.

10 AI agent actions for Heylibby — callable from any MCP-compatible runtime, Claude, Cursor, or Cerebral OS workflow. Use Heylibby to update contacts, move deals through pipelines, and trigger follow-up sequences automatically. 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
10
actions
100%
governed
<200ms
latency
10
AI agent actions
4
Read operations
6
Write operations
1
High-risk actions (approval gated)
CRM Heylibby is a CRM integration — use it to automate contact management, deals, and pipeline operations from any AI agent or MCP-compatible runtime.
Actions

What you can do
with Heylibby.

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 Contact
heylibby:get_contact
Fetch a single contact by ID with their conversation history and qualification status.
Read Low risk
Get Conversation
heylibby:get_conversation
Fetch a single conversation by ID with all messages and metadata.
Read Low risk
List Contacts
heylibby:list_contacts
List contacts with filtering and pagination options.
Read Low risk
List Conversations
heylibby:list_conversations
List conversations with filtering and pagination options.
Read Low risk
Create Contact
heylibby:create_contact
Create a new contact in HeyLibby.
Write Medium risk
Delete Contact
heylibby:delete_contact
Delete a contact from HeyLibby. This action cannot be undone.
Write High risk
Handoff Conversation
heylibby:handoff_conversation
Hand off a conversation from AI to a human agent.
Write Medium risk
Qualify Lead
heylibby:qualify_lead
Manually qualify or update the qualification status of a lead.
Write Medium risk
Send Message
heylibby:send_message
Send a message in an existing conversation.
Write Medium risk
Update Contact
heylibby:update_contact
Update an existing contact in HeyLibby.
Write Medium risk
MCP & Runtime API

Call Heylibby
from any AI agent.

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

heylibby:get_contact READ
# Call via Runtime API
curl
-X POST \
  "https://api.cerebralos.com/v1/runtime/actions/run"
  -H "X-API-Key: YOUR_KEY" \
  -d '{
    "verb": "heylibby:get_contact",
    "args": {},
    "execution_id": "agent-001"
  }'
heylibby:create_contact 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": "heylibby:create_contact",
    "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 Heylibby.

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 Heylibby data
Call heylibby:get_contact 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 Heylibby
Dry-run validates heylibby:create_contact before execution
Approval gate fires if risk level is high
Action executes with full governance — logged, audited, reversible
Trigger
Lead or deal event
Score with AI
Route to right rep
Trigger outreach sequence
How it works

Every Heylibby action
governed end-to-end.

Cerebral OS isn't a connector. It's the execution layer that sits in front of Heylibby — 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 Heylibby action before it touches production. See exactly what would happen before a single real call is made.
Immutable audit trail
Every Heylibby action is logged — what ran, what changed, who approved it, when it happened. Full history on every verb, forever.
Connect with

Heylibby works best
alongside these.

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

Heylibby integration

Start free.
No credit card required.

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

Start free — 1,000 runs Browse all integrations →