Connect VS Code to SignWith (MCP)

VS Code reads MCP servers from .vscode/mcp.json in a workspace, or from your user configuration. Steps checked against the VS Code documentation on 1 October 2026.

One-click install

The button opens VS Code and adds SignWith. On first use, VS Code opens your browser to sign in to SignWith, where you choose Full access or View only.

Add it by hand

Run MCP: Add Server from the Command Palette, or add SignWith to .vscode/mcp.json:

{
  "servers": {
    "signwith": { "type": "http", "url": "https://app.signwith.co/mcp" }
  }
}

VS Code handles the OAuth sign-in in your browser the first time it connects.

Use an API key instead

To connect with an API key, add a header. With an inputs prompt, VS Code asks for the key the first time and keeps it out of the file:

{
  "inputs": [
    { "type": "promptString", "id": "signwith-api-key", "description": "SignWith API key", "password": true }
  ],
  "servers": {
    "signwith": {
      "type": "http",
      "url": "https://app.signwith.co/mcp",
      "headers": { "Authorization": "Bearer ${input:signwith-api-key}" }
    }
  }
}

Check it works

Run MCP: List Servers and check signwith is running. Then open the chat in agent mode and ask: "Which SignWith templates do I have?" Copilot asks before it runs a tool that sends or changes something.

Troubleshooting

• 401 unauthenticated with an API key: the key is wrong, revoked or expired. See authentication.
• It can read but not send: the connection is View only, or the key is read-only.

All tools and access rules are on the MCP overview and MCP tools.