The Semogram MCP
Choose a client, copy your Semogram workspace MCP URL, sign in, and verify your first evidence-backed read.
Use Semogram from an assistant your team already uses. MCP connects the assistant to your workspace tools, so you can inspect records, run published queries, review evidence, and request supported operations within your permissions.
Setup guides
| Client | Setup path |
|---|---|
| Claude Code | Add a remote HTTP server and authenticate |
| Claude web or desktop | Add a custom connector and sign in |
| Codex CLI | Configure the server and complete OAuth |
| Cursor | Add a remote server to Agent chat |
| Zed | Connect a remote context server |
| VS Code | Enable Semogram tools in Copilot |
| Windsurf / Cascade | Configure the remote workspace server |
| JetBrains AI Assistant | Connect with a local OAuth bridge |
JetBrains uses a local bridge; the other guides use native remote connections.
These client setup flows have not all been tested end to end against Semogram. Use the verification steps in each guide to confirm your connection before relying on it.
Each walkthrough covers prerequisites, connection, sign-in, a first read, connection management, and common errors. Other clients need remote MCP over Streamable HTTP and OAuth; check their transport and authentication support before using the connection reference.
Copy the URL for the right workspace
In Semogram, open workspace Settings and find Connect an AI assistant. Copy the displayed URL. It contains a workspace UUID and has this form:
https://platform.semogram.com/api/mcp/workspaces/<WORKSPACE_ID>For a project-only connection, use the documented project endpoint and its UUID. Do not substitute a workspace name, append a secret to the URL, or paste an API key into chat. Interactive setup uses OAuth; the URL alone does not grant access.
What a successful first connection looks like
Ask the assistant to discover its tools, confirm the workspace, and list your accessible projects. Match the returned name and ID to the workspace you intended. Then inspect a known record or published query and follow its evidence references.
A connected status proves the client reached the server. It does not prove that source data is present, that a query exists, or that the result is correct. Connect data first if your workspace is empty.
Keep access understandable
The assistant uses your current workspace membership and permissions. Review operations that change data, and check which server-side approvals apply. Data returned to the assistant is handled by its provider under your agreement with that provider. Removing a client connection does not delete your workspace.
The MCP reference explains tool discovery, API-key access, resource scopes, limits, and errors. Read a run when you need to verify what an operation produced.