Hosted MCP, CLI and Web. Three paths into the same shared space.
The primary MCP endpoint is https://tonk.foundation/mcp with OAuth. This matrix defines the current support scope and separates available releases and service discovery from completed client trials.
Use an owner-provided tool connection. With CLI v0.6.17 and a foundation-issued link, join with --via https://tonk.foundation.
Stable CLI v0.6.17
Published builds: macOS Apple Silicon and Linux x86_64.
Release checked
The released binary’s version and join/help commands were checked. Its default trust origin is tonk.network; foundation needs the explicit --via origin. Shared-state compatibility still needs a live round trip.
For hosted chat products, compatibility depends on the specific host, account and connection flow. Treat an unlisted combination as unverified until it passes the checks below.
Match the service.
Use tonk.foundation/mcp for the current hosted MCP path. Your Tonk sign-in and space grants must belong to the matching service.
Primary hosted MCP
tonk.foundation
OAuth discovery checked
MCP endpoint
https://tonk.foundation/mcp
GET /mcp returned 401 with “missing bearer token”; protected-resource discovery returned JSON naming this service.
Use this endpoint with OAuth. The service is deployed on the development environment; a signed-in tool round trip is still required in your chosen host.
These were unauthenticated GET checks. A 401 with OAuth discovery establishes an authentication requirement; it does not establish a successful sign-in or tool call. Other deployment environments are outside this recommended connection path.
Use the matching setup.
Start with one client and one space. Keep the connection’s identity, environment and version explicit.
01
Hosted MCP
Add https://tonk.foundation/mcp to an OAuth-capable MCP client. Choose OAuth, sign in to Tonk and approve the spaces and access level the agent needs.
The same endpoint serves every client below. Each client has its own installation and authorization flow.
ChatGPT web
Open Plugins, add a custom MCP server and enter https://tonk.foundation/mcp. Select OAuth.
Create the plugin, complete Tonk authorization, and install it.
Select the installed plugin with @ in a conversation. Workspace controls may restrict installation or use.
Official setup and OAuth metadata checked; a signed-in Tonk trial remains pending. Official instructions ↗
Claude remote connector
In Customize → Connectors, add a custom connector with https://tonk.foundation/mcp.
Choose sign-in, complete Tonk authorization and connect. Organization accounts may need an owner to add the connector first.
Enable the connector in the conversation.
Official remote-connector setup checked; a signed-in Tonk trial remains pending. Official instructions ↗
Claude Code over hosted HTTP
Add the remote HTTP connection with the command below.
Open Claude Code, run /mcp and authenticate the Tonk connection. Complete interactive sign-in before starting unattended runs.
claude mcp add --transport http tonk https://tonk.foundation/mcp
Official HTTP/OAuth setup and published client metadata checked; a signed-in Tonk trial remains pending. Official instructions ↗
After connecting, ask the agent to call tonk_list_spaces. Use an exact returned space subject for tonk_query and tonk_evaluate, with { space, document }.
If the client cannot show an invite or an interactive Tonk view, use Tonk’s agent access settings to grant the space and open its ordinary Web link to use the view.
02
CLI
Install the CLI in the environment where the agent runs, then check its version and space commands. A remote shell or container needs its own installation and connection.
tonk --version
tonk help spaces
For a tool connection issued on tonk.foundation, explicitly select that origin with the released CLI:
tonk join 'TOOL_CONNECTION_LINK' --name shared-work --via https://tonk.foundation
tonk --space shared-work pull
tonk --space shared-work show
tonk --space shared-work status
CLI v0.6.17 defaults invitation trust to tonk.network. The --via origin must match the service that issued your link. Follow the join walkthrough for details; creating a new space has separate account prerequisites.
03
Web
Open the human space link supplied by its owner and complete the access flow. Confirm whether you can read or edit, then try one sample contribution and check it from another client.
Need a space first? Request hosted access. Access is provisioned separately; a public MCP endpoint alone does not provide a shared workspace.
One small acceptance check
Make sure the work travels.
Run this in a disposable example space before moving a real workflow. Record the client, version and environment with the result.
Connect. List the intended space and confirm the granted access.
Read and write. Save a distinctive sample value and read back the same record.
Cross the boundary. Read that exact change from an independent client.
Return later. Restart the session and retrieve the saved work.
Check access. Confirm read-only writes are refused and revoked access is removed.
Sources and verification scope
Current product scope: hosted MCP at tonk.foundation/mcp, CLI and Web. Public HTTP checks and source contracts are verified separately from signed-in client and multi-person acceptance. Source links are pinned to revision bfb2d720d40b; rolling releases may change after the check date.