Skip to main content

​
MCP Connection

The Social Glass plugin is the recommended setup for Codex and Claude Code. It installs the MCP connection and workflow skills together. Use a direct MCP connection when your agent does not support the plugin or you only want the tools. Do not add the standalone connection if the Social Glass plugin is already installed in the same agent. The plugin already provides this MCP server.

​
Endpoint

Sign in with your Social Glass account when prompted. Test the connection with get_context.

​
Codex

Use a current Codex release that supports CIMD sign-in.

​
ChatGPT

Create a custom remote MCP connection in developer mode using the endpoint above. Choose OAuth authentication and CIMD in the advanced client registration settings, then sign in with your Social Glass account. Confirm that get_context works before removing an older connection. After server tools change, use Refresh in the connection settings to update the saved tool catalog. This is separate from renewing your sign-in session.

​
Claude Code

Start Claude Code and use /mcp to finish signing in. Previously registered clients can reconnect; a new registration needs approval as described below.

​
Other MCP clients

Social Glass uses Client ID Metadata Documents (CIMD) to recognize approved OAuth clients. ChatGPT and Codex are approved. For a new connection from another client, contact the Social Glass team to confirm support and register the client first. Existing client registrations remain valid; open Dynamic Client Registration (DCR) is disabled. Installing a plugin does not approve a new OAuth client. Add the endpoint as a remote HTTP MCP server and complete the OAuth flow. Every authenticated Social Glass user gets the same tool catalog; reads and writes follow your account’s role and organization access. Each tool enforces its own permissions. Hosted clients such as ChatGPT may request openid, profile, email, and offline_access. The first and last scopes support sign-in and session renewal; they do not expand access to Social Glass organizations or tools.

​
API keys

OAuth is preferred. If your client cannot retain OAuth sessions and your workspace has Clerk user API keys enabled, create a key with the social-glass:mcp scope and use it as the bearer token.

​
Troubleshooting

  • Unauthorized: reconnect and finish signing in.
  • Forbidden: confirm that your account has the role and organization access required by the tool. Signing in again does not grant missing permissions.
  • No authorization support: confirm the client is using the endpoint above rather than an old or local URL.
  • Invalid OAuth scope: use only openid, profile, email, and offline_access. Update the client and reconnect if it retains older scope settings.
  • Client registration rejected: confirm that the client uses CIMD and is approved by Social Glass. Contact the team for a new client registration.
  • Sign-in required again: reconnect. In Codex, restart the app if an existing task still uses an old credential after a successful sign-in. If this recurs, report the approximate time and error message; do not share tokens.
  • Duplicate Social Glass server: choose either the plugin or the standalone connection. To keep the plugin, remove only the manually added social-glass MCP entry, then start a new session. Check its source or scope before removing it; do not delete the plugin-provided server.
For native workflow guidance alongside the MCP, install the plugin or the skills-only package.