MCP Basics
Offers code linting functionality through the example of adding ESLint as a custom tool, allowing for automatic fixing of code quality issues.
Provides code formatting capabilities across all projects using Prettier, allowing automatic code styling with the 'mcp-formatter' tool.
Enables JavaScript to TypeScript migration using the 'mcp-translator' tool, helping convert existing JavaScript projects to TypeScript.
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@MCP Basics format the code in the src directory using prettier"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
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
Related MCP server: Shannon MCP
Installation
Clone this repository:
git clone https://github.com/caroline-davis/mcp-basics.git
cd mcp-basicsInstall dependencies:
npm installTest the server (optional):
node index.jsConfiguration
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.jsonand 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 fileDevelopment
Running the Server
node index.jsThe 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-migrateHow It Works
This MCP server:
Reads tool definitions from
tools.jsonExposes 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.jsonTest 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.
Available Tools
8 toolsmcp-bugfixC
Execute mcp-bugfix: npx eslint . --fix
Inputs: directory.
mcp-docsC
Execute mcp-docs: npx typedoc
Inputs: directory.
mcp-formatterC
Execute mcp-formatter: npx prettier --write .
Inputs: directory.
mcp-linterC
Execute mcp-linter: npx eslint .
Inputs: directory.
mcp-npm-auditC
Execute mcp-npm-audit: npm audit fix
Inputs: directory.
mcp-npm-outdatedC
Execute mcp-npm-outdated: npm outdated
Inputs: directory.
mcp-testgenC
Execute mcp-testgen: npx jest --init
Inputs: directory.
mcp-translatorD
Execute mcp-translator: npx ts-migrate
Inputs: directory.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
TDQS
Scored across 8 tools
Each tool has a clearly distinct purpose targeting specific development tasks: bug fixing, documentation generation, code formatting, linting, security auditing, dependency checking, test generation, and code translation. There is no overlap or ambiguity between these functions.
All tools follow a perfectly consistent 'mcp-' prefix + descriptive noun pattern (e.g., mcp-bugfix, mcp-docs, mcp-formatter). This creates a predictable and readable naming convention throughout the entire toolset.
With 8 tools, this server provides a well-scoped set of essential development utilities. Each tool earns its place by covering distinct aspects of the development workflow without being overwhelming or insufficient.
The toolset covers most core development tasks including code quality (linting, formatting), security (audit), dependencies (outdated), testing (testgen), and migration (translator). Minor gaps might include build/compilation tools or deployment utilities, but the current coverage is quite comprehensive for basic development workflows.
Maintenance
Related MCP Connectors
A Model Context Protocol server for Wix AI tools
A comprehensive Model Context Protocol (MCP) server that enables AI assistants to interact with yo…
Shared memory MCP server for Claude Code, Codex, Gemini CLI and Cursor. Cited, editable.
MCP server for progressive tool usage at any scale (see https://klavis.ai)
Related MCP Servers
- AlicenseBqualityCmaintenanceA server that bridges the Model Context Protocol (MCP) with SAP ABAP systems, allowing tools like Cline to retrieve ABAP source code, table structures, and other development artifacts.13272 npm206MIT
- FlicenseNot gradedqualityDmaintenanceA comprehensive Model Context Protocol server for Claude Code that provides programmatic management of Claude Code CLI operations through a multi-agent collaborative system.2-
- AlicenseAqualityDmaintenanceA Model Context Protocol server that provides persistent project context management for AI-assisted development, specifically designed for the Cline VSCode Extension.461MIT
- AlicenseAqualityDmaintenanceA Model Context Protocol server that provides development standards and best practices context to AI coding assistants, ensuring generated code adheres to team/project conventions.325 npm1MIT