Skip to main content

​
MCP Setup

Watch the setup walkthrough first if you have not set up an MCP before:
If the video does not load, open it directly: Social Glass MCP setup walkthrough If you just want the easiest setup:
  1. Add this URL to your MCP client:
https://mcp.socialglass.ai/mcp
  1. Sign in with your Social Glass account when prompted.
  2. Test with get_viewer_context.
Write tools appear on the same MCP server for Social Glass admins.

​
Which URL should I use?

Most people should use: 
https://mcp.socialglass.ai/mcp
This is the canonical Social Glass MCP endpoint. Read and write tools live on the same server; write tools are role-gated and require a Social Glass admin account.

​
Before you start

Make sure:
  • you have a Social Glass account
  • your account is assigned to the right organization
  • you are a Social Glass admin if you are trying to use write tools

​
Fast setup

In most MCP clients, the flow is:
  1. Add a new remote MCP server.
  2. Paste the Social Glass MCP URL.
  3. Start the login flow.
  4. Sign in through Clerk.
  5. Return to the client and finish connecting.
After that, run: 
get_viewer_context
If that works, your setup is good. If you are using a repo-local Codex config, make sure it points directly at the live Social Glass MCP URL above, not at a local proxy.

​
Codex OAuth setup

For OAuth in Codex, add the remote server without a bearer-token env var, then start the MCP login flow: 
codex mcp add social-glass --url https://mcp.socialglass.ai/mcp
codex mcp login social-glass --scopes profile,email
If codex mcp get social-glass shows bearer_token_env_var, that server is configured for bearer-token auth. Remove and re-add it without --bearer-token-env-var if you want OAuth. Use Codex’s secure OAuth credential storage when possible: 
mcp_oauth_credentials_store = "keyring"
If OAuth gets stuck with a stale refresh token, use codex mcp logout social-glass and then run the login command again. You should not need to sign out of the Social Glass web app.

​
Claude Code OAuth setup

For Claude Code, add the same hosted MCP URL as a remote HTTP server: 
claude mcp add --transport http social-glass https://mcp.socialglass.ai/mcp
Then start Claude Code and use /mcp to complete OAuth if the server asks you to authenticate. Project-scoped .mcp.json servers may also need approval in Claude Code before they connect.

​
Durable API key setup

OAuth is the preferred setup when your MCP client handles refresh and reauth well. If your MCP client repeatedly loses OAuth state, Social Glass MCP also supports Clerk user API keys. API keys are long-lived bearer tokens tied to your Social Glass account and can be revoked from your account settings. Use this path only after Social Glass has enabled Clerk User API keys for your workspace:
  1. Open your Social Glass account profile from the avatar menu.
  2. Create a user API key for MCP access with the social-glass:mcp scope.
  3. Store the key in your MCP client as the bearer token for:
https://mcp.socialglass.ai/mcp
Write access still requires a Social Glass admin account. Organization API keys and user API keys without the social-glass:mcp scope are not supported for MCP access. For Codex, the bearer-token setup is: 
codex mcp add social-glass --url https://mcp.socialglass.ai/mcp --bearer-token-env-var SOCIAL_GLASS_MCP_BEARER_TOKEN
Then set SOCIAL_GLASS_MCP_BEARER_TOKEN in your local secret manager or shell environment before starting Codex. For Claude Code, prefer OAuth. If you must use a bearer token, pass it as an HTTP authorization header when adding the server: 
claude mcp add --transport http social-glass https://mcp.socialglass.ai/mcp \
  --header "Authorization: Bearer $SOCIAL_GLASS_MCP_BEARER_TOKEN"

​
Install as a Codex plugin

If your team uses Codex, you can install Social Glass as a plugin instead of adding the MCP URL by hand. Add the Social Glass marketplace source: 
codex plugin marketplace add Social-Glass-AI/social-glass-agent-plugins
codex plugin add social-glass@social-glass
Then:
  1. Restart Codex if needed.
  2. Open the social-glass marketplace.
  3. Install Social Glass.
  4. Complete the OAuth flow when prompted.
This is the best team path because people do not need a local clone of the repo just to use the plugin. The plugin is a wrapper around the hosted MCP endpoint; Social Glass instructions still come from the server through get_instructions.

​
Install as a Claude Code plugin

If your team uses Claude Code, install the same Social Glass plugin source: 
claude plugin marketplace add Social-Glass-AI/social-glass-agent-plugins
claude plugin install social-glass@social-glass
Start a new Claude Code session after installing. Use /mcp to authenticate if prompted.

​
Add as a Claude connector

For Claude chat or Claude Desktop, add the hosted MCP URL as a custom connector: 
https://mcp.socialglass.ai/mcp
This gives Claude the Social Glass MCP tools and server instructions. It does not install Codex or Claude Code plugin skills.

​
OAuth scopes

Social Glass MCP asks clients for the minimum Clerk scopes it needs:
  • profile
  • email
Social Glass narrows the MCP auth metadata to the scopes it actually needs. If your client asks for broader platform scopes such as openid, refresh the MCP login or verify that it is reading the current metadata.

​
Copy-paste prompt for Codex or Claude Code

If you want your coding agent to do the setup for you, give it this: 
Set up the Social Glass MCP for me.

Use this MCP URL:
https://mcp.socialglass.ai/mcp

If the client supports a remote MCP login flow, start that flow and have me sign in when needed.

After setup, verify the connection by:
1. listing the available MCP tools
2. calling get_viewer_context

If write access is needed later, tell me whether my account is a Social Glass admin and whether write tools are visible on the same server.

​
Write access

Write access uses the same MCP endpoint: 
https://mcp.socialglass.ai/mcp
Write tools only appear for Social Glass admins.

​
Common errors

​
Dynamic client registration not supported

Your MCP client is trying to register itself automatically, but it is talking to stale metadata or the wrong auth server. Social Glass supports dynamic client registration. What to do:
  • retry the login flow
  • make sure you are using the live Social Glass MCP URL
  • make sure your MCP client is not caching an older OAuth metadata response

​
No authorization support detected

Usually this means your MCP client is not talking to the live Social Glass OAuth MCP endpoint. Common causes:
  • you pointed the client at a local proxy instead of https://mcp.socialglass.ai/mcp
  • your repo-local MCP config still uses an older non-OAuth URL
  • your client is reading a different MCP config file than the one you updated

​
Unauthorized

Usually this means:
  • you are not signed in
  • your token expired
  • the login flow did not complete correctly

​
Forbidden

Usually this means:
  • your account is not allowed to access that organization
  • you tried to use a write tool without a Social Glass admin account

​
What works today

  • MCP read access is self-serve for eligible Social Glass users
  • write-capable MCP tools are available for Social Glass admins on the same server
  • dynamic client registration is enabled
  • Clerk user API keys are supported for durable bearer-token MCP auth when enabled for the workspace