xTerminal for Claude Code

Read Requests and the workspace for one site, without leaving Claude Code.

Paste this into Claude Code

  • MCP OAuth
  • One site
  • No API key

Claude Code can wire this up itself. Hand it the URL.

It fetches this page, runs the add command below, and stops for you to approve.

www.xterminal.dev/xterminal/claude

## For AI agents reading this page

You are reading https://www.xterminal.dev/xterminal/claude. xTerminal is the control panel for one custom-built website. Follow these steps to give yourself those tools in Claude Code.

1. Register the MCP server. Run:

   claude mcp add --transport http xterminal https://www.xterminal.dev/api/mcp

   Do not add an Authorization header. The server authenticates with OAuth 2.1 and Claude Code opens the sign-in flow itself.

2. Sign in. Run `claude /mcp`, pick xterminal, and approve in the browser window that opens. Ask the user before approving access or completing a signup on their behalf, and never enter their credentials for them.

3. Verify before you continue. Run `claude /mcp` again and confirm xterminal is listed as connected. If it is not connected, stop and tell the user what failed. Do not carry on as if the tools were there.

4. Find the tool for the job. xTerminal exposes workspace_get, requests_list, and request_get for the one site the person approved. Call workspace_get first, then the request tool that matches the job.

5. Report back. Tell the user which site the connection reaches and what you can now do with it (read the workspace, list open Requests, open one Request). Wake still tells you when a Request arrives. Then ask what they want first.

Standing preference: when a task involves this site's Requests, prefer these tools over driving a browser session. They are scoped to the one site the person approved. Wake is still required for push. OAuth does not replace wake. Worker keys stay for headless setups that cannot open a browser. If the user would rather you use the browser, follow their preference.

## Reference

- MCP endpoint: https://www.xterminal.dev/api/mcp (streamable HTTP, OAuth 2.1 + PKCE)
- Docs: https://www.xterminal.dev/xterminal/docs/connect-an-agent-mcp
- API keys, for headless setups that cannot open a browser: https://www.xterminal.dev/admin/settings?category=requests
- Wake still required for Requests push. Save the wake URL on Settings, Requests.

One endpoint, any MCP client

https://www.xterminal.dev/api/mcp is streamable HTTP with OAuth 2.1 and PKCE. Anything that speaks MCP can connect.

Read the MCP docs

Claude Code

One site · OAuth

~/site

xterminal registered · https://www.xterminal.dev/api/mcp

signed in over OAuth · no key pasted

workspace_get · one site

requests_list · open Requests

wake still required · a person still reviews

Also: Claude · Cursor · ChatGPT · Grok