GitHub Copilot

GitHub Copilot’s agent mode in VSCode supports MCP servers via a workspace or user-scoped .vscode/mcp.json (workspace) or the global VSCode mcp.json (user).

Setup

Get a Bearer token by visiting https://<your-workspace>.plaid.cloud/mcp/setup/token in a browser where you’re signed into PlaidCloud.

In VSCode, open the command palette and run MCP: Add Server, or create .vscode/mcp.json directly:

{
  "servers": {
    "plaidcloud": {
      "type": "http",
      "url": "https://<your-workspace>.plaid.cloud/mcp/",
      "headers": {
        "Authorization": "Bearer eyJhbGc…"
      }
    }
  }
}

Reload VSCode. Open the Copilot chat panel, switch the mode dropdown to Agent, and confirm the PlaidCloud tools appear in the tools list (typically shown as plaidcloud_*).

Usage

Ask Copilot to perform PlaidCloud operations directly:

“Find all workflows in project Q4 Forecast whose last run failed.”
“Show me the schema of table customers and suggest indexes.”
“Run the daily-load workflow and report the run status.”

Copilot picks the appropriate tool, executes it, and quotes results in its reply. For destructive operations (delete, organize, upsert without dry_run), it will typically ask for confirmation — review the planned action before approving.

Refreshing the Token

VSCode reads .vscode/mcp.json on startup and on file change. When the token expires, reload https://<your-workspace>.plaid.cloud/mcp/setup/token and overwrite the Authorization value — VSCode reloads the server automatically.

Restricting to Specific Tools

If you want to limit which PlaidCloud tools Copilot can call, use VSCode’s per-server tool allow-list (Settings → Copilot → MCP → server-specific tool selection). This is helpful for read-only sessions or for keeping mutating tools (*_upsert, *_run) gated behind explicit re-enable.