Services
MCP Server
Connect your PersonAIzer 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
One key: your account key (ak_…), minted on your profile page (Account API Key) or from any persona's API tab. Nothing is scoped to a persona — the tools that act on one take its personaId, and the knowledge tools name the source_id they write to. It's shown once; regenerating it replaces it everywhere.
Stateless transport — every tool call is an independent request, same as the REST API. There's no MCP session to open or keep alive.
{
"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 your account key on the profile page (Account API Key).
- 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 pollscheck_persona_status— no manual JSON required, the tool schemas below are what the client reads to know how to call them. - 4. Feed and talk to it — the build created a brand for the site with a source named by its host — take its id from
GET /v1/knowledge/sources;upload_knowledge_docs(products) orupload_knowledge_text(text) into that source by id, andchatwith thepersona_idyou got back.
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 & knowledge tools
Act on one persona, or one knowledge source — its id in the call.
chat10 creditsSend 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.
upload_knowledge_docsCreate or update products in a knowledge source. Every persona speaking for the source's brand answers from them once processing completes.
upload_knowledge_textAdd a plain-text document, stored as a .txt file. For PDFs and other files, use POST /v1/knowledge/sources/{source_id}/documents/upload.
Account tools
Create personas across the account.
create_personaStart 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.
check_persona_statusPoll the status of a persona build started by create_persona.