xTerminal for Cursor

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

Paste this into Cursor

  • MCP OAuth
  • One site
  • No API key

The agent in your repo can write its own config. Give it the URL.

It fetches this page, writes .cursor/mcp.json itself, and stops for you to sign in.

www.xterminal.dev/xterminal/cursor

## For AI agents reading this page

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

1. Register the MCP server. Write this into .cursor/mcp.json:

   { "mcpServers": { "xterminal": { "url": "https://www.xterminal.dev/api/mcp" } } }

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

2. Sign in. Open Cursor's settings, find xterminal under MCP, and start the sign-in. Approve the connection in the browser tab it 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. Back in Cursor MCP settings, confirm xterminal is connected and its tools are listed. 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.

Safe to commit

.cursor/mcp.json holds an endpoint and a name, nothing secret. Every developer signs in as themselves.

Read the MCP docs

Cursor

Composer · Cursor

~/site

wrote .cursor/mcp.json · project scope

signed in over OAuth · no key in the repo

workspace_get · one site

requests_list · open Requests

a person still reviews · wake still required

Also: Claude · Cursor · ChatGPT · Grok