Skip to main content

​
MCP Setup

Social Glass exposes a remote MCP server so approved AI clients can read from the Social Glass workspace and, for approved write clients, update the same objects our in-app chat agent works with.

​
Very simple mental model

There are two MCP endpoints:
  • https://www.socialglass.ai/api/mcp Read-only. Safe default.
  • https://www.socialglass.ai/api/mcp-write Broader write access. Restricted to approved OAuth clients.
Both endpoints use Clerk OAuth for sign-in. Social Glass then applies its own user and organization authorization rules after the user is authenticated.

​
What is supported today

As of April 19, 2026, Social Glass supports approved or preconfigured OAuth clients for MCP access. Today that means:
  • read-only MCP access is available for approved clients
  • write-capable MCP access is available only for specifically approved clients
  • fully self-serve dynamic client registration is not enabled yet
If your MCP client tries to self-register and fails with Dynamic client registration not supported, that is expected with the current setup.

​
Prerequisites

Before connecting an MCP client, make sure:
  • you have a valid Social Glass user account
  • your user is assigned to the correct organization in Social Glass
  • your MCP client has been approved for the endpoint you want to use
For write access, both of these must be true:
  • your Social Glass user has permission to modify data in that organization
  • your OAuth client has been explicitly approved for https://www.socialglass.ai/api/mcp-write

​
Endpoint choices

​
Read-only MCP

Use this when you want to:
  • inspect your viewer context
  • list organizations you can access
  • search zeitlets
  • open a specific zeitlet
  • list dashboards
Endpoint: 
https://www.socialglass.ai/api/mcp

​
Write-capable MCP

Use this only when you also need to:
  • create or update insights
  • create or update personas
  • create or update projects
  • create or update dashboard report content
Endpoint: 
https://www.socialglass.ai/api/mcp-write

​
Generic setup steps

The exact UI varies by client, but the flow is the same:
  1. Add the Social Glass MCP server URL to your client.
  2. Choose the read-only endpoint unless you specifically need writes.
  3. Start the login flow.
  4. Sign in through Clerk with your Social Glass account.
  5. Return to the MCP client and complete the connection.
After login, Social Glass still checks:
  • which user you are
  • which organization you belong to
  • whether you are allowed to use the write endpoint

​
Example MCP URLs

Read-only: 
https://www.socialglass.ai/api/mcp
Write-capable: 
https://www.socialglass.ai/api/mcp-write

​
What the client should expect

On a successful connection:
  • the client should be able to list MCP tools
  • a simple call like get_viewer_context should succeed
On the write endpoint:
  • the connection may still authenticate successfully
  • but write operations will be rejected unless the OAuth client is on the approved allowlist

​
Troubleshooting

​
Dynamic client registration not supported

Your MCP client is trying to create its own OAuth app automatically. Social Glass does not currently allow that flow. What to do:
  • use an approved or preconfigured Social Glass OAuth client
  • or contact the Social Glass team to get the client approved

​
Unauthorized

This usually means one of these:
  • you are not signed in
  • the token expired
  • the client did not complete the Clerk OAuth flow correctly

​
Forbidden

This usually means one of these:
  • your Social Glass user is not allowed to access that organization
  • you tried to use the write endpoint with an unapproved OAuth client
  • your Social Glass user does not have permission for the requested operation
After connecting, run a simple read call first:
  • get_viewer_context
Then, if needed:
  • search_zeitlets
  • get_zeitlet
  • list_dashboards
Only move to the write endpoint after the read-only flow is working.