MCP Tools MCP Server

Local setup required. This server has to be cloned and prepared on your machine before you register it in Claude Code.
1

Set the server up locally

Run this once to clone and prepare the server before adding it to Claude Code.

Run in terminal
npm install
npm run build
2

Register it in Claude Code

After the local setup is done, run this command to point Claude Code at the built server.

Run in terminal
claude mcp add mcp-tools-ecbd -- node "<FULL_PATH_TO_MCP_TOOLS>/dist/index.js"

Replace <FULL_PATH_TO_MCP_TOOLS>/dist/index.js with the actual folder you prepared in step 1.

README.md

A local MCP server that exposes custom tools to Claude Desktop

šŸ› ļø MCP Tools

A local Model Context Protocol (MCP) server that exposes custom tools to Claude Desktop, enabling Claude to interact with your local environment directly.


šŸ“‹ Prerequisites

Before you begin, make sure you have the following installed:


šŸš€ Setup

1. Install Dependencies

Open a terminal, navigate to the project folder, and install:

cd 
npm install

2. Build the Project

Compile the TypeScript source:

npm run build

This will generate the compiled output in the dist/ folder (typically dist/index.js).

3. Configure Claude Desktop

Claude Desktop needs to know about your MCP server. Open (or create) the config file at:

%APPDATA%\Claude\claude_desktop_config.json

Tip: You can open this quickly by pressing Win + R, typing %APPDATA%\Claude, and pressing Enter.

Paste the following configuration:

{
  "mcpServers": {
    "mcp-tools": {
      "command": "node",
      "args": [
        "/dist/index.js"
      ]
    }
  }
}

Note: Replace `` with the actual path to your project folder (e.g. C:\\Users\\username\\Desktop\\mcp-tools). If you already have other MCP servers in your config, add "mcp-tools" as a new entry inside "mcpServers" — don't replace the entire file.

4. Restart Claude Desktop

Fully quit and relaunch Claude Desktop so it picks up the new config.

On Windows, make sure to right-click the system tray icon and choose Quit — just closing the window may leave it running in the background.


āœ… Verify the Connection

Once Claude Desktop restarts:

  1. Open a new chat
  2. Click the šŸ”§ Tools icon (hammer icon) in the bottom-left of the input box
  3. You should see your mcp-tools tools listed and available

If the tools don't appear, see Troubleshooting below.


šŸ’¬ Using the Tools

Once connected, you can ask Claude to use your tools naturally in conversation. For example:

"Can you use the mcp-tools to..."

Claude will automatically detect when a tool is relevant and invoke it on your behalf.


šŸ”„ Making Changes

If you modify any source files, rebuild and restart Claude Desktop:

npm run build

Then fully restart Claude Desktop for the changes to take effect.


šŸ› Troubleshooting

Tools not showing up in Claude Desktop

  • Double-check the path in claude_desktop_config.json matches your actual project location exactly (watch for single vs double backslashes)
  • Make sure npm run build completed without errors and dist/index.js exists
  • Fully quit and relaunch Claude Desktop (check system tray)
  • Open Claude Desktop logs via Help → Open Logs Folder to look for MCP errors

Build errors

# Make sure dependencies are installed
npm install

# Check your Node version (needs v18+)
node --version

Config file not found

If %APPDATA%\Claude\ doesn't exist yet, create the folder and the claude_desktop_config.json file manually.


šŸ“‚ Project Structure

mcp-tools/
ā”œā”€ā”€ src/
│   └── index.ts          # Main MCP server entry point
ā”œā”€ā”€ dist/                 # Compiled output (generated by build)
│   └── index.js
ā”œā”€ā”€ package.json
ā”œā”€ā”€ tsconfig.json
└── README.md

šŸ”Ø Build Commands Reference

Different ways to compile the TypeScript source depending on your setup:

# Recommended — bundle with esbuild (fastest, most compatible)
npx esbuild src/index.ts --bundle --platform=node --format=cjs --target=node18 --outfile=dist/index.js

# Alternative — compile with tsc directly
npx tsc index.ts --module commonjs --target ES2020 --esModuleInterop true --outDir dist

Useful References

https://simplescraper.io/blog/how-to-mcp#core-server-setup-with-express

https://vercel.com/kb/guide/mcp-server-with-weather-tool-express

šŸ“œ License

MIT

Configuration

claude_desktop_config.json
{"mcpServers": {"mcp-tools": {"command": "node", "args": ["<project-path>/dist/index.js"]}}}

Try it

→Can you use the mcp-tools to interact with my local environment?
→Use the mcp-tools to perform tasks in my local project folder.
→Help me manage my local files using the mcp-tools integration.

Frequently Asked Questions

What are the key features of MCP Tools?

Exposes custom TypeScript tools to Claude Desktop. Enables direct interaction with local environment. Provides a framework for building custom MCP tools. Supports local execution via Node.js.

What can I use MCP Tools for?

Developers building custom tools for Claude Desktop. Users needing to bridge Claude with local system tasks. Extending Claude's capabilities with custom TypeScript logic.

How do I install MCP Tools?

Install MCP Tools by running: npm install && npm run build

What MCP clients work with MCP Tools?

MCP Tools works with any MCP-compatible client including Claude Desktop, Claude Code, Cursor, and other editors with MCP support.

Turn this server into reusable context

Keep MCP Tools docs, env vars, and workflow notes in Conare so your agent carries them across sessions.

Need the old visual installer? Open Conare IDE.
Open Conare