How do I find my StarRocks FE Host and Port?

The FE Host is the IP address or domain of your StarRocks Frontend node. The default HTTP port is 8030. You can verify these in your deployment configuration or by contacting your administrator.

Can I execute DELETE or UPDATE queries through this server?

Yes. Use the `execute_query` tool. As long as your authenticated user has the necessary permissions in StarRocks, you can execute any valid SQL statement, including DDL and DML operations.

Is it possible to monitor cluster health through the agent?

Yes! Use the `get_cluster_info` and `list_nodes` tools to retrieve real-time status for all Frontend and Backend nodes, helping you identify offline or overloaded nodes instantly.

StarRocks MCP Server for VS Code Copilot 10 tools — connect in under 2 minutes

Name: StarRocks
Availability: InStock
Author: Vinkius

code.visualstudio.com/docs/copilot/chat/mcp-servers

Built by Vinkius GDPR 10 Tools IDE

GitHub Copilot in VS Code is the most widely adopted AI coding assistant, embedded directly into the world's most popular code editor. With MCP support in Agent mode, Copilot can access external data and APIs to generate context-aware code grounded in real-time information.

Get MCP Server for AI Agents

ASK AI ABOUT THIS MCP SERVER

Open in ChatGPT Open in Claude Open in Perplexity

Vinkius supports streamable HTTP and SSE.

RecommendedModern Approach — Zero Configuration

Vinkius Desktop App

The modern way to manage MCP Servers — no config files, no terminal commands. Install StarRocks and 2,500+ MCP Servers from a single visual interface.

Download Free Open SourceNo signup required

Classic Setup·json

{
  "mcpServers": {
    "starrocks": {
      "url": "https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp"
    }
  }
}

Fully ManagedVinkius Servers

60%Token savings

High SecurityEnterprise-grade

IAMAccess control

EU AI ActCompliant

DLPData protection

V8 IsolateSandboxed

Ed25519Audit chain

<40msKill switch

Stream every event to Splunk, Datadog, or your own webhook in real-time

* 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

About StarRocks MCP Server

Empower your AI agent to orchestrate your high-performance OLAP infrastructure with StarRocks, the leading distributed analytical database. By connecting StarRocks to your agent, you transform complex cluster auditing, schema management, and data querying into a natural conversation. Your agent can instantly list databases, retrieve table schemas, monitor backend nodes, and even execute complex SQL queries without you ever needing to open a SQL terminal or the StarRocks Manager. Whether you are conducting a data audit or monitoring real-time ingestion jobs, your agent acts as a real-time data reliability assistant, keeping your analytical platform accurate and your insights moving.

GitHub Copilot Agent mode brings StarRocks data directly into your VS Code workflow. With a project-scoped config, the entire team shares access to 10 tools. Copilot queries live data, generates typed code, and writes tests from actual API responses, all without leaving the editor.

What you can do

Database Orchestration — List all databases and retrieve detailed table schemas and structures.
Analytical Querying — Execute arbitrary SQL queries directly through the agent to retrieve real-time insights.
Cluster Monitoring — Browse status and metadata for Frontend (FE) and Backend (BE) nodes to audit health.
Ingestion Control — Monitor data load jobs and historical ingestion performance for your analytical pipelines.
Storage Insights — Retrieve disk usage and data size statistics across the entire distributed cluster.

The StarRocks MCP Server exposes 10 tools through the Vinkius. Connect it to VS Code Copilot in under two minutes — no API keys to rotate, no infrastructure to provision, no vendor lock-in. Your configuration, your data, your control.

How to Connect StarRocks to VS Code Copilot via MCP

Follow these steps to integrate the StarRocks MCP Server with VS Code Copilot.

Create MCP config

Create a .vscode/mcp.json file in your project root

Add the server config

Paste the JSON configuration above

Enable Agent mode

Open GitHub Copilot Chat and switch to Agent mode using the dropdown

Start using StarRocks

Ask Copilot: "Using StarRocks, help me...". 10 tools available

Why Use VS Code Copilot with the StarRocks MCP Server

GitHub Copilot for Visual Studio Code provides unique advantages when paired with StarRocks through the Model Context Protocol.

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

StarRocks + VS Code Copilot Use Cases

Practical scenarios where VS Code Copilot combined with the StarRocks MCP Server delivers measurable value.

Live API integration: Copilot can query an MCP server, inspect the response schema, and generate typed API client code in the same step

DevSecOps workflows: security teams can give developers access to domain intelligence tools directly in their editor for real-time vulnerability assessment during code review

Data pipeline development: Copilot fetches sample data via MCP and generates transformation scripts, validators, and test fixtures from actual API responses

Documentation generation: Copilot queries available tools and auto-generates README sections, API reference docs, and usage examples

StarRocks MCP Tools for VS Code Copilot (10)

These 10 tools become available when you connect StarRocks to VS Code Copilot via MCP:

execute_query

Execute arbitrary SQL query

get_cluster_info

Get frontend nodes info

get_storage_usage

Get data storage statistics

get_table_schema

Get table structure

list_databases

List all databases

list_jobs

List data load jobs

list_mvs

List materialized views

list_nodes

List backend nodes

list_tables

List tables in a database

list_views

List database views

Example Prompts for StarRocks in VS Code Copilot

Ready-to-use prompts you can give your VS Code Copilot agent to start working with StarRocks immediately.

"List all databases in my StarRocks cluster."

"Show me the average order value from the 'sales' table."

"Check for any offline backend nodes."

Troubleshooting StarRocks MCP Server with VS Code Copilot

Common issues when connecting StarRocks to VS Code Copilot through the Vinkius, and how to resolve them.

MCP tools not available

Ensure you are in Agent mode in Copilot Chat. MCP tools only appear in Agent mode.

StarRocks + VS Code Copilot FAQ

Common questions about integrating StarRocks MCP Server with VS Code Copilot.

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.