MCP server
Reach your Taizen workspace from any MCP client over OAuth 2.0.
Taizen runs a public MCP (Model Context Protocol) server. Third-party AI clients — Claude Code, Claude Desktop, Cursor and others — connect to a Taizen account over OAuth 2.0 and work with your data, agents and integrations through a small set of tools.
The practical payoff: you can ask your own call history and CRM questions from inside the tool you're already working in, and drive Taizen agents from there.
How it works
MCP client ──OAuth──▶ taizen-mcp ──▶ Taizen backend
├──▶ vector store (semantic search)
└──▶ agent service- The client performs OAuth 2.0 with PKCE against the Taizen MCP server.
- The server authenticates you against Taizen and issues an access token.
- On every tool call, that token is used to call Taizen on your behalf. You only ever see your own workspace.
The server speaks MCP over SSE, and OAuth discovery follows the standard well-known endpoints (RFC 8414 and RFC 9728), so compliant MCP clients auto-configure from the URL alone.
What you get
Six tools, covering search, assets, and running the agent:
| Tool | Does |
|---|---|
search_knowledge | Semantic search across your indexed calls and documents, grouped by project |
list_assets | List the marketing assets in your workspace |
get_asset | Fetch one asset, with a short-lived download URL if it has a file |
run_agent | Run Taizen's agent on a question or task, continuing your current conversation |
new_conversation | Reset the conversation context |
list_integrations | List workspace and user integrations (keys are stripped) |
Full detail: MCP tools reference.
What it's good for
- Asking your own data from your editor. "What did buyers say about pricing last quarter" without switching windows.
- Driving agents from a coding session.
run_agentruns the same agent as the product, including asset generation. - Feeding another agent your buyer research. An assistant that can search your real calls writes very differently from one that can't.
What it isn't
- Not the internal relay. Taizen also runs an internal MCP relay that proxies vendor APIs from inside the VPC. That's infrastructure, not something you connect to.
- Not the reverse direction. Connecting external MCP servers so your Taizen agents can use their tools is Settings → MCPs.
Get connected
Connect a client — Claude Code, Claude Desktop, Cursor.