Skip to content

Connect Worken MCP in different clients

Worken is a remote MCP server at https://mcp.worken.ru/mcp.

The server accepts both token types in Authorization: Bearer …:

PrefixHow to obtainBest for
wat_…OAuth 2.1 via https://api.worken.ruClaude Chat, ChatGPT Connectors, IDE OAuth
sk-…Project API key in the dashboardCursor (headers), Codex, CI, REST/SDK

Limits are usually on the client: some UIs only support OAuth; others also accept a static Bearer token.

Comparison

ClientMCP in UIOAuth 2.1API key in UI/configRecommendation
ClaudeYesYesNo (Connectors)OAuth
ChatGPTYes (Connectors)YesNo in web formOAuth
CursorYesYesYes (mcp.json headers)OAuth for humans, sk-… for CI
CodexVia configDepends on buildYes (env + Bearer)WORKEN_API_KEY + URL
DeepSeekNoNo MCPREST API or Cursor

Interactive examples (UI simulation)

Switch tabs to see typical connection screens. Fields are read-only for illustration; copy the config snippet at the bottom.

Shared endpoints

  • MCP endpoint: https://mcp.worken.ru/mcp
  • Authorization Server: https://api.worken.ru
  • Protected Resource Metadata: https://mcp.worken.ru/.well-known/oauth-protected-resource
  • AS Metadata: https://api.worken.ru/.well-known/oauth-authorization-server

OAuth 2.1 (Claude, ChatGPT, Cursor OAuth)

OAuth flow: discovery → consent → wat_…. Use MCP URL https://mcp.worken.ru/mcp, authorization server https://api.worken.ru, PKCE S256. Revoke under Connected apps in Worken. Full diagram (Russian): connect-claude.

API key (Cursor, Codex, servers)

  1. Create a project API key (sk-…).
  2. Send Authorization: Bearer sk-… on every MCP request.
  3. Keep keys in env or a secret manager — never in git.

Security

Do not put sk-… in URL query strings. OAuth access tokens (wat_…) are short-lived and refresh automatically.

DeepSeek and chats without MCP

DeepSeek Chat has no custom MCP connector yet:

  • use the Worken API with sk-…;
  • for MCP tools in the IDE, connect via Cursor (tab above).

Руководство пользователя Worken AI