Services

MCP Server

Connect a PersonAIzer persona — or your whole account — to Claude Desktop, Claude Code, Cursor, or any MCP-compatible client. One remote server, five tools, no custom integration code: add the config below and the client discovers everything itself.

Connect

URLhttps://sessions.personaizer.com/mcp

TransportStreamable HTTP (stateless)

AuthX-Api-Key

Rate120/min

Two kinds of key, depending on what you want the client to do. A persona secret key (pa_…) scopes every call to one persona — get one from that persona's Developer tab in the dashboard. An account-level key (ak_…) isn't scoped to any persona — it's for tools that create or manage personas across your account. There's no dashboard button for this one yet — mint it directly:

mint an account key — run once you're logged in

curl -X POST https://core.personaizer.com/api/account/api-key/regenerate \
  -H "Authorization: Bearer <your access token>"

# { "key": "ak_...", "info": { "id": "...", "prefix": "...", "created_at": "...", "is_active": true } }
# Copy the "key" now — like the persona secret key, it's shown once.

Stateless transport — every tool call is an independent request, same as the REST API. There's no MCP session to open or keep alive.

persona key — search, chat, upload

{
  "mcpServers": {
    "personaizer": {
      "url": "https://sessions.personaizer.com/mcp",
      "headers": { "X-Api-Key": "pa_..." }
    }
  }
}

account key — create & manage personas

{
  "mcpServers": {
    "personaizer": {
      "url": "https://sessions.personaizer.com/mcp",
      "headers": { "X-Api-Key": "ak_..." }
    }
  }
}

Quickstart

Zero to a working, chattable persona — no dashboard needed.

1. Mint an account key — see the curl example above, or reuse a persona secret key if you already have a persona.
2. Register the server with your MCP client using the config in Connect above (or the CLI command to the right, for Claude Code).
3. Ask your agent to use the tools — with the server connected, just prompt naturally: "use create_persona to build a persona from https://example.com, then check_persona_status until it's ready". The client calls create_persona, gets back { job_id, persona_id }, then polls check_persona_status — no manual JSON required, the tool schemas below are what the client reads to know how to call them.
4. Get that persona's own secret key from its Developer tab in the dashboard once it's built, then upload_knowledge_docs to feed it content and chat to talk to it.

claude code — register the server

claude mcp add --transport http personaizer \
  https://sessions.personaizer.com/mcp \
  --header "X-Api-Key: ak_..." --scope user

claude mcp list   # confirm "personaizer  ✔ Connected"

Persona-key tools

Scoped to one persona — authenticate with that persona's own secret key.

toolsearch_knowledge1 credit (fast) · 5 credits (smart)

Search the persona's knowledge base (site pages, documents, and products) for content relevant to a query — same retrieval as POST /v1/search.

toolchat1 credit

Send a message and get the persona's full reply, including any knowledge-base cards it surfaces — a non-streaming, call-and-wait variant of POST /v1/chat. Also works with an account-level key when personaId is given.

toolupload_knowledge_docs

Upsert structured knowledge documents (products, FAQs, etc.) into the persona's knowledge base. Persona secret key only — an account-level key is rejected here even if it can act on the same persona; create the persona first, then use its own key.

Account-key tools

Not scoped to any persona — authenticate with your account-level key.

toolcreate_persona

Start building a new persona from a website URL — scrapes the site, synthesizes an identity, generates an avatar, and (by default) harvests the site into the persona's knowledge base. Asynchronous (~1 minute) — returns job_id and persona_id; poll with check_persona_status.

toolcheck_persona_status

Poll the status of a persona build started by create_persona.