Connect VS Code

Add Siglata to VS Code from the Command Palette or a .vscode/mcp.json entry, then use it from Copilot Chat agent mode.

VS Code adds MCP servers from the Command Palette or from a JSON file in your workspace. Either way you paste the Siglata address once and sign in in your browser. GitHub Copilot Chat then uses Siglata in agent mode. This path is installable / spec-compatible for v1 (Cursor and Codex are the proven clients).

Before You Start

A Siglata account. Sign in once at the Siglata Console. See Sign in.
VS Code with GitHub Copilot Chat, installed and up to date.

Steps

Open the Command Palette. Press Cmd+Shift+P on macOS or Ctrl+Shift+P on Windows and Linux.
Run MCP: Add Server.
Choose HTTP as the server type.
Paste the address.
```
https://www.siglata.com/v1/mcp
```
Name the server siglata, then choose whether to save it in your workspace or in your user settings.
Confirm the trust prompt. VS Code asks before it starts a server for the first time.
Sign in when VS Code offers it. Your browser opens on Siglata.
Sign in with your email magic link if you are not signed in already.
Pick the organization this connection may reach, then approve the permissions VS Code asked for.

Edit the File Instead

To write the entry yourself, create .vscode/mcp.json in your workspace with this content. VS Code uses a servers key here, not mcpServers.

{
  "servers": {
    "siglata": {
      "type": "http",
      "url": "https://www.siglata.com/v1/mcp"
    }
  }
}

Save the file, then click Start above the "siglata" entry.

You’re Done When

MCP: List Servers shows siglata as running.
The server lists exactly two tools, execute and search.
You open Copilot Chat in Agent mode, ask it to list the files in your Siglata organization, and it answers with your files.

Troubleshooting

The server does not start. Run MCP: List Servers, select siglata, and open its output log. The log names the failing step.
The sign-in window closed before it finished. Run MCP: List Servers, select siglata, and start it again. The authorization link expires after a few minutes.
Copilot ignores Siglata. Switch the chat to Agent mode, open the tools picker, and turn siglata on. Ask mode does not call MCP tools.
The agent reads the wrong organization. A connection is bound to the organization you picked while authorizing. Add a second entry named "siglata-acme" with the same address, and pick the other organization when it asks.
Calls fail with 401. Your grant ended, because the session was revoked or your membership changed. Restart the server and sign in again.

What the Agent Can Do

Copilot can list files and folders, upload new ones, download and read them, rename them, move them, send them to the trash, and restore them within 30 days. It can also read your organization’s profile, list members, invite people, and change roles. It never reaches past the organization you picked, and never past the permissions you approved.

The full operation list, with the permission each one needs, is in MCP.

For Agents

{
  "servers": {
    "siglata": {
      "type": "http",
      "url": "https://www.siglata.com/v1/mcp"
    }
  }
}

Workspace entries live in .vscode/mcp.json under a servers key. User-level entries live in the profile mcp.json that MCP: Open User Configuration opens.
Transport is Streamable HTTP at https://www.siglata.com/v1/mcp. Authorization is OAuth 2.0, and the client registers dynamically.
tools/list returns exactly two tools, execute and search. There is no context tool.
Management operations are CallScript functions called inside an execute script, not MCP tools. Call search to list the operations this grant may call.
Call principal_get inside an execute script to read the bound organizationId, plus userId, role, and scopes.
Other clients: Connect.