mcp-loader
# MCP Loader
Drop `.ts` or `.js` files in a folder. They become MCP tools. That's it.
## Quick Start
```typescript
// .claude/tool/math.ts
import { tool } from "mcp-loader";
export const add = tool({
description: "Add two numbers",
args: {
a: tool.schema.number(),
b: tool.schema.number(),
},
execute: ({ a, b }) => a + b,
});
```
Add to `.mcp.json`:
```json
{
"mcpServers": {
"tools": {
"command": "npx",
"args": ["mcp-loader", ".claude/tool"]
}
}
}
```
Done. Tools work in Claude.
## Install
Global install:
```bash
npm install -g mcp-loader
```
Or as a dev dependency:
```bash
npm install --save-dev mcp-loader
```
Or just use npx (no install):
```bash
npx mcp-loader .claude/tool
```
## Features
- **Hot reload** - Save file, tool updates (disable with `MCP_NO_HOT_RELOAD=true`)
- **Multiple tools per file** - Use named exports
- **MCP context** - Second param in execute has request info
- **TypeScript** - Full type safety
## Note
After changing tools, refresh with `/mcp` in Claude Code or restart Claude Desktop.
## License
MIT
TDQS
Scored across 16 tools
Several tools overlap in purpose, especially the generic verification tools 'test', 'demo', 'test_hotReloadTest', and 'test_liveTest', which an agent could easily confuse. The context/system information tools also blur together: 'system', 'session_info', and 'context-test_contextInfo' all report similar environment/context details.
Tool naming is mixed: math_, session_, and test_ prefixes are used, but there are bare names like 'demo', 'system', and 'test' alongside hyphens and camelCase in 'context-test_contextInfo' and 'test_hotReloadTest'. The overall pattern is readable but inconsistent.
At 16 tools, the set is borderline heavy for what appears to be a loader/test utility server. Many of the test/demo/verification tools could likely be consolidated without losing functionality.
The set covers math, session, context, echo, time, and reload-testing scenarios, but it feels like a grab bag rather than a complete domain surface. Notable gaps include no math subtraction, no negative/error-case testing tools, and redundant generic test tools that do not clearly advance the loader-testing purpose.