Connect Claude web or desktop to Semogram
Set up a Semogram workspace MCP connection, authenticate, verify evidence-backed reads, and manage access in Claude web or desktop.
The steps below follow the client’s documented MCP setup. This client connection has not yet been verified end to end against Semogram; complete the first-read checks below to verify your workspace access.
Install
Before you start
You need a Semogram account with access to the workspace and permission to read the records you intend to inspect. Connecting an assistant does not create a workspace, import data, or grant additional permissions.
In Semogram, open the workspace Settings and copy the URL from Connect an AI assistant. Use the copied UUID-based URL, not the workspace name, the homepage, or the sign-in URL. Its shape is:
https://platform.semogram.com/api/mcp/workspaces/<WORKSPACE_ID>Replace every placeholder below with that copied URL. The URL identifies the workspace; it does not contain an API key. This guide uses OAuth sign-in.
Add a custom connector
Open Claude's Connectors area. Current Claude web navigation uses Customize → Connectors; desktop versions may expose it through Settings. Choose the option to add a custom connector, give it the name Semogram, and paste the copied workspace URL as the remote MCP server URL.
Review the detected authentication settings and use the sign-in option for OAuth. Follow the connector flow to add and connect it. Semogram will ask you to sign in and approve the connection for the workspace. Return to Claude and confirm the connector is connected.
On a managed Claude organization, an owner may need to add the custom connector before members can connect. If the option is missing, check your organization's policy and Claude's current connector availability with your administrator.
This setup uses Claude's native remote connector. A local stdio configuration is a different connection method and is not part of this walkthrough.
Enable it in your conversation
Start a conversation and make the Semogram connector available using your client's connector controls. Name Semogram in your request so the assistant knows which service to use. If the connector is configured but no tools are available, check its connected status and the conversation's enabled tools.
Make your first read
Start a conversation with this request:
Use the Semogram MCP connection. Discover my available capabilities, confirm the workspace name and ID, and list the projects I can access. Do not change anything.
The assistant should use discover_capabilities, workspace_get, and
project_list. Check the returned workspace and choose the intended project.
Project tools on a workspace connection require its projectId; workspace
resources such as sources and uploads do not.
Then ask about a known record or published query:
Use Semogram to inspect the delivery query we published for this project. Explain its inputs and show the records and run references behind its result. If the query is missing, tell me rather than creating one.
Use your own query name. A successful connection does not mean that this example query exists or that an answer is correct. Compare the returned evidence with a record you recognize before expanding the task.
Manage the connection
Use Claude's Connectors area to disconnect or remove Semogram. If the wrong Semogram account was used, disconnect and authenticate again with the intended account. On a managed organization, a shared connector may be controlled by its owner. Removing a connector does not delete workspace data.
FAQ
What permissions does the assistant have?
Your current Semogram membership and permissions determine the available tools. Some mutations require confirmation or a current member approval under the operation's policy. An assistant's approval prompt and Semogram's server-side approval requirements are separate checks.
For long-running work, keep the returned job or operation ID and check its status. Saving a draft is not the same as executing it. The records returned by Semogram are sent to the assistant provider; use a client and account approved for the data your organization permits it to receive.
Why is the connection failing?
| What you see | What to check |
|---|---|
Sign-in is requested again or 401 missing_token | Authenticate again in the client. Verify that you are signing into Semogram, not only the assistant provider. |
404 workspace_not_found | Copy the URL again and check workspace membership for the account used during sign-in. A name or slug cannot replace the UUID. |
| The assistant responds without using Semogram | Name the connection explicitly, check that it is enabled, and ask it to discover the available tools. |
| Expected tools or projects are absent | Check your Semogram membership and permissions. Reconnecting does not grant access. |
405 when opening the MCP URL | A browser sends GET; Semogram's MCP endpoint accepts POST. Verify through the client rather than judging the browser response. |
429 | Wait for the Retry-After interval. See workspace consumer API limits. |
For API-key scopes, source-write restrictions, and the complete error list, use the MCP reference.
Where can I learn more?
Read MCP tools and permissions, or return to assistant setup. For client controls that vary by version, consult Claude custom connector documentation.