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.
README Documentation
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
- Clone this repository:
git clone https://github.com/caroline-davis/mcp-basics.git
cd mcp-basics
- Install dependencies:
npm install
- 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:
- Edit
tools.json
and add your tool:
[
{
"name": "your-tool-name",
"tool": "your-command-here"
}
]
- 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:
- Reads tool definitions from
tools.json
- Exposes tools via the MCP protocol to Cline
- Executes commands in the specified directory when called
- 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
- Fork the repository
- Add your tools to
tools.json
- Test the changes
- 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.