MCP Basics

MCP Basics

A centralized Model Context Protocol server that provides common development tools (like formatting and translation) across all your Cline projects without needing to install them individually.

Category
Visit Server

Tools

mcp-translator

Execute mcp-translator: npx ts-migrate

mcp-formatter

Execute mcp-formatter: npx prettier --write .

README

MCP Basics

A centralized Model Context Protocol (MCP) server that provides common development tools across all your Cline projects. Instead of installing tools individually in each project, use this single MCP server to access formatting, translation, and other development utilities.

Features

  • mcp-formatter: Code formatting using Prettier (npx prettier --write .)
  • mcp-translator: JavaScript to TypeScript migration (npx ts-migrate)
  • Centralized tool management: Add tools once, use everywhere
  • Directory-specific execution: Run tools in any project directory

Installation

  1. Clone this repository:
git clone https://github.com/caroline-davis/mcp-basics.git
cd mcp-basics
  1. Install dependencies:
npm install
  1. Test the server (optional):
node index.js

Configuration

In VSCode, set up your MCP settings and add Local MCP Basics as a new entry inside the mcpServers object:

Configuration:

{
  "mcpServers": {
    "Local MCP Basics": {
      "disabled": false,
      "timeout": 60,
      "type": "stdio",
      "command": "node",
      "args": ["/path/to/mcp-basics/index.js"]
    }
  }
}

Replace /path/to/mcp-basics/index.js with the actual path to your cloned repository.

Usage

Once configured, you can use these tools in any Cline project by simply asking:

  • "Use the mcp-formatter tool to format this code"
  • "Run the mcp-translator tool to convert JavaScript to TypeScript"
  • "Format the code using prettier"

The tools will execute in your current project directory automatically.

Tool Parameters

Each tool accepts an optional directory parameter:

// Example: Format code in a specific directory
{
  "directory": "/path/to/specific/folder"
}

If no directory is specified, tools run in the current working directory.

Adding New Tools

To add new tools to the server:

  1. Edit tools.json and add your tool:
[
  {
    "name": "your-tool-name",
    "tool": "your-command-here"
  }
]
  1. The tool will automatically be available in Cline without restarting.

Example: Adding ESLint

[
  {
    "name": "mcp-translator",
    "tool": "npx ts-migrate"
  },
  {
    "name": "mcp-formatter", 
    "tool": "npx prettier --write ."
  },
  {
    "name": "mcp-linter",
    "tool": "npx eslint . --fix"
  }
]

Project Structure

mcp-basics/
├── index.js          # Main MCP server implementation
├── tools.json        # Tool configuration
├── package.json      # Node.js dependencies
├── .gitignore        # Git ignore rules
└── README.md         # This file

Development

Running the Server

node index.js

The server will start and listen for MCP protocol messages via stdio.

Testing Tools

You can test individual tools by calling them through the MCP protocol or by running the commands directly:

# Test formatter
npx prettier --write .

# Test translator
npx ts-migrate

How It Works

This MCP server:

  1. Reads tool definitions from tools.json
  2. Exposes tools via the MCP protocol to Cline
  3. Executes commands in the specified directory when called
  4. Returns results with stdout, stderr, and execution status

Requirements

  • Node.js (v14 or higher)
  • npm or yarn
  • Cline with MCP support

License

MIT License - feel free to use and modify as needed.

Contributing

  1. Fork the repository
  2. Add your tools to tools.json
  3. Test the changes
  4. Submit a pull request

Note: This server runs locally and doesn't require any external API keys or authentication. All tools execute using your local development environment.

Recommended Servers

playwright-mcp

playwright-mcp

A Model Context Protocol server that enables LLMs to interact with web pages through structured accessibility snapshots without requiring vision models or screenshots.

Official
Featured
TypeScript
Magic Component Platform (MCP)

Magic Component Platform (MCP)

An AI-powered tool that generates modern UI components from natural language descriptions, integrating with popular IDEs to streamline UI development workflow.

Official
Featured
Local
TypeScript
Audiense Insights MCP Server

Audiense Insights MCP Server

Enables interaction with Audiense Insights accounts via the Model Context Protocol, facilitating the extraction and analysis of marketing insights and audience data including demographics, behavior, and influencer engagement.

Official
Featured
Local
TypeScript
VeyraX MCP

VeyraX MCP

Single MCP tool to connect all your favorite tools: Gmail, Calendar and 40 more.

Official
Featured
Local
graphlit-mcp-server

graphlit-mcp-server

The Model Context Protocol (MCP) Server enables integration between MCP clients and the Graphlit service. Ingest anything from Slack to Gmail to podcast feeds, in addition to web crawling, into a Graphlit project - and then retrieve relevant contents from the MCP client.

Official
Featured
TypeScript
Kagi MCP Server

Kagi MCP Server

An MCP server that integrates Kagi search capabilities with Claude AI, enabling Claude to perform real-time web searches when answering questions that require up-to-date information.

Official
Featured
Python
E2B

E2B

Using MCP to run code via e2b.

Official
Featured
Neon Database

Neon Database

MCP server for interacting with Neon Management API and databases

Official
Featured
Exa Search

Exa Search

A Model Context Protocol (MCP) server lets AI assistants like Claude use the Exa AI Search API for web searches. This setup allows AI models to get real-time web information in a safe and controlled way.

Official
Featured
Qdrant Server

Qdrant Server

This repository is an example of how to create a MCP server for Qdrant, a vector search engine.

Official
Featured