Bring Registry
to VS Code Copilot
Create your Vinkius account to connect Smithery to VS Code Copilot and start using all 11 AI tools in minutes. Fully managed, enterprise secure, and ready to use without writing a single line of code. No hosting, no server setup — just connect and start using.
GDPR Free for SubscribersCompatible with every major AI agent and IDE
Gemini
What is the Smithery MCP Server?
What you can do
Connect AI agents to the Smithery Registry for comprehensive MCP server discovery and management:
- 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
How it works
- Get your Smithery API key from smithery.ai/account/api-keys
- Ask your AI agent to search the registry, discover server capabilities, or create connections
- Natural language commands replace manual Smithery dashboard navigation
- Zero OAuth configuration — Smithery Connect handles tokens and sessions automatically
Who is this for?
Essential for AI application developers, agent architects, platform engineers, MCP server publishers, and enterprise AI teams building with the Model Context Protocol. Let AI agents discover relevant MCP servers, review their capabilities, create managed connections, and monitor usage analytics. Perfect for teams integrating multiple MCP servers who want to streamline server discovery, eliminate manual OAuth configuration, and enable AI-driven MCP ecosystem management.
Built-in capabilities (11)
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
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
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
Requires namespace and connection ID. Use this to review connection details or troubleshoot connectivity issues. Get detailed information about a specific MCP connection
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
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
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
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
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
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
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
Why VS Code Copilot?
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.
- —
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
Smithery in VS Code Copilot
Why run Smithery with Vinkius?
The Smithery connection runs on our fully managed, secure cloud infrastructure. We handle the hosting, maintenance, and security so you don't have to deal with servers or code. All 11 tools are ready to work instantly without any complex setup.
You stay in complete control of your data. Your AI only accesses the information you approve, keeping your sensitive passwords and private details completely safe. Plus, with automatic optimizations, your AI works faster and more efficiently.
* Every connection is hosted and maintained by Vinkius. We handle the security, updates, and infrastructure so you don't have to write code or manage servers. See our infrastructure
Over 4,000 integrations ready for AI agents
Explore a vast library of pre-built integrations, optimized and ready to deploy.
Connect securely in under 30 seconds
Generate tokens to authenticate and link external services in a single step.
Complete visibility into every agent action
Audit live requests, latency, success rates, and active security compliance policies.
Optimize spending and track token ROI
Analyze real-time token consumption and cost metrics detailed by connection.
Explore our live AI Agents Analytics dashboard to see it all working
This dashboard is included when you connect Smithery using Vinkius. You will never be left in the dark about what your AI agents are doing with your tools.
Smithery and 4,000+ other AI tools. No hosting, no code, ready to use.
Professionals who connect Smithery to VS Code Copilot through Vinkius don't need to write code, manage servers, or worry about security. Everything is pre-configured, secure, and runs automatically in the background.
Raw MCP | Vinkius | |
|---|---|---|
| Ready-to-use MCPs | Find and configure each manually | 4,000+ MCPs ready to use |
| Connection Setup | Manual coding & server setup | 1-click instant connection |
| Server Hosting | You host it yourself (needs 24/7 uptime) | 100% hosted & managed by Vinkius |
| Security & Privacy | Stored in plaintext config files | Bank-grade encrypted vault |
| Activity Visibility | Blind execution (no logs or tracking) | Live dashboard with real-time logs |
| Cost Control | Runaway AI token spend risk | Automatic budget limits |
| Revoking Access | Must delete files or code to stop | 1-click disconnect button |
How Vinkius secures
Smithery for VS Code Copilot
Every request between VS Code Copilot and Smithery is protected by our secure gateway. We automatically keep your sensitive data private, prevent unauthorized access, and let you disconnect instantly at any time.
Frequently asked questions
Do I need a Smithery account to use this MCP server?
Yes, you need a free Smithery account to generate an API key. Sign up at smithery.ai, then go to Account Settings > API Keys to create your key. The key gives access to the registry search, server details, and connection management features.
How does Smithery Connect handle OAuth for MCP servers?
Smithery Connect automatically handles OAuth flows, token refresh, and session management for MCP servers that require authentication. You don't need to configure redirect URIs, client IDs, or manage token expiration. Simply create a connection and Smithery manages the authentication lifecycle, providing your agents with seamless access.
Can I search for verified MCP servers only?
Yes! Use the verified filter in the search_servers tool by setting verified=true. This returns only servers that have been verified by Smithery, ensuring higher quality and security standards. Verified servers display a verification badge and have undergone additional review.
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.
MCP tools not available
Ensure you are in Agent mode in Copilot Chat. MCP tools only appear in Agent mode.
Explore More MCP Servers
View all →
Simplenote
8 toolsManage your Simplenote notes directly from your AI assistant. Create, search, edit, and organize plain-text notes without leaving the conversation.
Google Cloud Storage Bucket
4 toolsThis MCP does exactly one thing: it manages files in a single Google Cloud Storage Bucket. That's its only function, and nothing else. Incredible for giving your AI secure file storage.
Webex
10 toolsManage rooms, meetings, and collaboration workflows on Cisco Webex — the leading enterprise video conferencing platform.
Paperless-ngx
26 toolsManage your digital archive via Paperless-ngx — search documents, upload files, manage tags, and organize correspondents directly from any AI agent.