Hither docs

Add Hither to your AI app

For people adding Hither to an AI app, and coding agents that can run the setup themselves.

Every app connects the same way. Add https://hither.dev/mcp as a remote MCP server over Streamable HTTP, and the app handles sign-in with OAuth. No token goes in the configuration. When the sign-in page opens, sign in to keep access, or choose Continue without an account for 24 hours per computer. Then ask the agent to connect your computer and approve it there. Add the server once; the add command and the plugin each create a copy.

These steps follow each app's own documentation as of 2026-11-01. Pi was run as far as sign-in, in Pi 1.4.0 on 2026-11-03. Nobody has yet tested a signed-in session on a real computer through these apps.

An app that can't add an MCP server at all can still connect over REST for 24 hours.

Starter prompts

In a chat app:

Use Hither to connect my computer. Give me the approval link and wait until it is online before working on it.

In a coding agent, which can run most of the setup itself:

Set up Hither for this agent using https://hither.dev/skill.md. Run the setup steps you can perform yourself. Ask me to sign in when needed and give me the connection approval link. Wait for my computer to be online before working on it.

Claude

In Claude connectors, choose Add, Custom, Web. Enter https://hither.dev/mcp and sign in. Workspace administrators may control custom connectors. Source.

ChatGPT

In ChatGPT Plugins, select the plus button, then Add custom MCP server. Enter https://hither.dev/mcp, choose OAuth and sign in. Older interfaces use Settings, Apps, Create. Source.

Grok

Add https://hither.dev/mcp in Grok's custom connector settings and sign in. If your account lacks that control, use Claude or ChatGPT. Source.

Claude Code

claude mcp add --transport http hither https://hither.dev/mcp

Open /mcp and sign in. Or install the plugin, which adds the server and this skill: claude plugin marketplace add KohliNaman/hither, then claude plugin install hither@hither. Source.

Codex

codex mcp add hither --url https://hither.dev/mcp
codex mcp login hither

Or install the plugin: codex plugin marketplace add KohliNaman/hither, then codex plugin add hither@hither. Source.

Gemini

Gemini on the web has no verified way to add a custom MCP server, so use Gemini CLI. Merge this into its settings, then run /mcp auth hither:

{ "mcpServers": { "hither": { "httpUrl": "https://hither.dev/mcp" } } }

Source.

OpenCode

Merge into opencode.json, then run opencode mcp auth hither. Source.

{
  "mcp": {
    "hither": { "type": "remote", "url": "https://hither.dev/mcp", "enabled": true }
  }
}

Hermes

Merge into ~/.hermes/config.yaml, run hermes mcp login hither, then start a new session or run /reload-mcp. On a remote host, sign-in needs a forwarded port; Hermes's OAuth over SSH guide covers it. Source.

mcp_servers:
  hither:
    url: "https://hither.dev/mcp"
    auth: oauth

OpenClaw

openclaw mcp set hither '{"url":"https://hither.dev/mcp","transport":"streamable-http","auth":"oauth"}'
openclaw mcp login hither
openclaw mcp probe hither

If the commands differ in your version, check openclaw mcp --help. To also get this skill, run openclaw plugins install hither --marketplace KohliNaman/hither and keep the mcp set entry above. The bundle's server has no OAuth setting, and your hither entry replaces it. Source.

Pi

Pi 1.0 and later use built-in MCP:

pi mcp add hither --url https://hither.dev/mcp --exposure deferred --description "Use a computer its owner approved: files, Terminal, browser and local MCP servers."
pi mcp login hither

On a remote host, paste the redirected URL back into Pi when sign-in asks. --exposure deferred keeps the tools out of each prompt until tool search loads them. From a checkout of the repository, pi install ./plugins/pi adds the server and this skill as a package; a hither entry in mcp.json overrides it. Pi's own read, write, edit and bash stay on the Pi host. Source, Pi 1.5.0.

Cursor

Merge into .cursor/mcp.json, then connect from Cursor's MCP settings to sign in. Connect your AI has an install button. Source.

{ "mcpServers": { "hither": { "url": "https://hither.dev/mcp" } } }

VS Code and Copilot

Merge into .vscode/mcp.json, start the server from VS Code's MCP controls, trust it and sign in. Turn on its tools in Copilot agent mode. Source.

{ "servers": { "hither": { "type": "http", "url": "https://hither.dev/mcp" } } }

Other MCP clients

Add a Streamable HTTP server at https://hither.dev/mcp with OAuth discovery and no Authorization header. The client needs protected resource discovery, S256 PKCE and resource indicators. OAuth details lists the rest. These two calls show what the server offers and grant nothing:

curl -fsS https://hither.dev/.well-known/oauth-protected-resource/mcp
curl -fsS https://hither.dev/.well-known/oauth-authorization-server

A client without OAuth can connect over REST instead, for 24 hours. Source.