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

​
Claude Code

Start Claude Code and use /mcp to finish signing in.

​
Other MCP clients

Add the endpoint as a remote HTTP MCP server and complete the OAuth flow. Eligible Social Glass users receive read access; write tools are available only to Social Glass admins.

​
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 can access the selected organization. Write tools also require an admin account.
  • No authorization support: confirm the client is using the endpoint above rather than an old or local URL.
  • 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.