Other MCP clients

Any MCP client that can call a remote server over HTTP and send a custom header can use blink artifacts.

Connection details

If your client supports OAuth, you do not need the header: the server answers 401 with a WWW-Authenticate header and offers OAuth 2.1 discovery (RFC 9728 metadata, dynamic client registration, PKCE). If it does not, use the Bearer token.

Create the token in the app under Agent connection. The server offers tools only; there are no prompts or resources. It returns 401 when the token is missing or revoked, and 429 when a token sends too many requests in a short time. Send the token only in the header: a ?token= in the URL is rejected with 400.

Check the connection

Once connected, the client should list more than thirty tools, starting with get_skill, create_artifact and publish_html. The server's instructions, sent when the client connects, ask the agent to call get_skill for a type before it creates or edits an artifact of that type.

Listening for questions

Use the generic harness with get_listener. If your client cannot run background processes, the agent can wait for questions with asks_wait, which returns as soon as someone asks or after a timeout of up to 55 seconds. See Listener & asks_wait.