Compatible with every major AI agent and IDE
What is the QuestDB (Time-Series) MCP Server?
Connect your QuestDB instance to any AI agent to perform high-speed time-series analysis and data management using natural language.
What you can do
- SQL Execution — Run complex SQL queries, DDL, and DML operations optimized for time-series data.
- High-Speed Ingestion — Import tabular data (CSV/TSV) directly into tables with automatic schema creation and partitioning.
- Data Export — Extract large datasets in CSV or Parquet formats for external analysis or reporting.
- Health Monitoring — Instantly check server status and version information to ensure your database is operational.
How it works
- Subscribe to this server
- Provide your QuestDB URL and optional credentials (Username/Password or Token)
- Start querying and managing your time-series data from Claude, Cursor, or any MCP-compatible client
Who is this for?
- Data Engineers — Quickly inspect table schemas, run migrations, and verify data ingestion pipelines.
- Analysts — Perform ad-hoc time-series analysis and export results without writing complex scripts.
- DevOps Teams — Monitor database health and perform maintenance tasks through a conversational interface.
Built-in capabilities (4)
Use this for standard SELECT, INSERT, or DDL operations. Execute SQL statements (queries, DDL, DML) on QuestDB
Useful for extracting large datasets. Export query results as CSV or Parquet
Automatically creates tables and columns if they do not exist. Import tabular data (CSV, TSV) into a table
Health check and version information
Why VS Code Copilot?
GitHub Copilot Agent mode brings QuestDB (Time-Series) data directly into your VS Code workflow. With a project-scoped config, the entire team shares access to 4 tools. Copilot queries live data, generates typed code, and writes tests from actual API responses, all without leaving the editor.
- —
VS Code is used by over 70% of developers. adding MCP tools to Copilot means your team can leverage external data without leaving their primary editor
- —
Project-scoped MCP configs (
.vscode/mcp.json) let you commit server configurations to your repository, ensuring the entire team shares the same tool access - —
Copilot's Agent mode integrates MCP tools seamlessly with file editing, terminal commands, and workspace search in a single agentic loop
- —
GitHub's enterprise compliance and audit features extend to MCP tool usage, providing visibility into how AI interacts with external services
QuestDB (Time-Series) in VS Code Copilot
QuestDB (Time-Series) and 4,000+ other MCP servers. One platform. One governance layer.
Teams that connect QuestDB (Time-Series) to VS Code Copilot through Vinkius don't need to source, host, or maintain individual MCP servers. Every tool call runs inside a hardened runtime with credential isolation, DLP, and a signed audit chain.
Raw MCP | Vinkius | |
|---|---|---|
| Server catalog | Find and host yourself | 4,000+ managed |
| Infrastructure | Self-hosted | Sandboxed V8 isolates |
| Credential handling | Plaintext in config | Vault + runtime injection |
| Data loss prevention | None | Configurable DLP policies |
| Kill switch | None | Global instant shutdown |
| Financial circuit breakers | None | Per-server limits + alerts |
| Audit trail | None | Ed25519 signed logs |
| SIEM log streaming | None | Splunk, Datadog, Webhook |
| Honeytokens | None | Canary alerts on leak |
| Custom domains | Not applicable | DNS challenge verified |
| GDPR compliance | Manual effort | Automated purge + export |
Why teams choose Vinkius for QuestDB (Time-Series) in VS Code Copilot
The QuestDB (Time-Series) MCP Server runs on Vinkius-managed infrastructure inside AWS — a purpose-built runtime with per-request V8 isolates, Ed25519 signed audit chains, and sub-40ms cold starts. All 4 tools execute in hardened sandboxes optimized for native MCP execution.
Your AI agents in VS Code Copilot only access the data you authorize, with DLP that blocks sensitive information from ever reaching the model, kill switch for instant shutdown, and up to 60% token savings. Enterprise-grade infrastructure, zero maintenance.

* Every MCP server runs on Vinkius-managed infrastructure inside AWS - a purpose-built runtime with per-request V8 isolates, Ed25519 signed audit chains, and sub-40ms cold starts optimized for native MCP execution. See our infrastructure
How Vinkius secures
QuestDB (Time-Series) for VS Code Copilot
Every tool call from VS Code Copilot to the QuestDB (Time-Series) MCP Server is protected by DLP redaction, cryptographic audit chains, V8 sandbox isolation, kill switch, and financial circuit breakers.
Frequently asked questions
Can I execute standard SQL queries and DDL commands like creating tables?
Yes! Use the execute_sql tool to run any valid QuestDB SQL statement, including SELECT, INSERT, and table definitions. You can also include parameters like explain to see the execution plan.
How do I import a CSV file into a new or existing table?
Use the import_data tool. Provide the target table name and the raw CSV data. The tool can automatically create the table structure and handle partitioning if specified.
Is there a way to export large query results for use in other tools?
Absolutely. The export_data tool allows you to run a query and receive the output in CSV or Parquet format, which is ideal for large-scale data extraction.
Which VS Code version supports MCP?
MCP support requires VS Code 1.99 or later with the GitHub Copilot extension. Ensure both are updated to the latest version. Older versions of Copilot may not expose the Agent mode toggle.
How do I switch to Agent mode?
Open the Copilot Chat panel and look for two mode options: "Ask" and "Agent". Click "Agent" to enable autonomous tool calling. In Ask mode, Copilot provides conversational answers but cannot invoke MCP tools.
Can I restrict which MCP tools Copilot can access?
Yes. VS Code shows a tool consent dialog before any MCP tool is invoked for the first time. You can also configure tool access policies at the organization level through GitHub Copilot settings.
Does MCP work in VS Code Remote or Codespaces?
Yes. MCP servers configured via .vscode/mcp.json work in Remote SSH, WSL, and GitHub Codespaces environments. The MCP connection is established from the remote host, so ensure the server URL is accessible from that environment.
MCP tools not available
Ensure you are in Agent mode in Copilot Chat. MCP tools only appear in Agent mode.
Explore More MCP Servers
View all →
Dotdigital
10 toolsEquip your AI agent to manage email campaigns, track contacts, and monitor marketing automation via the Dotdigital API.

Together AI
7 toolsGenerate code, evaluate embeddings, and deploy open-source LLMs instantly from your local agent via Together AI's infrastructure.

FDA (openFDA)
12 toolsAccess public health data via openFDA — search drug labeling, monitor adverse events, and track food recalls directly through your AI agent.

Laravel Forge
9 toolsManage Laravel Forge servers, orchestrate site deployments, and query databases directly from your AI agent.
