Can my agent list all available search engines in Elastic?

Yes. Use the 'list_engines' tool. The agent iterates through your engine containers, managing logical indexing schemas and providing a complete map of your search spaces.

How do I index a batch of JSON documents via chat?

Use the 'index_documents' tool. Provide the engine name and a JSON array of your documents. The agent will command the bulk payload ingestion, triggering native pipeline mappings to store your data synchronously.

Can I check the search analytics for a specific engine through the agent?

Absolutely. The 'analytics' tool generates precise internal metric tracking for your engine. It will isolate usage insights and calculate click log data, allowing you to monitor search performance natively.

Elastic Enterprise Search MCP Server for VS Code Copilot 6 tools — connect in under 2 minutes

Name: Elastic Enterprise Search
Availability: InStock
Author: Vinkius

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

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

Download Free Open SourceNo signup required

Classic Setup·json

{
  "mcpServers": {
    "elastic-enterprise-search": {
      "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 Elastic Enterprise Search MCP Server

Connect your Elastic Enterprise Search deployment to any AI agent and take full control of your application search engines and workplace discovery through natural conversation.

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

What you can do

Engine Orchestration — Iterate through explicit engine containers managing logical indexing schemas and search spaces completely
Search & Discovery — Resolve semantic or literal queries enforcing deep contextual matches against structured enterprise scopes seamlessly
Document Indexing — Command explicit bulk payload ingestions triggering native pipeline mappings to store and update document collections synchronously
Metadata Inspection — Analyze specific global bounds fetching discrete index layouts and extracting linguistic configuration nodes cleanly
Analytics Auditing — Generate precise internal metric tracking isolating usage insights and calculating exact click log data to monitor performance
Catalog Retrieval — Extract explicitly attached REST arrays mapping exact document payloads fetching physical raw records flawlessly

The Elastic Enterprise Search MCP Server exposes 6 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 Elastic Enterprise Search to VS Code Copilot via MCP

Follow these steps to integrate the Elastic Enterprise Search 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 Elastic Enterprise Search

Ask Copilot: "Using Elastic Enterprise Search, help me..." — 6 tools available

Why Use VS Code Copilot with the Elastic Enterprise Search MCP Server

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

Elastic Enterprise Search + VS Code Copilot Use Cases

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

Elastic Enterprise Search MCP Tools for VS Code Copilot (6)

These 6 tools become available when you connect Elastic Enterprise Search to VS Code Copilot via MCP:

analytics

Get search analytics

get_engine

Get engine

index_documents

Index newly created JSON documents targeting specific schemas

list_documents

List indexed documents in an engine

list_engines

List engines

search

Search documents within an engine

Example Prompts for Elastic Enterprise Search in VS Code Copilot

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

"List all search engines in my Elastic deployment"

"Search for 'api integration' in engine 'help-center-docs'"

"Show me search analytics for engine 'e-commerce-products'"

Troubleshooting Elastic Enterprise Search MCP Server with VS Code Copilot

Common issues when connecting Elastic Enterprise Search 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.

Elastic Enterprise Search + VS Code Copilot FAQ

Common questions about integrating Elastic Enterprise Search 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.