OpenApps

CatchIntent MCP MCP server — tools & history

CatchIntent MCP MCP server: observed open status, tool schemas, linked apps and version history.

CatchIntent MCP

Endpoint: https://engine.catchintent.com/mcp

Observed status: open. Checked: 2026-10-12T05:09:09+00:00.

Linked apps

  • CatchIntent MCP

    CatchIntent is the intent data layer for AI-native teams. Connect Claude, Cursor, or any AI tool. Query your signals, manage listeners, and run your GTM workflows, all through natural language. Your data, your AI, your workflows.

Observed tools

  • lead_enrich — Trigger full LinkedIn profile enrichment via Apify (~$0.002, idempotent).
  • lead_get — Get full details of one lead: profile, discovery context (fit reason, pain hypothesis, role signals, disqualifiers), the AI-drafted outreach sequence (lead.outreach), warmth score, and status.
  • lead_push_to_crm — Push leads to your connected CRM (HubSpot, Close, Pipedrive, Zoho). Each lead becomes a contact / deal in the destination. Lead status does not change automatically — call lead_update_status to mark as `pushed` once CRM confirms.
  • lead_regenerate_sequence — Re-draft the lead's AI outreach sequence (LinkedIn/X steps). Optional instructions steer the rewrite. Capped per lead — edit directly once the cap is hit.
  • lead_search — Search leads in the workspace. A lead is always a person discovered on LinkedIn. Filter by warmth, status, or text.
  • lead_update_sequence — Replace the lead's outreach sequence steps with edited versions (marks the sequence as edited).
  • lead_update_status — Move a lead through the triage funnel. Valid transitions: NEW → SEEN/SAVED/PUSHED/ARCHIVED, SEEN ↔ SAVED, SAVED → PUSHED/ARCHIVED, PUSHED → ARCHIVED, ARCHIVED → SEEN. PUSHED is irreversible — it marks handoff to an outreach tool / CRM.
  • product_create — Create a new product. You can set sell (name/description/keywords/competitors), the structured offer, voice, and reach (roles/seniority/functions). Company firmographics (industries/size/country) are set in the dashboard, not here. Brand fields are optional and can be filled later via product_update.
  • product_delete — Delete a product. Fails only if it's the workspace's only product. Its audience and leads cascade-delete.
  • product_get — Resolved brand profile for a product, returned as nested sections with human-readable labels: sell (name/description/keywords/competitors/offer), fit (company firmographics), reach (roles/seniority/functions), plus offer, voice, and domain. Drives all AI scoring + outreach drafting for that product.
  • product_list — List every product/brand tracked by this workspace. Each product has its own brand profile, audience, and leads. Returns id, name, and timestamps.
  • product_update — Update a product. Partial — only provided fields change. You can set sell (name/description/keywords/competitors), the structured offer, voice, and reach (roles/seniority/functions). Company firmographics (industries/size/country) are set in the dashboard, not here. Reach labels are resolved strictly to canonical IDs; unknown values rejected.
  • workspace_icp_options — Get the valid Seniority Level and Job Function labels for product targeting (the reach dimensions MCP can set; roles are free text). Call this before product_update — unknown labels are rejected, never silently dropped.
  • workspace_usage — Current workspace usage vs plan limits: leads delivered this billing period, team members, products, AI compute budget, daily/monthly caps.

Data as of 2026-10-12T05:09:09+00:00.

OpenApps records store listings and observed changes. Store ranks are not download counts; launch dates may be derived or use the first observation. Coverage gaps are shown in the interactive catalog.

REST API specification · Guide for AI clients · Manage API keys and MCP connections