Skip to main content

Developer docs

Read-only MCP capabilities for assistant guided business analysis.

Logic Igniter MCP helps customer visible, operations, and developer teams ask an assistant to retrieve context, score inputs, summarize findings, and recommend next steps. It is designed for safe analysis only: production actions remain in your application through the REST/JSON API.

Who it is for

MCP is for teams that want AI supported analysis while keeping customer impacting actions behind established product workflows. It is useful for developers building assistant experiences, customer success teams preparing account reviews, revenue teams researching opportunities, and operators triaging work before taking action in the product.

Read-only capabilities

Retrieve business context

Bring relevant service information into a supported assistant so teams can investigate customer, revenue, operations, or workflow questions faster.

Score and prioritize inputs

Evaluate records or scenarios against subscribed Logic Igniter capabilities and return ranked signals for human review.

Summarize findings

Turn service responses into concise summaries that help sales, success, operations, and technical teams understand what matters next.

Recommend next steps

Provide decision support for follow up actions while leaving every production action under your application and team controls.

Entitlement boundaries

MCP access follows the same subscribed bundle boundaries as API access. If a capability is not included in your subscription, it is not available through MCP. MCP does not expand permissions, expose unavailable services, or change what your organization is allowed to use.

Setup details are provided during onboarding for approved customers and developer partners. Use the contact path below if you need MCP enabled for a subscribed bundle. Documentation examples use redacted key shapes such as li_... only; never paste real API keys, customer data, or production credentials into an assistant transcript.

What MCP will not do

  • Create, update, delete, publish, send, notify, schedule, charge, or modify records.
  • Bypass subscribed bundle access, approval workflows, or application permissions.
  • Replace your production API integration for actions that change business state.

API or MCP?

A teammate wants assistant guided research, scoring, summaries, or recommendations.

Use MCP for read-only analysis.

Your application must submit, approve, send, publish, charge, or update something.

Use the REST/JSON API and your application workflow.

A prospect or internal team needs a safe product walkthrough before implementation.

Use MCP examples to explain analysis workflows without promising write access.