Can my AI agent manually index new pages?

Yes. If you provide the AddSearch Secret Key, your agent can use the `index_document` tool. You can supply a URL and a JSON payload containing the title and body, and the agent will push it directly into your live search index without waiting for the web scraper.

What kind of search analytics can I retrieve?

Using the Secret Key, your agent can call two analytics endpoints: `stats_queries` (to see what users searched for, including top searches and zero-result queries) and `stats_clicks` (to see the click-through rates and popular URLs users navigated to from the search bar).

Do I need the Secret Key if I just want to test search queries?

No, if your goal is solely to run searches, paginate results, or check auto-suggestions, the public 'Site Key' is completely sufficient. The Secret Key is only required to list all documents, modify the index, and fetch analytics.

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

Name: AddSearch
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 AddSearch and 2,500+ MCP Servers from a single visual interface.

Download Free Open SourceNo signup required

Classic Setup·json

{
  "mcpServers": {
    "addsearch": {
      "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 AddSearch MCP Server

Connect your AddSearch account to your AI agent and turn your site's search index into an interactive, manageable database. Perfect for content teams and developers who need to audit site search performance without opening dashboards.

GitHub Copilot Agent mode brings AddSearch 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

Deep Search — Query your indexed content using natural language, apply custom field filters (e.g. "category=shoes"), or sort by custom variables
Document Management — List all indexed pages, import new content directly via JSON, or permanently delete outdated documents from the index
Search Analytics — Retrieve live statistics on user queries, identifying top searches, zero-result queries, and click-through rates
Frontend Emulation — Test your auto-suggestions and pagination just like a real user interacting with your search bar

The AddSearch 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 AddSearch to VS Code Copilot via MCP

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

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

Why Use VS Code Copilot with the AddSearch MCP Server

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

AddSearch + VS Code Copilot Use Cases

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

AddSearch MCP Tools for VS Code Copilot (10)

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

autosuggest

Get autocomplete suggestions

delete_document

Requires Secret Key. Permanently delete a document

index_document

Requires Secret Key. Add or update an indexed document

list_documents

Requires Secret Key. List all indexed documents

search_filtered

g., "category=shoes", "brand=nike"). Search indexed content by custom field

search_keyword

Search indexed content by keyword

search_pagination

Retrieve a specific page of search results

search_sorted

Search indexed content with custom sort

stats_clicks

Requires Secret Key. Retrieve click-through analytics

stats_queries

Requires Secret Key. Retrieve search query analytics

Example Prompts for AddSearch in VS Code Copilot

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

"Show me the top search queries that resulted in 0 hits."

"Search my site for "pricing updates" filtered by category=news."

"Test the auto-suggest for the prefix "shoe"."

Troubleshooting AddSearch MCP Server with VS Code Copilot

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

AddSearch + VS Code Copilot FAQ

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