Connect VS Code to Semogram

Use VS Code to inspect your Semogram workspace from the conversation where you already work. For example, compare a delivery summary with its underlying orders and receipts, or inspect a published workflow before deciding to run it.

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 a workspace, an installed client with MCP tools enabled, and a model that can call tools. Your organization may control which external servers and assistant providers you can use.

In Semogram, open workspace Settings → Connect an AI assistant and copy the workspace MCP URL. Its form is:

https://platform.semogram.com/api/mcp/workspaces/<WORKSPACE_ID>

Use the copied URL wherever the example says <YOUR_WORKSPACE_MCP_URL>. A workspace name cannot replace its UUID. The URL identifies the workspace and does not grant access by itself. Connecting an assistant does not import records or create a project; connect your data if there is nothing to inspect yet.

Add the connection and sign in

Run MCP: Add Server from the Command Palette and choose a remote HTTP server. Enter the workspace URL and the name semogram. For a personal connection, choose the user configuration; for a team connection, choose the workspace scope.

For the .vscode/mcp.json format, the entry is:

{
  "servers": {
    "semogram": {
      "type": "http",
      "url": "<YOUR_WORKSPACE_MCP_URL>"
    }
  }
}

Merge this into existing configuration. VS Code also supports portable .mcp.json configuration with a top-level mcpServers object; do not mix the two schemas. Start Semogram through MCP: List Servers, review any trust prompt, and complete Semogram sign-in when requested. Open Copilot chat in Agent mode and enable the Semogram tools in the tools picker.

Make your first read

In Copilot Agent chat, start with a read-only request:

Use Semogram to discover the available capabilities, confirm the workspace name and ID, and list the projects I can access. Do not change anything.

The assistant should call discover_capabilities, workspace_get, and project_list. Compare the returned workspace with the one you intended and choose a project. Workspace-scoped resources do not take a projectId; project operations on this workspace connection do.

Then use a record or query that actually exists in that project:

Inspect our published delivery summary query. Explain its inputs, show its latest run, and identify the order and receipt records behind the result. If it does not exist, say so rather than creating a replacement.

Replace the example query name with yours. Inspect the tool calls and returned references, rather than accepting a conversational answer as proof of access. A tool list confirms discovery, not that your data is complete or the answer is correct. Read a run to inspect the result.

Manage the connection

Run MCP: List Servers, select semogram, and use its stop, restart, disable, or output actions. Remove the matching entry to uninstall the connection. An organization policy or restricted workspace can prevent a configured server from starting; check that before changing the URL.

Removing a client configuration does not delete Semogram data. Each additional workspace should have its own clearly named connection and its own copied URL.

FAQ

What permissions does the assistant have?

An OAuth connection uses the signed-in account’s current workspace permissions. A missing project or tool can reflect those permissions. An assistant approval prompt does not replace Semogram’s server-side operation approvals.

Ask to inspect drafts before executing workflows or changing records. Keep the returned job or operation ID when work runs asynchronously and check its final status. Data returned to the client is handled by its assistant provider; use your organization’s approved account and data-sharing policy.

Source-write tools have additional API-key requirements described in the MCP reference. They are not enabled simply by reconnecting an OAuth client.

Why is the connection failing?

For client-specific failures, inspect MCP: List Servers → Show Output. Before sharing logs, remove tokens, private records, and personal information. See MCP troubleshooting for server error details.

Where can I learn more?

Return to choose your assistant, review tools and scopes, or consult the official VS Code MCP documentation for controls that vary by version.