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 Cursor?
Cursor's Agent mode turns QuestDB (Time-Series) into an in-editor superpower. Ask Cursor to generate code using live data from QuestDB (Time-Series) and it fetches, processes, and writes. all in a single agentic loop. 4 tools appear alongside file editing and terminal access, creating a unified development environment grounded in real-time information.
- —
Agent mode turns Cursor into an autonomous coding assistant that can read files, run commands, and call MCP tools without switching context
- —
Cursor's Composer feature can generate entire files using real-time data fetched through MCP. no copy-pasting from external dashboards
- —
MCP tools appear alongside built-in tools like file reading and terminal access, creating a unified agentic environment
- —
VS Code extension compatibility means your existing workflow, keybindings, and extensions all work alongside MCP tools
QuestDB (Time-Series) in Cursor
QuestDB (Time-Series) and 4,000+ other MCP servers. One platform. One governance layer.
Teams that connect QuestDB (Time-Series) to Cursor 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 Cursor
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 Cursor 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 Cursor
Every tool call from Cursor 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.
What is Agent mode and why does it matter for MCP?
Agent mode is Cursor's autonomous execution mode where the AI can perform multi-step tasks: reading files, editing code, running terminal commands, and calling MCP tools. Without Agent mode, Cursor operates in a simpler ask-and-answer mode that doesn't support tool calling. Always ensure you're in Agent mode when working with MCP servers.
Where does Cursor store MCP configuration?
Cursor looks for MCP server configurations in a mcp.json file. You can configure servers at the project level (.cursor/mcp.json in your project root) or globally (~/.cursor/mcp.json). Project-level configs take precedence.
Can Cursor use MCP tools in inline edits?
No. MCP tools are only available in Agent mode through the chat panel. Inline completions and Tab suggestions do not trigger MCP tool calls. This is by design. tool calls require user visibility and approval.
How do I verify MCP tools are loaded?
Open Settings → Features → MCP and look for your server name. A green indicator means the server is connected. You can also check Agent mode's available tools by clicking the tools dropdown in the chat panel.
Tools not appearing in Cursor
Ensure you are in Agent mode (not Ask mode). MCP tools only work in Agent mode.
Server shows as disconnected
Check Settings → Features → MCP and verify the server status. Try clicking the refresh button.
Explore More MCP Servers
View all →
NVIDIA NIM
8 toolsMLOps proxy unifying explicitly local hardware limits extracting telemetry across active NVIDIA AI containers.

ManoMano (Home Improvement Marketplace)
11 toolsManage your ManoMano seller account — update offer prices, track orders, and audit fulfillment stock.

Stirling PDF
11 toolsManage PDF documents via Stirling PDF — add watermarks, convert images to PDF, sign documents with certificates, and monitor server metrics directly.

ON24
12 toolsHost enterprise webinars and virtual events that generate pipeline with interactive engagement tools and first-party intent data.
