Skip to main content
If your AI client supports MCP, it works with UniversalBench. The protocol is open and the connection details are always the same: one URL.

Connection details

FieldValue
Personal MCP URLhttps://universalbench-mcp.penantiaglobal.workers.dev/u/ubk_xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
ProtocolMCP over HTTP (Streamable HTTP transport)
AuthBaked into the URL path
Content typeapplication/json
Accept headerapplication/json, text/event-stream
MCP toolsub_read (reads), ub_write (code and writes), ub_ai (AI and web)

Confirmed working clients

Continue

Open source AI coding assistant. Add UB to ~/.continue/config.json under mcpServers with a url field.

Zed Editor

Set up via Zed’s MCP extension. Paste your URL. UB appears in the assistant panel.

Cline (VS Code)

Add UB under “MCP Servers” in Cline’s settings panel with the URL field only.

Anything MCP

Any agentic builder that supports MCP. Paste your URL in their integrations panel.

Your own agent

Build with @modelcontextprotocol/sdk (Node) or mcp (Python). See below.

Build your own agent in Python

Build your own agent in Node and TypeScript

Direct JSON RPC without an MCP SDK

If you cannot or do not want to use the MCP protocol library, post JSON RPC envelopes to the URL directly:
The response is a server sent event with the JSON RPC result, or the result inline as JSON depending on your Accept header.

Alternative authentication

If you cannot embed the token in the URL path for some reason (rare), the API also accepts:
  • Authorization: Bearer ubk_your_key_here
  • X-Api-Key: ubk_your_key_here
  • ?key=ubk_your_key_here query parameter
The path embedded URL is preferred because it works in every MCP client without configuration.