MCP

Plug your AI into Kleos.

Kleos speaks the Model Context Protocol. Connect Claude, ChatGPT, Gemini or any MCP-capable agent, and it can browse your creator CRM, discover new creators and read your campaigns, in plain language.

https://api.kleos.arthea.ai/api/mcp

One endpoint. Claude and ChatGPT connect with your Kleos sign-in; headless clients use a token from Settings → AI agents.

Works with the agents you already use.

Claude

Claude Code, Claude Desktop and claude.ai custom connectors, including Cowork sessions grounded on your live workspace.

ChatGPT

Custom connectors and the OpenAI Agents SDK connect to the same server. MCP is provider-neutral by design.

Gemini & more

Gemini, IDE agents, open-source frameworks: anything that implements MCP Streamable HTTP can drive Kleos.

What your agent can do.

Nine tools today, scoped to your workspace only. Reads are the default; write tools exist only on tokens you explicitly mint with write access.

brand_me

Your workspace: plan, shop, connections.

dashboard_metrics

GMV, ROAS, reach, engagement. The whole cockpit.

list_creators

Your roster, filterable by stage.

get_creator

One creator's full record and tracking.

discover_creators

Search the Kleos master database, ranked by brand fit.

list_campaigns

Gifting, outreach and sourcing campaigns.

add_creatorwrite

Add a creator to your roster.

move_stagewrite

Advance a creator through the pipeline.

set_trackingwrite

Set discount codes and UTM links.

Connected in three steps.

Paste the endpoint

In Claude or ChatGPT, add a custom connector and paste the URL above. When prompted, sign in with Kleos and approve. No keys to copy, revocable anytime.

Or mint a token

For Claude Code, IDEs and headless agents: generate a token in Settings → AI agents and send it as a bearer header. One command:

claude mcp add --transport http kleos https://api.kleos.arthea.ai/api/mcp \
  --header "Authorization: Bearer YOUR_TOKEN"

Ask away

“Which gifting creators drove sales this month?” “Find 20 skincare creators over 3% engagement and shortlist them.” Your agent does the clicking.

Built safe by default.

Your workspace only

Every token is scoped to one workspace. There is no cross-tenant surface, period.

Reads first, writes opt-in

A default token can look, not touch. Write tools appear only on tokens minted with write access.

Revoke in one click

Kill a token in Settings and every agent using it loses access instantly.

Everything audited

Token creation, revocation and use land in the same audit trail as the rest of Kleos.

Questions, answered.

What is MCP?

The Model Context Protocol is an open standard that lets AI assistants call external tools. Kleos implements it server-side, so any MCP-capable agent can operate your workspace with your permission.

Which clients are supported?

Anything that speaks MCP over Streamable HTTP with a bearer token: Claude Code, Claude Desktop, claude.ai custom connectors, ChatGPT connectors, the OpenAI Agents SDK, Gemini and most agent frameworks.

Can an agent spend money or message creators?

No. The MCP surface has no payment, sending or messaging tools. Writes are limited to roster management, and only on tokens you explicitly mint with write access.

Is it included in my plan?

Yes. MCP access ships with every Kleos workspace at no extra cost, including discovery reads.

Give your AI a marketing team.

Start free