Lorikeet

Name: Lorikeet MCP Server
Availability: InStock
Author: Lorikeet

HIPAA CompliantSOC2 ReadyISO 27001 Ready

Productivity106 tools

Build, diagnose and test Lorikeet support agents: workflows, guardrails, knowledge base, tickets, simulations. 106 tools, OAuth 2.1, any MCP client.

Verified connector

Listed by Anthropic as a partner connector in its Connectors Directory.

Connection checked by Agentman on 16 August 2026.

Anthropic states this reflects the level of review a connector received, not a security audit.

Connect Lorikeet via MCP

https://mcp.lorikeetcx.ai

Works in any MCP-compatible client. In Agentman Studio it is one click — no config file to edit.

Use in Agentman

Connect Lorikeet once and your agents call these tools on their own — on a schedule, in a workflow, with nobody at the keyboard.

Open in Agentman Studio

Lorikeet Tools & Capabilities (106)

whoami

get_brand

list_workflows

get_workflow

get_workflow_context

get_natural_language_workflow_guidelines

list_tools

list_integrations

list_integration_endpoints

list_integration_instances

list_apis

get_api

list_auth_configs

get_auth_config

list_articles

get_article

list_scrapers

get_scraper

list_guardrails

list_message_checks

list_agent_guardrails

get_guardrail

list_phone_numbers

search_available_phone_numbers

list_channel_configs

list_brand_guidelines

get_brand_guideline

get_taxonomy

get_validation_results

sample_recent_tickets

list_simulations

get_simulation

list_mock_profiles

get_mock_profile

list_simulation_batches

list_simulation_runs

list_simulation_results

create_tool

update_tool

test_tool

delete_tool

create_integration

update_integration

delete_integration

create_integration_instance

update_integration_instance

delete_integration_instance

create_integration_endpoint

update_integration_endpoint

delete_integration_endpoint

edit_natural_language_workflow_draft

read_natural_language_workflow

write_natural_language_workflow

edit_natural_language_workflow

create_natural_language_workflow

update_workflow

update_workflow_status

get_workflow_version_history

create_api

update_api

delete_api

create_auth_config

delete_auth_config

create_article

update_article

delete_article

create_scraper

update_scraper

delete_scraper

run_scraper

test_scraper

create_guardrail

create_message_check

create_agent_guardrail

update_guardrail

delete_guardrail

create_channel_config

update_channel_config

provision_phone_number

provision_chat_widget

create_brand_guideline

update_brand_guideline

delete_brand_guideline

configure_content_extraction

validate_taxonomy

deploy_taxonomy

list_ticket_ids

get_ticket

analyze_metrics

query_metrics

diagnose_ai_response

diagnose_ticket

get_quality_checks

get_ticket_quality_score

list_tickets_with_feedback

list_customers

create_test_ticket

add_test_message

create_customer

create_simulation

update_simulation

delete_simulation

create_mock_profile

update_mock_profile

delete_mock_profile

run_simulations

Tool names from Anthropic's directory listing. This server requires sign-in, so we could not read tool descriptions or parameter schemas.

Limits

It manages your Lorikeet configuration, not your customers' conversations. The tools act on workflows, guardrails, integrations, articles and simulations. This is a connector for the team that builds the support agent, not one that answers tickets on a customer's behalf.
A paid assistant plan is a real gate. Claude Pro, Team or Enterprise, or ChatGPT Team, Business or Enterprise, per Lorikeet's own prerequisites. ChatGPT additionally needs a Workspace Admin for setup.
No per-tool documentation exists publicly. Lorikeet's MCP page covers setup, transport, auth and skills, but publishes no tool reference. We read 106 names from Anthropic's directory and no descriptions, parameters or safety annotations, because the endpoint requires OAuth.
load_prompt is documented but absent from the directory listing. Lorikeet's skills page instructs clients to call a load_prompt tool, and the directory's own prompt_names field lists six prompts. That tool name is not among the 106 in the directory snapshot of 2026-08-16 — likely because MCP prompts are a separate protocol surface from tools. Expect the skill workflow to work as documented; do not expect to find load_prompt in a tool list.
Unguided use degrades quietly. Lorikeet's documented failure mode for skipping skill invocation is "silent failures that look fine in the UI" — a caution the vendor publishes about its own connector, and the reason the skills section above is not optional reading.
Most of the documentation site is private. Only the two MCP pages and the llms.txt index are publicly readable. docs.lorikeetcx.ai/ and pages such as /tools/mcp redirect to a login, so broader product context could not be cited here.
We did not exercise any tool. Our check was an anonymous protocol request that returned an OAuth challenge. Everything above about tool behaviour comes from Lorikeet's documentation or from the directory listing, not from running anything.

Frequently asked questions

A paid one. Lorikeet's setup docs list Claude Pro, Team or Enterprise for the Claude path, and a ChatGPT Team, Business or Enterprise subscription for the ChatGPT path. Claude Code has no plan requirement listed, only the CLI installed. Free-tier accounts on either assistant are not covered by the documented setup.

For ChatGPT, yes. Lorikeet states Workspace Admin access is required for the initial setup, after which all workspace members can use the app. For Claude, its docs warn you may need admin access to add custom connectors and to contact your workspace admin if the option is missing. Claude Code needs neither.

Because MCP has no automatic orchestration. Lorikeet's docs explain that Coach loads guided skills from your intent, while MCP exposes the underlying tools directly, so the assistant improvises. Its documented consequences are simulations created without test customer profiles, weak assertions, the wrong execution environment and silent failures. Invoke the skill explicitly instead.

Explicitly, and the syntax varies by client. Lorikeet documents a slash command such as /lorikeet:create-simulations in Claude Code, and a universal fallback for Claude, ChatGPT, Cursor, Continue and Cline: ask the assistant to use the Lorikeet load_prompt tool to load a named skill, then describe the task.

One hour. Lorikeet's technical details table gives a token lifetime of 1 hour and states that interactive tokens auto-refresh while headless tokens are re-requested. Sign-in uses OAuth 2.1, with PKCE for interactive clients and client credentials for headless ones, so no API key is pasted into the assistant.

No. Lorikeet documents a single region-agnostic URL, https://mcp.lorikeetcx.ai, and states that authentication routes traffic to your account's region automatically. That holds regardless of where the account is hosted, so the same connect string works for every customer and no region-specific hostname is published.

Sources

Live OAuth posture check against https://mcp.lorikeetcx.ai/ — an anonymous initialize returns HTTP 401 invalid_token, and the server publishes an RFC 9728 .well-known/oauth-protected-resource document (HTTP 200). This is our own observation on 2026-08-16, and it is why the sign-in requirement above is stated as verified rather than quoted from the vendor. It is also why no tool descriptions or parameter schemas appear on this page: the handshake never reached tools/list. · retrieved 2026-08-16
Lorikeet MCP Server documentation (HTTP 200, retrieved 2026-08-16 via the Markdown variant at /mcp/mcp-server.md) · retrieved 2026-08-16
Running simulations from MCP (HTTP 200, retrieved 2026-08-16 via /mcp/skills.md) · retrieved 2026-08-16
Lorikeet documentation index (HTTP 200, retrieved 2026-08-16; lists two public pages, both used above) · retrieved 2026-08-16
Live auth posture check against https://mcp.lorikeetcx.ai — HTTP 401 with WWW-Authenticate: Bearer realm="MCP" and an OAuth protected-resource pointer (2026-08-16) · retrieved 2026-08-16
Anthropic Connectors Directory entry, including the 106 tool names, permissions and tier (from the committed directory snapshot of 2026-08-16) · retrieved 2026-08-16
Lorikeet support — <support@lorikeetcx.ai> · Privacy (HTTP 200, checked 2026-08-16) · retrieved 2026-08-16