Artificial Intelligence
Z.ai MCP connector
Connect Z.ai to Elaichi and Claude, ChatGPT, Cursor, or the Elaichi Agent can generate images and video, transcribe audio, parse documents, search the web, and run Z.ai agents, with every request logged under the person who made it.
-
How it connects. Connects with an API key. The credential goes into a vault nobody reads back.
-
One address. https://api.elaichi.ai/mcp, the same for every user.
-
Their own access. An agent never gets more than the person it acts for.
How to connect
How to connect Z.ai to Claude, ChatGPT or Cursor
Two steps, about a minute.
In Elaichi
Connect Z.ai once
-
Open Connections, choose Add connection, and pick Z.ai.
-
Optionally set Share with to give a team access, then press Connect.
-
Paste a Z.ai API key. One person generates a token in Z.ai and pastes it once. Everyone else works through Share with, and never sees it.
The credential is vaulted. Nobody reads it back, not even the AI.
Add connection
Choose a connector.
In your AI client
Point it at one endpoint
Everyone in the organization uses the same address, and each person only ever reaches what their own account allows.
Connect Z.ai to Claude
-
1
Open Customize, then Connectors.
-
2
Press Add.
-
3
Name it, paste the MCP server URL, then Continue.
https://api.elaichi.ai/mcp -
4
Sign in and approve.
On Team and Enterprise, an Owner adds it once. Everyone else turns it on for themselves.
Connect Z.ai to ChatGPT
-
1
Open Plugins, then press the + button.
-
2
Name it and paste the endpoint into Server URL.
https://api.elaichi.ai/mcp -
3
Leave Authentication on OAuth, then tick the risk acknowledgement.
-
4
Press Create, then sign in and approve.
Works on the web today. The plugin directory lives at chatgpt.com/plugins.
Connect Z.ai to Cursor
-
1
Open
~/.cursor/mcp.json. -
2
Add the endpoint under
mcpServers.https://api.elaichi.ai/mcp -
3
Reload Cursor, then sign in and approve.
~/.cursor/mcp.json
{
"mcpServers": {
"elaichi": {
"url": "https://api.elaichi.ai/mcp"
}
}
}
Set up per machine, so repeat it on each computer you work from.
Connect Z.ai to any MCP client
-
1
Add the endpoint as a remote MCP server.
https://api.elaichi.ai/mcp -
2
Sign in and approve.
{
"mcpServers": {
"elaichi": {
"url": "https://api.elaichi.ai/mcp"
}
}
}
The Elaichi Agent already has these tools, with nothing to set up.
Use cases
What teams do with Z.ai through Elaichi
Every one of these runs inside the access the person already has, and lands in the same audit log.
-
Marketing
Turn a campaign brief into visuals
Describe the shot you need and get Z.ai images back for a landing page, ad, or social post. Ask for a different angle or color palette and the next version arrives in the same conversation.
-
Marketing
Draft a short product video from a script
Hand Z.ai a scene description and a script, then check back for the finished clip once it has rendered. Longer jobs run in the background so nobody sits and waits.
-
Support
Transcribe a recorded customer call
Drop in the recording and Z.ai returns a transcript you can read, quote from, and turn into follow-up actions. No more scrubbing through audio to find the moment a customer raised a complaint.
-
Operations
Pull the tables out of a scanned contract
Upload a PDF or scan and Z.ai's layout parsing returns the headings, paragraphs, and tables in order. Ask for the payment terms or renewal dates and get them from the right section.
-
Research
Read a competitor page and brief the team
Ask for a web search on a topic, have Z.ai read the pages that matter, and get a summary with the sources named. Useful before a pitch, a board update, or a pricing review.
-
Product
Set up a Z.ai agent for a recurring task
Create a Z.ai agent with the instructions for a job your team repeats, then start conversations with it and collect the results as they finish. One person configures it, everyone uses it.
Try asking
- “Summarize this week's Z.ai image generations by team.”
- “Which transcriptions did Support run in Z.ai yesterday?”
- “List Z.ai files uploaded by Research this month.”
AI tools
Z.ai tools for your AI agents
14 tools are ready to call through Elaichi's MCP endpoint the moment you connect Z.ai, governed by the same roles, restrictions, and audit log as everything else in Elaichi.
No tools match your search.
See it in Elaichi
What connecting Z.ai gets you
6 screens from the product, each doing one job for your Z.ai account.
The agent
Ask about Z.ai runs in plain language.
Starter prompts answer from live Z.ai completions, generations and files.
- completions
- generations
- transcriptions
- files
Ask Elaichi to work across your apps.
Summarize this week's Z.ai image generations by team.
Which transcriptions did Support run in Z.ai yesterday?
List Z.ai files uploaded by Research this month.
Also runs in Claude, ChatGPT or Cursor
MCP clients
Claude, ChatGPT and Cursor reach Z.ai.
One org MCP endpoint over OAuth, no SDK and no shared API key.
Copy the endpoint
Tool catalog
14 Z.ai tools ready without custom code.
Browse every Z.ai tool name, resource and method in one catalog.
- Create a Z.ai chat completion
- Create a Z.ai videos generation
- Get single Z.ai paas async result by ID
- Create a Z.ai images generation
Toolboxes
Every team gets its own Z.ai toolbox.
Toolboxes scope Z.ai completions, generations and agents to the teams that need them.
- Research
- Content
- Support
- Engineering
Shared connections
Teammates use Z.ai without seeing a key.
See who connected each Z.ai account and how many teams share it.
- Research
- Content Studio
- Support
- Engineering
Audit log
Answer who ran which Z.ai call.
Append-only log records when, who, what happened, type and resource.
- When
- Who
- What happened
- Type
Launching soon
From answering questions to doing the work
A person no longer has to ask. A trigger starts the work, inside the same permissions and the same audit log as everything else. Automations and live dashboards are launching soon, on the Black plan.
Automations
A schedule drives Z.ai work end to end.
Six steps fetch Z.ai completions, group them, draft a digest, await approval, post back.
Z.ai digest
Run 418 · started 2 minutes ago · on behalf of Emma Laurent
-
✓
Schedule
Every weekday at 08:00
0.2s -
✓
Fetch completions
Z.ai
1.4s -
✓
Group by owner
Transform
0.1s -
✓
Draft the digest
Agent step
Ran with 4 tools, returned a structured summary
6.2s -
Approve the digest
Needs approval
Assigned to Michael Brennan
Approve Deny -
Post the digest
Z.ai
Queued
Collections and dashboards
Z.ai health counted, not asked for.
Four metrics, 14 days of generations and a team breakdown, refreshed on schedule.
Z.ai health
Refreshed 4 minutes ago · every 15 minutes · from the completions collection
Completions
1,284 ↓ 12%
Generations
96 ↓ 8%
Needs attention
3 ↑ 2
Updated this week
412 ↑ 9%
Completions created
Last 14 days
By team
Share of activity
Research 34%
Content Studio 27%
Support 21%
Engineering 18%
FAQ
Frequently asked questions
How do I connect Z.ai to Claude?
First connect Z.ai in Elaichi by pasting in the API key from your Z.ai account, which takes under a minute. There is no OAuth application to register and no client ID or secret to generate. Then in Claude open Customize, then Connectors, then Add, and paste https://api.elaichi.ai/mcp as the endpoint. Sign in with your Elaichi account and Z.ai appears in Claude ready to use.
Does Z.ai work with ChatGPT and Cursor as well as Claude?
Yes. Once Z.ai is connected in Elaichi, the same endpoint, https://api.elaichi.ai/mcp, works in Claude, ChatGPT, Cursor, the Elaichi Agent, and any other MCP client. You connect Z.ai once and every client your team uses picks it up.
What can an AI agent actually do with Z.ai?
Through this connector an agent can ask Z.ai to write or answer in chat, generate images and video, transcribe audio recordings, and parse the layout of a PDF or scanned document into readable text and tables. It can also run a Z.ai web search, read a web page into text, upload a file for Z.ai to work on, count tokens before a long request, and create and talk to Z.ai agents. Long jobs like video run in the background and the agent collects the result when it is ready.
Does connecting Z.ai give the AI access to everything in my Z.ai account?
Z.ai connects with an API key, so the connection can do exactly what that key's Z.ai account allows and nothing beyond it. Elaichi can narrow that further, for example by allowing transcription and document parsing but not video generation, and it can never widen what the key already permits. Every request is recorded against the person who made it, not against the key.
Can I stop an agent from running expensive or unwanted actions in Z.ai?
Yes. Restrictions in Elaichi apply per action, so you can allow Z.ai chat and transcription while blocking image or video generation for a given team. A blocked action is never shown to Claude, ChatGPT, Cursor, or any other client, so no prompt, however worded, can reach it.
What happens to a Z.ai connection when someone leaves?
Offboarding a person in Elaichi ends their access to Z.ai at once across every client they had connected. If they were using a shared Z.ai connection, it keeps working for everyone else on the team. Disconnecting Z.ai once in Elaichi removes it from Claude, ChatGPT, Cursor, and every other client at the same time.
Put Z.ai in front of your team
Fourteen days on Gold, no credit card. Connect it once and pick what each team can call.