unlob Docs
Console
Browse documentation

VS Code

For Copilot agent mode, with the key held as an input rather than a literal.

Configuration

VS Code reads .vscode/mcp.json for a workspace, or a user-level mcp.json reached through MCP: Open User Configuration in the command palette.

The workspace form, written so the file is safe to commit:

{
  "inputs": [
    {
      "type": "promptString",
      "id": "unlob-key",
      "description": "unlob API key",
      "password": true
    }
  ],
  "servers": {
    "unlob": {
      "type": "http",
      "url": "https://api.unlob.com/mcp",
      "headers": { "x-api-key": "${input:unlob-key}" }
    }
  }
}

inputs is the part worth using. VS Code prompts once, stores the value in its secret storage, and the file itself never contains a key — which is what makes a workspace config shareable.

Note the key is servers, not mcpServers. VS Code differs from most other clients here, and the wrong key produces a config that silently does nothing.

Start it

Open the Copilot chat view, switch to Agent mode, and open the tools picker. unlob should be listed with eleven tools. If the server has not started, the command palette has MCP: List Servers, from which you can start it and read its output.

Read the output when it fails

MCP: List Servers → unlob → Show Output is the fastest diagnosis available in any of these clients — it shows the actual transport errors rather than an empty tool list.

Using it

In agent mode, reference the tools directly:

#unlob find the most independently corroborated reporting on this, then summarise what the independent sources agree on.

Next