Connect Cursor and other clients

Every GPT Workspace server speaks streamable HTTP with OAuth 2.0, so any client that supports remote MCP servers can use it. The only thing to configure is the URL; the client discovers the OAuth endpoints itself and opens Google’s sign-in page the first time.

Cursor

Open Cursor Settings ➤ MCP and click Add new global MCP server, or edit ~/.cursor/mcp.json (global) or .cursor/mcp.json in a project:

{
  "mcpServers": {
    "google-sheets": {
      "url": "https://api.gpt.space/servers/google-sheets/mcp"
    },
    "gmail": {
      "url": "https://api.gpt.space/servers/gmail/mcp"
    }
  }
}

Save, then click Connect or the sign-in link next to the server in the MCP settings. After Google’s consent screen the tools show up with a green dot.

VS Code (GitHub Copilot)

Run MCP: Add Server from the command palette, choose HTTP, paste the URL and a name. Or add to .vscode/mcp.json:

{
  "servers": {
    "google-docs": {
      "type": "http",
      "url": "https://api.gpt.space/servers/google-docs/mcp"
    }
  }
}

Click Start next to the server and sign in with Google when prompted.

Windsurf, Gemini CLI, other clients

Use the same shape: a server entry with a url (some clients call the field serverUrl or need "type": "streamable-http"). Check your client’s documentation for the exact key names.

Clients without OAuth support

Some clients only run local commands. Bridge the remote server with mcp-remote, which handles the OAuth flow in your browser and keeps the token:

{
  "mcpServers": {
    "google-drive": {
      "command": "npx",
      "args": ["-y", "mcp-remote", "https://api.gpt.space/servers/google-drive/mcp"]
    }
  }
}

Your own agent

Use any MCP SDK with the streamable HTTP transport and an OAuth client provider. The server exposes its metadata at:

https://api.gpt.space/.well-known/oauth-protected-resource/servers/<name>/mcp
https://api.gpt.space/.well-known/oauth-authorization-server/servers/<name>/mcp

Dynamic client registration is supported, so your agent does not need a pre-registered client id. A request without a valid token receives a 401 with a WWW-Authenticate header that points at the metadata above.