2,500+ MCP servers ready to use
Vinkius

Smithery MCP Server for VS Code Copilot 11 tools — connect in under 2 minutes

Built by Vinkius GDPR 11 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.

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

Vinkius Desktop InterfaceVinkius Desktop InterfaceVinkius Desktop InterfaceVinkius Desktop Interface
Download Free Open SourceNo signup required
Classic Setup·json
{
  "mcpServers": {
    "smithery": {
      "url": "https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp"
    }
  }
}
Smithery
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 Smithery MCP Server

What you can do

Connect AI agents to the Smithery Registry for comprehensive MCP server discovery and management:

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

  • Search MCP servers — find servers by name, description, or tags with semantic search
  • Get server details — review metadata, verification status, and user counts
  • Discover tools — list all tools (functions) exposed by any registered MCP server
  • Discover resources — list all data resources available from MCP servers
  • Discover prompts — list all prompt templates exposed by MCP servers
  • Create connections — connect to MCP servers via Smithery Connect with automatic OAuth handling
  • Manage connections — list, inspect, and remove MCP server connections
  • Generate service tokens — create scoped, time-limited tokens for frontend/agent access
  • View analytics — monitor server usage, adoption trends, and performance metrics

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

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

01

Create MCP config

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

02

Add the server config

Paste the JSON configuration above

03

Enable Agent mode

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

04

Start using Smithery

Ask Copilot: "Using Smithery, help me...". 11 tools available

Why Use VS Code Copilot with the Smithery MCP Server

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

01

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

02

Project-scoped MCP configs (`.vscode/mcp.json`) let you commit server configurations to your repository, ensuring the entire team shares the same tool access

03

Copilot's Agent mode integrates MCP tools seamlessly with file editing, terminal commands, and workspace search in a single agentic loop

04

GitHub's enterprise compliance and audit features extend to MCP tool usage, providing visibility into how AI interacts with external services

Smithery + VS Code Copilot Use Cases

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

01

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

02

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

03

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

04

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

Smithery MCP Tools for VS Code Copilot (11)

These 11 tools become available when you connect Smithery to VS Code Copilot via MCP:

01

create_connection

Smithery handles OAuth, tokens, and sessions automatically. Requires the server namespace and connection configuration (mcpUrl, optional headers, metadata). Returns the connection ID, status, and server info. Use this to integrate MCP servers into your applications without managing authentication complexity. Create a new connection to an MCP server via Smithery Connect

02

create_service_token

The token has limited permissions defined by the policy (namespaces, resources, operations, metadata, TTL). Returns the token string. Use this to provide secure, time-limited access to MCP servers without exposing your main API key. Generate a scoped service token for frontend/agent access to MCP servers

03

delete_connection

This action cannot be undone. Requires namespace and connection ID. Use this to clean up unused connections or revoke access. Remove an MCP server connection

04

get_connection

Requires namespace and connection ID. Use this to review connection details or troubleshoot connectivity issues. Get detailed information about a specific MCP connection

05

get_server_analytics

Requires the server qualified name. Use this to monitor server adoption, identify usage trends, or troubleshoot performance issues. Get usage analytics for a specific MCP server

06

get_server_details

Requires the qualified name (e.g., "smithery/hello-world" or "github/github") from search_servers results. Use this to review server capabilities before connecting. Get detailed information about a specific MCP server from the Smithery registry

07

get_server_prompts

Returns prompt names, descriptions, and argument definitions. Requires the server qualified name. Use this to discover reusable prompt workflows available from the server. List all prompt templates exposed by a specific MCP server

08

get_server_resources

Returns resource URIs, names, descriptions, and MIME types. Requires the server qualified name. Use this to understand what data the server provides read access to. List all resources exposed by a specific MCP server

09

get_server_tools

Returns tool names, descriptions, input schemas, and annotations. Requires the server qualified name. Use this to understand what actions the server can perform before connecting it to your agents. List all tools exposed by a specific MCP server

10

list_connections

Returns connection IDs, names, statuses, creation dates, and metadata. Use this to audit which connections are active, review connection configurations, or identify unused connections. List all connections for a specific MCP server namespace

11

search_servers

Returns matching servers with qualified names, descriptions, verification status, user counts, and deployment info. Use optional filters to narrow by namespace, verified status, or deployment state. Results include pagination metadata. Use this as the first step to discover available MCP servers before connecting or installing them. Search the Smithery registry for MCP servers by name, description, or tags

Example Prompts for Smithery in VS Code Copilot

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

01

"Search for verified GitHub-related MCP servers"

02

"Show me all tools exposed by the Stripe MCP server"

03

"Create a connection to the Slack MCP server for my workspace"

Troubleshooting Smithery MCP Server with VS Code Copilot

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

01

MCP tools not available

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

Smithery + VS Code Copilot FAQ

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

01

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.
02

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.
03

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.
04

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.

Connect Smithery to VS Code Copilot

Get your token, paste the configuration, and start using 11 tools in under 2 minutes. No API key management needed.