Lorikeet MCP Server

The Lorikeet MCP server allows AI tools like ChatGPT and Claude to access your Lorikeet account data directly, including workflows, tools, integrations, knowledge base articles, and more.

Looking to connect an external MCP server to Lorikeet as a tool provider? See the External MCP Servers page instead.

Once connected, you can:

Diagnose tickets - trace workflow execution and identify root causes
“Pull up ticket #12345. What went wrong and why did the customer get escalated?”
Audit knowledge bases - analyze articles at scale, find gaps, and spot quality issues
“Review all our knowledge base articles. Which ones are outdated, which topics have gaps, and are there any quality issues?”
Explore your setup - inspect workflows, tools, and integrations
“Give me a summary of what integrations are configured.”
Build workflows - create and iterate on workflows using natural language
“Create a new natural language workflow that handles refund requests by checking order status, verifying the return window, and processing the refund.”
Test tools - run and validate tool configurations directly from your AI assistant
“Test the ‘get-order-status’ tool with order ID 98765 and check if the response matches what we expect.”
Run simulations - test workflows against different customer scenarios
“Set up a simulation batch for the refund workflow with 3 different customer scenarios — a valid refund, an expired return window, and a missing order — and run it.”

MCP (Model Context Protocol) is an open standard for connecting AI tools to external data sources and services.

MCP server URL

Use a single, region-agnostic endpoint regardless of where your Lorikeet account is hosted:

https://mcp.lorikeetcx.ai

Authentication routes traffic to your account’s region automatically.

Setup

ChatGPT
Claude
Claude Code

Prerequisites

Access to ChatGPT with a Team, Business, or Enterprise subscription
Workspace Admin access is required for the initial setup (Steps 1–5). Once complete, all workspace members can use the app.

Connect

Open Workspace Settings

Go to chatgpt.com, click your profile icon in the bottom-left corner, and select Workspace settings.

Create a new app

In the admin panel, click the Create button.

Configure the app

Fill in the app configuration:

Name: Lorikeet
Description: Access your Lorikeet account.
MCP Server URL: https://mcp.lorikeetcx.ai
Authentication: Select OAuth

Click Create to proceed.

Authorize

You will be redirected to the Lorikeet authorization page. Sign in to your Lorikeet account and click Authorize.

Publish the app

After authorization, the Lorikeet app will appear in the Drafts section. Click on the app, then click Publish to make it available to your workspace.

Use the app

Workspace members can now use the Lorikeet app in their conversations:

Start a new chat
Click the + button near the message input
Click More to see all available apps
Select Lorikeet

Troubleshooting

For troubleshooting connection issues, refer to the ChatGPT apps docs.If you’re still having trouble, reach out to the Lorikeet team.

Prerequisites

Access to Claude with a Pro, Team, or Enterprise subscription

Connect

Open Settings

Go to claude.ai and click your profile icon in the bottom-left corner, then select Settings.

Add a Custom Connector

In Settings, click the Connectors tab, then click + Add Custom Connector.

You may need admin access to add custom connectors. Contact your workspace admin if this option is not available.

Configure the connector

Fill in the connector form:

Name: Lorikeet
Description: Access your Lorikeet account.
URL: https://mcp.lorikeetcx.ai

Click Add to proceed. Claude will automatically discover the OAuth endpoints.

Authorize

You will be redirected to the Lorikeet authorization page. Sign in to your Lorikeet account and click Authorize.

Verify

Once connected, the Lorikeet connector will appear in your Connectors list. Try asking Claude:

What Lorikeet account am I connected to?

Troubleshooting

For troubleshooting connection issues, refer to the Claude connector docs.If you’re still having trouble, reach out to the Lorikeet team.

Prerequisites

Claude Code installed on your machine

Connect

Run the following command in your terminal:

claude mcp add --scope user --transport http lorikeet https://mcp.lorikeetcx.ai

Then authenticate by running /mcp inside Claude Code and following the browser login flow.

Verify

Once connected, ask Claude Code:

What Lorikeet account am I connected to?

Troubleshooting

For troubleshooting connection issues, refer to the Claude Code MCP docs.If you’re still having trouble, reach out to the Lorikeet team.

Non-interactive access

For headless clients that have no browser to complete the interactive login, such as cloud agents, CI jobs, and scheduled scripts, authenticate with the client credentials grant, the standard OAuth 2.1 flow for machine-to-machine (M2M) access. If your client needs a human at any point, use the interactive tabs above instead.

Tokens issued this way are read-only. They can read workflows, tools, tickets, and other config, but cannot create or modify anything. Use the interactive flow if you need write access.

Create an API key

Generate a client_id and client_secret pair with the Create an API key endpoint. The secret is shown once, so store it somewhere safe.

Exchange it for an access token

POST to the token endpoint https://mcp.lorikeetcx.ai/oauth/token with grant_type=client_credentials. Send the secret in the request body (client_secret_post), or via HTTP Basic (client_secret_basic).

curl -X POST https://mcp.lorikeetcx.ai/oauth/token \
  --data-urlencode grant_type=client_credentials \
  --data-urlencode client_id=$LORIKEET_CLIENT_ID \
  --data-urlencode client_secret=$LORIKEET_CLIENT_SECRET

The response returns an access token:

{
  "access_token": "...",
  "token_type": "Bearer",
  "expires_in": 3600,
  "scope": "manage:read tickets:read customers:read"
}

The client credentials grant does not issue a refresh token, so request a new token once the one-hour token expires.

Connect your client

Pass the token as Authorization: Bearer <token> to https://mcp.lorikeetcx.ai. Any MCP client accepts a bearer token; the tabs below show the idiomatic wiring.

Codex
Custom agent (SDK)
Claude Code
Raw HTTP

Codex reads the bearer from an environment variable, so mint a token into it before launching:

export LORIKEET_MCP_TOKEN=$ACCESS_TOKEN
codex mcp add --url https://mcp.lorikeetcx.ai \
  --bearer-token-env-var LORIKEET_MCP_TOKEN lorikeet

Or in ~/.codex/config.toml:

[mcp_servers.lorikeet]
url = "https://mcp.lorikeetcx.ai"
bearer_token_env_var = "LORIKEET_MCP_TOKEN"

Codex reads the token once at launch and does not refresh it. The token expires one hour after it is minted, so mint a fresh one before each run.

If you are writing your own agent in code rather than using a prebuilt client, connect with the official MCP SDK (@modelcontextprotocol/sdk). Its ClientCredentialsProvider runs the token exchange and re-runs it to mint a new token when the current one expires, so you pass the key pair once instead of managing tokens yourself:

import { ClientCredentialsProvider } from '@modelcontextprotocol/sdk/client/auth-extensions.js'
import { StreamableHTTPClientTransport } from '@modelcontextprotocol/sdk/client/streamableHttp.js'

const provider = new ClientCredentialsProvider({
  clientId: process.env.LORIKEET_CLIENT_ID,
  clientSecret: process.env.LORIKEET_CLIENT_SECRET,
})

const transport = new StreamableHTTPClientTransport(
  new URL('https://mcp.lorikeetcx.ai'),
  { authProvider: provider },
)

Pass the token as a header:

claude mcp add --transport http --scope user lorikeet \
  https://mcp.lorikeetcx.ai --header "Authorization: Bearer $ACCESS_TOKEN"

To avoid re-minting by hand, point headersHelper at a script that mints the token; Claude Code re-runs it to get a new token when the current one expires. See the Claude Code MCP docs.

Open a session with initialize, then send the returned Mcp-Session-Id header on every subsequent request (tools/list, tools/call, and so on):

curl -X POST https://mcp.lorikeetcx.ai \
  -H "Authorization: Bearer $ACCESS_TOKEN" \
  -H "Content-Type: application/json" \
  -H "Accept: application/json, text/event-stream" \
  -d '{"jsonrpc":"2.0","id":1,"method":"initialize","params":{"protocolVersion":"2025-06-18","capabilities":{},"clientInfo":{"name":"my-agent","version":"1.0.0"}}}'

Technical details

Property	Value
Protocol	Model Context Protocol (MCP)
Transport	Streamable HTTP
Authentication	OAuth 2.1 (PKCE for interactive, client credentials for headless)
Token Lifetime	1 hour (interactive tokens auto-refresh; headless tokens are re-requested)

​MCP server URL

​Setup

​Prerequisites

​Connect

​Troubleshooting

​Prerequisites

​Connect

​Troubleshooting

​Prerequisites

​Connect

​Verify

​Troubleshooting

​Non-interactive access

​Technical details

MCP server URL

Setup

Prerequisites

Connect

Troubleshooting

Prerequisites

Connect

Troubleshooting

Prerequisites

Connect

Verify

Troubleshooting

Non-interactive access

Technical details