01 / provider
Arsenkin
enabled
Mode: jobs
One endpoint / explicit authority
Provider access,
under control.
A single authenticated MCP surface for Telegram, Arsenkin, Yandex Search and Yandex Direct. Durable work, scoped tools, revocable identities and audit by default.
Canonical endpoint
https://mcp.zai.one/mcp
02 / provider
Crawl4ai
enabled
Mode: research
03 / provider
Keys So
enabled
Mode: read_only
04 / provider
Knowledge
disabled by policy
Mode: native_database_read_only
05 / provider
Passbolt
enabled
Mode: governed_server_custody
06 / provider
Telegram
enabled
Mode: embedded_write
07 / provider
Topvisor
enabled
Mode: read_write_guarded
08 / provider
Twenty Crm
enabled
Mode: read_write_guarded
09 / provider
Yandex Direct
enabled
Mode: read_write_guarded
10 / provider
Yandex Metrika
enabled
Mode: read_write_guarded
11 / provider
Yandex Search
enabled
Mode: jobs
12 / provider
Yandex Webmaster
enabled
Mode: read_write_guarded
Connection contract
Bearer token via a secret store
Authorization: Bearer <individual opaque token>
Tokens are shown once at issuance. The platform stores only an HMAC-SHA256 hash. Provider credentials never enter tool arguments.
Codex / config.toml
Environment-backed bearer
[mcp_servers.zai_mcp]
enabled = true
required = true
url = "https://mcp.zai.one/mcp"
bearer_token_env_var = "ZAI_MCP_TOKEN"
startup_timeout_sec = 10.0
tool_timeout_sec = 120.0
Set ZAI_MCP_TOKEN in the client secret environment, never in config.toml.
Claude Code / .mcp.json
Shared config, local secret
{
"mcpServers": {
"zai-mcp": {
"type": "http",
"url": "https://mcp.zai.one/mcp",
"headers": {
"Authorization": "Bearer ${ZAI_MCP_TOKEN}"
}
}
}
}
Claude expands the environment variable locally; the token is not committed with the project.
Safety
No write surface
Telegram sends and Direct apply tools are absent in v1.
Paid work
Four gates
Prepare, typed acceptance, budget reservation and idempotency.
State
PostgreSQL only
MCP-owned schema, durable jobs, no Redis.