API and MCP

Connect your data.
Work with context.

Recognize customers in your product. Work with conversations, tickets and tasks in your AI tools. Choose the path that fits your workflow.

Book a demo Choose your integration

Explore the product in a demo tailored to your business.

One shared context

Your applicationWidget APIidentify() · goal()

Customer and visit

ChatGPT · VS Code · Gemini CLIMCPread / write

Context and action

On your customer’s website and in your team’s tools. Two different uses, the same Meetlead.

Widget API · JavaScript

Pass the signed-in user’s identity to the widget. Your team gains customer context, while configured goals measure events from your product.

Identity and custom customer attributes
Goals after a confirmed product action
CSAT ratings and consent controls

Identity setup guide

IdentifyJavaScript

const identity = {
  userId: currentUser.userId,
  name: currentUser.name,
  email: currentUser.email
};

const meetlead = window.meetlead || (window.meetlead = { q: [] });
if (typeof meetlead.identify === 'function') {
  meetlead.identify(identity);
} else {
  meetlead.q.push(['identify', identity]);
}

GoalsJavaScript

const meetlead = window.meetlead || (window.meetlead = { q: [] });
const goal = { value: order.total, currency: order.currency };

if (typeof meetlead.goal === 'function') {
  meetlead.goal('purchase', goal);
} else {
  meetlead.q.push(['goal', 'purchase', goal]);
}

Profile assignment needs no secret. History access requires separate verification. The purchase key must refer to an active goal for this website. The full guide covers queuing before the widget loads.

Goals, CSAT and consent

Model Context Protocol

Meetlead context.
In your AI tool.

Connect ChatGPT, VS Code, Gemini CLI, Codex, Claude Code, Cursor or Windsurf to your workspace. Read a request, create a task and leave concrete next steps for your team.

01
Add the server in your application
Open MCP Server in Meetlead settings. Choose your application and add the configuration containing the server URL.
02
Sign in and approve access
Complete OAuth sign-in. As the owner, choose your workspace, read access and optional write access.
03
Choose the correct website
Start with list_applications. Use its applicationKey in subsequent operations.

CodexShell

codex mcp add meetlead --url https://api.meetlead.eu/mcp
codex mcp login meetlead

Claude CodeShell

claude mcp add --transport http meetlead https://api.meetlead.eu/mcp

CursorJSON

{
  "mcpServers": {
    "meetlead": {
      "url": "https://api.meetlead.eu/mcp"
    }
  }
}

ChatGPTURL

https://api.meetlead.eu/mcp

VS Code / CopilotURL

https://api.meetlead.eu/mcp

Windsurf (Cascade)JSON

{
  "mcpServers": {
    "meetlead": {
      "serverUrl": "https://api.meetlead.eu/mcp"
    }
  }
}

Gemini CLIJSON

{
  "mcpServers": {
    "meetlead": {
      "httpUrl": "https://api.meetlead.eu/mcp"
    }
  }
}

You do not create or copy a token. Find each application’s sign-in instructions in MCP Server settings. Claude Code uses /mcp; Gemini CLI uses /mcp auth meetlead.

MCP performs supported internal actions. It does not send replies to customers.

Conversations and tickets

Read a transcript, add an internal note, update a ticket status or priority.

Projects and tasks

Create a task, comment and link to the source request. Projects must be active.

Help center

Read articles, prepare drafts and manage publication with administrator permissions.

Reports and configuration

Use reports, Widget Studio configuration and automation tools within the granted scope.

From context to action

From a ticket to a task.

Skip copying the whole history. Ask for a concrete outcome and keep a link to the source.

“Read ticket #124. Create a task in Projects with a description of the problem and a link to the ticket.”

list_applicationsChoose the website
get_ticketRead the request
create_project_issueCreate the task
link_project_issueLink the source

Example prompt. Writing requires write scope, appropriate permissions and an active Projects App.

Meetlead Projects task board. — Customer requests and team tasks in one place.

Access under your control

You set the scope.

read allows data access. write adds supported changes and includes reading. Roles, limits and active Apps still apply. Disconnect the application in MCP Server settings whenever needed.

OAuth sign-in · Consent for up to 30 days · Disconnect at any time

Good to know

Before your first connection.

Let’s discuss your integration

How is MCP different from Meet AI?

Meet AI assists visitors and operators inside Meetlead. MCP connects an external AI tool to a controlled scope of workspace data and actions.

Who can connect an application through MCP?

Only the workspace owner. During OAuth sign-in they choose the workspace and access scope. Consent lasts up to 30 days and can be revoked earlier in MCP Server settings.

Can an assistant reply to customers through MCP?

No. The current scope covers reading and selected internal actions such as notes, tickets, Projects and help articles.

Can I send goal events without configuring them first?

No. The key must refer to an active goal configured for that website. Define what the event means and trigger it after confirmed success.

Does an MCP connection bypass App access?

No. The granted access scope, user permissions and active installation still apply. Write access does not activate an inactive App or enable arbitrary operations.

Start with one connection.

Documentation for implementation. A demo if you want to see the full workflow first.

Open documentation Book a demo