The Data-Bridge (TDB) for VS Code
Connect VS Code's agent mode to a TDB server. Your
agent gets governed, read-only SQL over your data, and every tool call is recorded in
TDB's audit log.
The extension does one job: it registers your TDB server as an MCP server in VS Code.
It keeps your API key in VS Code's encrypted secret storage, so you never write a key
into mcp.json or your settings.
Requirements
- VS Code 1.101 or later, desktop. VS Code for the Web (vscode.dev) is not
supported: the browser sends an
Origin header, and TDB refuses cross-origin
requests.
- A running TDB server and an API key for it.
- Community edition (free): one CSV source, the
query_source tool. See the
quickstart.
- Enterprise: databases and seven tools. Every key sees all seven; a key with
an
allowed_tools list is refused when it calls a tool outside that list.
- An agent that can use MCP tools, such as GitHub Copilot in agent mode.
Getting started
- Open the Command Palette and run TDB: Connect to Server.
- Enter the server's base URL, for example
http://localhost:8000.
- Enter your API key. It is stored in VS Code's secret storage.
- In agent mode, open the tools picker. The Data-Bridge (TDB) is listed with its
tools. Ask your agent a question about your data.
The status bar shows the connection: the server's version when it is reachable, a
warning when it is not, and a plug when you are not connected. Click it to connect
or change servers.
Commands
| Command |
What it does |
| TDB: Connect to Server |
Sets the server URL and API key. Run it again to switch servers. |
| TDB: Disconnect |
Deletes the stored key and clears the URL. The server disappears from VS Code. |
Settings
| Setting |
Default |
Description |
tdb.serverUrl |
"" |
Base URL of the TDB server. Set by TDB: Connect to Server. |
The API key is never a setting.
What the extension sends
- To your TDB server only:
Authorization: Bearer <your key> on every MCP request.
MCP-Protocol-Version: 2025-11-25 on every request. VS Code agrees this version
with the server when it connects, but does not repeat it on later requests. Without
the header, TDB would answer those requests with an older protocol, so your agent
would miss tool titles, read-only hints and structured results. If VS Code starts
sending its own header, its value is used instead.
- An unauthenticated
GET / to your server every 60 seconds, for the status bar.
The extension collects no telemetry. TDB's audit log records each call with
mcp_client set to Visual Studio Code/<version>. See
audit logging.
OAuth (Enterprise)
This extension authenticates with an API key or a JWT. To sign in with OAuth 2.1
instead, configure VS Code's own MCP client in mcp.json. It runs the OAuth flow
itself. See IDE setup.
Other editors
The extension is also published on Open VSX.
It needs an editor that supports VS Code's MCP server provider API. For any other
MCP client, configure it by hand as described in
IDE setup.
License
The extension is MIT licensed. TDB Community is AGPLv3. TDB Enterprise is commercial.