Same project.
Shared context.

Connect from the MCPBinder ChatGPT page.

Our ChatGPT connection page links directly to the directory listing when available, with a setup guide while the listing is awaiting publication. Sign in with MCPBinder, then choose the workspace and permissions. No API key is needed for this OAuth connection.

1. Add the remote MCP server.

In ChatGPT on the web, create a custom app from Settings → Apps → Create, or from Workspace settings → Apps → Create if you are an admin. Enable Developer mode if prompted. Enter this server address, choose OAuth, scan the tools, and sign in when asked. In Codex or another remote MCP client, add this address in the client’s MCP settings and choose OAuth if asked.

https://www.mcpbinder.com/api/mcp

2. Sign in and choose access.

Sign in to your MCPBinder account when prompted. Choose your workspace, projects, allowed actions, connected provider accounts, and expiry. A recent sign-in is required when adding access.

For a review-first workflow, start with read and propose permissions. Give direct write permissions only for actions the agent should be able to perform without a separate approval. Clients must request the scopes needed for those actions.

3. Check the connection with a small read.

Ask the agent to read the context for a project you allowed. Confirm that the result matches the intended workspace. It should not need your database credentials, Google password, or an AI subscription token.

If you grant write access, try a disposable task and inspect its history in MCPBinder. For a file operation, wait for the final operation status before treating the result as complete.

4. Keep permissions current.

Open Agent access in the workspace to reduce or revoke access. Expanding permissions requires reconnecting, a fresh sign-in if prompted, and new consent.

The same client can have separate connections to different workspaces. Reconnecting or revoking its access in one workspace leaves its other workspace connections intact; each token addresses one workspace.

If the connection needs attention.

• No OAuth flow: confirm the client supports remote HTTP MCP with OAuth.
• Only reading appears in the permission screen: the app requested read-only access. Reconnect with additional permissions; remove and re-add the connection if the app keeps the old request.
• Read works but editing fails: the client token and the MCPBinder grant both need the action’s scope. Reconnect to request more access.
• The agent reports no provider accounts: select the accounts during consent and allow the relevant file actions. The agent’s account list reflects its permissions, not every account in MCPBinder.
• Google actions fail: confirm the provider is connected and explicitly allowed in the grant.
• Access stopped: check membership, expiry, and revocation in Agent access.
• The agent did not wake for a recurring task: MCPBinder creates tasks and sends email reminders; it does not start an external agent conversation.