Clarify MCP
for LuumenAI

Read your CRM for context, then write records and campaigns as approved steps.

Connect Clarify MCP and Luumen can read your CRM the way you would: companies, people, deals, meetings, campaign engagement, saved lists, and the schema behind them. Reads come back right away. Changes — a new draft campaign, a comment on a record, an email draft — are shown first and wait for your approval. Auth is DCR OAuth.

The Clarify MCP toolbox

46 tools: 16 read, 30 write. Reads answer instantly. Writes require approval by default. Everything is logged.

  • ReadGet-agent-runsList an agent's runs, executions, invocations, and past run history, or fetch one run with its full transcript.
  • ReadGet-agentsList agents visible to the current user, or fetch a single agent by ID.
  • ReadGet-artifact-component-docGet the full prop contract for one or more Clarify design-system components available to artifacts — each component's summary, a usage snippet, and every prop with its type and allowed values.
  • ReadGet-artifact-sourceRead the current source of an existing artifact — the JSX of its applied version, plus its name and description.
  • ReadGet-calendar-eventsList the current user's calendar events in a time range.
  • ReadGet-campaign-recipientsList the individual people enrolled in a campaign, with their per-person engagement — who opened, who clicked, who replied, and when.
  • ReadGet-campaignsList campaigns in the workspace, or fetch a single campaign by ID with full details.
  • ReadGet-current-userGet information about the current authenticated user, including their timezone.
  • ReadGet-listsGet list metadata (saved views) for an entity type, or fetch a single list by ID.
  • ReadGet-recordsRetrieve detailed information about specific records by their IDs.
  • ReadGet-schemaGet the schema for Clarify entities.
  • ReadGet-workflow-runsGet execution runs for a workflow.
  • ReadGet-workflowsGet and search workflows in the workspace, or fetch a single workflow with its full configuration.
  • ReadQuery-analyticsExecute read-only ClickHouse SQL against the analytics event log.
  • ReadQuery-dataExecute PostgreSQL queries to retrieve data from Clarify.
  • ReadRead-contextRead Clarify product knowledge and documentation.
  • WriteAdd-commentAdd a comment to a supported entity. Approval by default
  • WriteCreate-campaignCreate a new email campaign (sequence) in DRAFT mode. Approval by default
  • WriteCreate-email-draftCreate an email draft in the user's connected Gmail or Outlook account for them to review, edit, and send themselves. Approval by default
  • WriteCreate-or-update-agentCreate or update an agent, an autonomous AI assistant. Approval by default
  • WriteCreate-or-update-artifactCreate a new artifact or write a new version to an existing artifact. Approval by default
  • WriteCreate-or-update-calendar-eventCreate a new calendar event or update an existing one. Approval by default
  • WriteCreate-or-update-custom-objectCreate a new custom object type or update an existing one in the workspace. Approval by default
  • WriteCreate-or-update-fieldsCreate new fields or update existing field metadata (name, options, AI config) on any entity (company, person, deal, meeting, or custom object). Approval by default
  • WriteCreate-or-update-listCreate or update a dynamic list: a saved view whose membership is defined by a SQL query. Approval by default
  • WriteCreate-or-update-recordsCreate or update records in Clarify. Approval by default
  • WriteCreate-or-update-workflowCreate a new workflow or update an existing one. Approval by default
  • WriteDelete-agentDelete an agent by its ID. Approval by default
  • WriteDelete-artifactDelete an artifact by its ID. Approval by default
  • WriteDelete-calendar-eventCancel a calendar event. Approval by default
  • WriteDelete-campaignDelete a campaign by its ID. Approval by default
  • WriteDelete-custom-objectDelete a custom object type by its entity identifier. Approval by default
  • WriteDelete-fieldsDelete one or more custom fields from an existing object (built-in entities like person, company, deal, or custom objects like c_my_object). Approval by default
  • WriteDelete-listDelete a list (saved view) by its ID. Approval by default
  • WriteDelete-recordsDelete one or more records by their IDs. Approval by default
  • WriteDelete-workflowDelete a workflow by its ID. Approval by default
  • WriteFind-leadsSearch Clarify's built-in prospect database of companies and people to find new leads matching criteria like industry, location, headcount, job title, seniority, and funding stage, and save… Approval by default
  • WriteImport-leadsImport leads from a tam_company or tam_person search into Clarify. Approval by default
  • WriteImport-meeting-transcriptImport a meeting transcript from an external source (Granola, Notion, Circleback). Approval by default
  • WriteManage-accessManage who can access a specific object — a list, meeting, message, task, or record (deal, company, person, or a custom object) — by granting, updating, revoking, or reading its access grants, or… Approval by default
  • WriteMerge-recordsMerge two or more records into a single primary record in Clarify. Approval by default
  • WriteRespond-to-calendar-eventRSVP to a calendar event you've been invited to. Approval by default
  • WriteRun-workflowStart a workflow run. Approval by default
  • WriteSend-emailSend an email immediately through the user's connected email account. Approval by default
  • WriteSubmit-feedbackSubmit concise feature requests or feedback about MCP tools. Approval by default
  • WriteUpdate-campaignUpdate an existing email campaign: rename it, change its target list, adjust the sender, edit its email steps, or configure send time windows. Approval by default

One prompt, start to finish

What a governed Clarify MCP run looks like inside Luumen.

Questions

How does LuumenAI connect to Clarify MCP?

Authorize once with OAuth 2.0. Luumen lists the scopes each action needs before you approve the connection, and credentials never appear in the chat.

Can LuumenAI change things in Clarify MCP on its own?

Read actions answer immediately. Anything that writes — add-comment, create-campaign, create-email-draft, create-or-update-agent, and more — is shown as a plan and requires approval by default, including the 21 actions classified as destructive. Administrators configure that per tool, so you decide exactly which actions can ever run unattended.

Who gets access to the integration?

You decide. Actions are granted per agent, skill, and team, and per environment — production is not staging. Read access can be broad while writes stay narrow.

Is there an audit trail?

Every call to Clarify MCP — read or write, approved or declined — is recorded with the actor, the input, and the result, and can be linked to the ticket or change record.

Put Clarify MCP to work with Luumen

Connect in minutes. Every action scoped, approved, and audited from day one.