Documentation

Connecting a client

Junkt is a remote MCP server, so there is nothing to install and nothing to run. You paste one URL, approve the connection once, and the tools appear.

Your server URL

Every account uses the same endpoint. Your identity comes from the OAuth token, not from the URL, so there is no per-account address to keep secret: 

https://junkt.io/mcp

It is also shown on your dashboard with a copy button, alongside the connectors you have already approved.

Claude and Claude Cowork

  1. Open Settings → Connectors.
  2. Choose Add custom connector.
  3. Paste the URL above and confirm.
  4. Claude opens Junkt in a new tab. Log in if you are not already, then approve the connection.
  5. Junkt's tools appear in the connector's tool list. That is it.

There is no client ID or client secret step. Junkt supports Dynamic Client Registration, so the client registers itself during that first handshake.

Claude Desktop

Same flow, same URL. Desktop's connector settings live under Settings → Connectors → Add custom connector. Because Junkt is remote rather than a local stdio server, there is no JSON config file to edit and nothing to keep running on your machine.

Claude Code

Add it from the command line, then run /mcp inside a session to complete the OAuth approval in your browser: 

claude mcp add --transport http junkt https://junkt.io/mcp

Worth knowing: because the state lives on Junkt rather than on disk, keys written from one worktree are readable from another, and from a Cowork task running while your laptop is shut.

Other MCP clients

Junkt is a standard remote MCP server over HTTP with OAuth 2.1, so anything implementing the spec connects the same way — ChatGPT custom connectors, Cursor, and the rest. Point the client at the URL above and let it discover the rest. The discovery metadata is published where the spec says it should be:

  • /.well-known/oauth-authorization-server — authorization server metadata (RFC 8414)
  • /.well-known/oauth-protected-resource — protected resource metadata (RFC 9728)

Your first call

Ask the model to list what it has stored. On a new account the answer is nothing, which is the correct answer and proves the connection works: 

"Use Junkt to list my keys."

Then give it something to remember:

"Store 'ok' under the key demo:hello using Junkt, then read it back."

Both calls show up in the activity list on your dashboard, tagged as coming from MCP.

Revoking a connector

Your dashboard lists every connector you have approved and the date you approved it. Revoking one invalidates its token on the next call it makes. Your keys are untouched — revoking access does not delete state.

When it does not work

  • The tools do not appear. The OAuth approval probably did not complete. Remove the connector and add it again, watching for the Junkt tab.
  • Calls fail after a while. Check the connector is still listed on your dashboard and has not been revoked.
  • A write is rejected. Read the error message — they are written to be read by the model and say exactly which limit was hit. The tool reference lists all of them.
  • Something else. Get in touch.

Ask an AI

Junkt is built for agents, so ask one

Pick a question and where to ask it. Each link opens a fresh chat with the question already written, including a nudge to give you a straight answer rather than a sales pitch.

Models get things wrong about small products. The docs are the source of truth, and llms.txt is the version written for them.