# MCP connectors sign in through a new OAuth server

> Claude, ChatGPT, and other MCP clients reconnect once onto a new sign-in server, and every connector token now works only for the workspace it was set up for.

Oct 27, 2026. Topics: Developers, Security, Integrations. https://www.generalinput.com/changelog/2026-10-27-mcp-connector-sign-in

We rebuilt how Claude, ChatGPT, Claude Code, Codex CLI, and other MCP clients sign in to your General Input workspace. Connectors now follow the current MCP authorization standard end to end, and every access token is tied to the one workspace whose server URL you connected. Each connector needs to reconnect once: the next time your AI tool calls General Input, it asks you to sign in again, and after you approve it on the same Connect screen it works as before. Your workspace, integrations, and tools are unchanged. Read how the [MCP server](/blog/general-input-mcp) works.

### How it works

- **Reconnect once.** Tokens issued before this update stop working. Your AI tool shows a sign-in prompt, and once you approve it the connector picks up where it left off.
- **One workspace per token.** A token names the workspace URL it was issued for, so a connector set up for one workspace can't be used with another, even by someone who belongs to both.
- **Nothing to configure.** Clients still find the sign-in server from the workspace URL itself and register themselves, as the MCP specification describes.
- **Requests that expire.** The sign-in and approval pages carry your AI tool's request for ten minutes. If one expires, start connecting again from the tool.