beginner10-20 minutes

Step-by-step guide to integrate Smithery MCP server with Cline. Enhanced Cline functionality with Smithery integration.

Use Smithery MCP Server with Cline

Smithery is a MCP server that Gateway to 5000+ ready-made MCP servers with one-click deployment..

When integrated with Cline, you can:

  • Access Smithery functionality through Cline

This guide provides step-by-step instructions to set up Smithery in Cline, including configuration, examples, and troubleshooting.

What You'll Achieve

After completing this setup:

  • Smithery will be fully integrated and operational
  • You can use Smithery tools directly in Cline
  • All Smithery capabilities will be available for your workflows

Prerequisites

Before starting, ensure you have:

  • Cline installed and configured
  • Compatible operating system (Windows, macOS, Linux)

Installation

Step 1: Install Smithery

Configuration

Step 2: Configure Cline

  1. Open Cline settings
  2. Navigate to MCP server configuration
  3. Add Smithery server with appropriate settings
  4. Save and restart if needed

Examples

Once configured, you can use Smithery in Cline:

Testing Your Setup

  1. Launch Cline
  2. Verify Smithery is available in the tools list
  3. Test basic Smithery functionality

Troubleshooting

Common Issues

Extension Not Loading

Symptoms: Cline extension not appearing, Command palette empty

Cause: Extension installation or VS Code configuration issue

Solution:

  • Verify extension is properly installed via Extensions panel
  • Check VS Code version compatibility
  • Reload VS Code window or restart application
  • Check VS Code developer console for error messages

MCP Server Not Found

Symptoms: Server command not found, Tools unavailable in Cline

Cause: Server not installed or not accessible from VS Code

Solution:

  • Verify MCP server installation and PATH configuration
  • Test server command from VS Code integrated terminal
  • Use absolute path to server executable in configuration
  • Check server executable permissions

Configuration Not Applied

Symptoms: Settings changes not taking effect, Old configuration persisting

Cause: VS Code settings not reloaded or invalid configuration

Solution:

  • Reload VS Code window after configuration changes
  • Verify JSON syntax in settings.json is valid
  • Check Cline extension settings panel for errors
  • Review VS Code developer console for configuration warnings

Tool Execution Fails

Symptoms: MCP tools available but not working, Error during tool execution

Cause: Server configuration or environment issues

Solution:

  • Verify environment variables are set correctly
  • Check server logs for execution errors
  • Test server functionality outside of VS Code
  • Ensure all required dependencies are installed

Smithery not appearing in Cline

Symptoms: Server not listed, Tools not available

Cause: Configuration or installation issue

Solution:

  • Verify configuration syntax
  • Check Smithery installation
  • Restart Cline
  • Check logs for error messages

Next Steps

Now that Smithery is integrated with Cline:

  • Explore all Smithery capabilities through Cline
  • Check out other MCP servers that work with Cline
  • Join the MCP community for tips and support
  • Consider contributing to Smithery development

Need Help?

Related Resources

More Integrations

Explore other MCP servers that work with Cline

Need Help?

Join the MCP community for support and discussions