MCP Tools Server

An extensible MCP server for Claude Desktop and Claude Code

Add any .js file to tools/ - it's auto-loaded. Zero boilerplate.

---

Overview

An MCP (Model Context Protocol) server that exposes tools to Claude through a plugin-style layout. New tools are added by creating files in the tools/ directory; the server loads them automatically at startup.

Built for use with Claude Desktop (chat) and Claude Code (IDE).

---

Features

• Auto-loading tools - Any .js file in tools/ with a register(server) export is loaded
• Standard MCP - Uses @modelcontextprotocol/sdk
• Schema validation - Tool inputs validated with Zod
• Extensible - Add tools without changing the main server code

---

Prerequisites

• Node.js 18+ (ES modules)
• npm or yarn

---

Quick Start

1. Clone and install

git clone https://github.com/ashish0553/mcp_server_tools_claude.git
cd mcp_server_tools_claude
npm install

2. Configure Claude

Claude Desktop (chat app)

• Windows: %APPDATA%\Claude\claude_desktop_config.json
• Windows (MS Store): %LOCALAPPDATA%\Packages\Claude_pzs8sxrjxfjjc\LocalCache\Roaming\Claude\claude_desktop_config.json
• macOS: ~/Library/Application Support/Claude/claude_desktop_config.json
• Linux: ~/.config/claude/claude_desktop_config.json

Claude Code (IDE)

• Config file: ~/.claude.json
• Windows: C:\Users\YourUsername\.claude.json

3. Add config JSON

{
  "mcpServers": {
    "mcp-server-test-1": {
      "command": "node",
      "args": ["/absolute/path/to/mcp_server_tools_claude/index.js"],
      "description": "Custom MCP tools"
    }
  }
}

Replace /absolute/path/to/ with your actual project path (e.g. D:/xampp/htdocs/mcp_server_tools_claude/index.js on Windows).

4. Restart Claude

Restart Claude so it picks up the new MCP server.

---

Built-in Tools

• convertCurrency - Convert between currencies (USD, INR, EUR, etc.) using live exchange rates

---

Adding Your Own Tools

1. Create tools/myTool.js
2. Export a register(server) function that registers the tool
3. Restart the MCP server

Template:

import { z } from "zod";

export function register(server) {
  server.registerTool("myTool", {
    description: "What your tool does",
    inputSchema: z.object({
      param: z.string().describe("A parameter"),
    }),
  }, async ({ param }) => {
    return {
      content: [{ type: "text", text: `Result for ${param}` }],
    };
  });
}

Tool contract:

• register(server) - Required export; receives the MCP server instance
• description - Shown to the model
• inputSchema - Zod schema for arguments
• Return format: { content: [{ type: "text", text: "..." }] } or { content: [...], isError: true }

See tools/convertCurrency.js for a full example.

---

Project Structure

mcp_server_tools_claude/
|-- index.js              (entry point, loads tools and starts server)
|-- tools/
|   |-- README.md
|   |-- convertCurrency.js
|-- package.json
|-- README.md

---

Debugging

• Logs (Claude Desktop): .../Claude/logs/mcp-server-mcp-server-test-1.log
• Check server start: Run node index.js - you should see [mcp] Loaded tool: convertCurrency.js
• Use stderr for logs - MCP uses stdout for JSON-RPC; use console.error for debugging

---

Development

node index.js
npm install

---

Contributing

Contributions are welcome. Please open an issue or PR.

1. Fork the repo
2. Create a branch: git checkout -b feature/my-tool
3. Add your tool in tools/
4. Commit: git commit -m 'Add my tool'
5. Push: git push origin feature/my-tool
6. Open a Pull Request

---

License

ISC