How do I get a Confluent Cloud API Key?

Log in to your Confluent Cloud dashboard. Go to **Cloud API Keys** under the administration menu. Click **Add key**, select the scope, and copy both the API Key and Secret.

What is an Environment in Confluent?

An Environment is a logical boundary containing clusters, schema registries, and connectors. You often need the Environment ID when querying specific resources.

Can the agent consume messages directly?

This integration focuses on control-plane tasks: managing topics, monitoring cluster status, and listing connectors. Direct message consumption from streams is not supported.

Confluent MCP Server for VS Code Copilot 7 tools — connect in under 2 minutes

Name: Confluent
Availability: InStock
Author: Vinkius

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

Built by Vinkius GDPR 7 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 Confluent and 2,500+ MCP Servers from a single visual interface.

Download Free Open SourceNo signup required

Classic Setup·json

{
  "mcpServers": {
    "confluent": {
      "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 Confluent MCP Server

Connect your AI to Confluent Cloud, the fully managed data streaming platform built on Apache Kafka.

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

What you can do

Cluster Monitoring — Check the health and status of your Kafka clusters, including node availability and CPU metrics.
Topic Management — List, create, and inspect topics, check partition health, and review recent event flows.
Environment Audits — Query environments to list active connectors and verify configuration states.

The Confluent MCP Server exposes 7 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 Confluent to VS Code Copilot via MCP

Follow these steps to integrate the Confluent 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 Confluent

Ask Copilot: "Using Confluent, help me...". 7 tools available

Why Use VS Code Copilot with the Confluent MCP Server

GitHub Copilot for Visual Studio Code provides unique advantages when paired with Confluent 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

Confluent + VS Code Copilot Use Cases

Practical scenarios where VS Code Copilot combined with the Confluent 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

Confluent MCP Tools for VS Code Copilot (7)

These 7 tools become available when you connect Confluent to VS Code Copilot via MCP:

get_cluster_details

Returns configuration, endpoint URLs, availability, and provisioning status. Retrieve detailed information about a specific Kafka cluster

list_cloud_api_keys

Retrieve API keys in the Confluent Cloud account

list_clusters

Returns all Kafka clusters with their status, cloud provider, and region. Retrieve Kafka clusters in a specific environment

list_connectors

Returns configured source and sink connectors with their status. Retrieve Kafka Connect connectors in an environment and cluster

list_environments

Use this to discover environment IDs needed for cluster and connector operations. Retrieve a list of Confluent Cloud environments

list_service_accounts

Useful for auditing programmatic access. Retrieve service accounts in the Confluent Cloud organization

list_topics

Returns all topics with partition count and replication configuration. Retrieve topics in a specific Kafka cluster

Example Prompts for Confluent in VS Code Copilot

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

"Check the health of the 'main-eu' Kafka cluster."

"List all active topics in the 'default_env' environment."

"Check the status of the 'mysql-source' connector."

Troubleshooting Confluent MCP Server with VS Code Copilot

Common issues when connecting Confluent 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.

Confluent + VS Code Copilot FAQ

Common questions about integrating Confluent 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.