2,500+ MCP servers ready to use
Vinkius

Smithery MCP Server for Cline 11 tools — connect in under 2 minutes

Built by Vinkius GDPR 11 Tools IDE

Cline is an autonomous AI coding agent inside VS Code that plans, executes, and iterates on tasks. Wire Smithery through Vinkius and Cline gains direct access to every tool. from data retrieval to workflow automation. without leaving the terminal.

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:

Cline operates autonomously inside VS Code. it reads your codebase, plans a strategy, and executes multi-step tasks including Smithery tool calls without waiting for prompts between steps. Connect 11 tools through Vinkius and Cline can fetch data, generate code, and commit changes in a single autonomous run.

  • 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 Cline 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 Cline via MCP

Follow these steps to integrate the Smithery MCP Server with Cline.

01

Open Cline MCP Settings

Click the MCP Servers icon in the Cline sidebar panel

02

Add remote server

Click "Add MCP Server" and paste the configuration above

03

Enable the server

Toggle the server switch to ON

04

Start using Smithery

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

Why Use Cline with the Smithery MCP Server

Cline provides unique advantages when paired with Smithery through the Model Context Protocol.

01

Cline operates autonomously. it reads your codebase, plans a strategy, and executes multi-step tasks including MCP tool calls without step-by-step prompts

02

Runs inside VS Code, so you get MCP tool access alongside your existing extensions, terminal, and version control in a single window

03

Cline can create, edit, and delete files based on MCP tool responses, enabling end-to-end automation from data retrieval to code generation

04

Transparent execution: every tool call and file change is shown in Cline's activity log for full visibility and approval before committing

Smithery + Cline Use Cases

Practical scenarios where Cline combined with the Smithery MCP Server delivers measurable value.

01

Autonomous feature building: tell Cline to fetch data from Smithery and scaffold a complete module with types, handlers, and tests

02

Codebase refactoring: use Smithery tools to validate live data while Cline restructures your code to match updated schemas

03

Automated testing: Cline fetches real responses from Smithery and generates snapshot tests or mocks based on actual payloads

04

Incident response: query Smithery for real-time status and let Cline generate hotfix patches based on the findings

Smithery MCP Tools for Cline (11)

These 11 tools become available when you connect Smithery to Cline 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 Cline

Ready-to-use prompts you can give your Cline 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 Cline

Common issues when connecting Smithery to Cline through the Vinkius, and how to resolve them.

01

Server shows error in sidebar

Click the server name to see logs. Verify the URL and token are correct.

Smithery + Cline FAQ

Common questions about integrating Smithery MCP Server with Cline.

01

How does Cline connect to MCP servers?

Cline reads MCP server configurations from its settings panel in VS Code. Add the server URL and Cline discovers all available tools on initialization.
02

Can Cline run MCP tools without approval?

By default, Cline asks for confirmation before executing tool calls. You can configure auto-approval rules for trusted servers in the settings.
03

Does Cline support multiple MCP servers at once?

Yes. Configure as many servers as needed. Cline can use tools from different servers within the same autonomous task execution.

Connect Smithery to Cline

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