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-loader list my available tools"
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.
Drop .ts or .js files in a folder. They become MCP tools. That's it.
// .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:
{
"mcpServers": {
"tools": {
"command": "npx",
"args": ["mcp-loader", ".claude/tool"]
}
}
}Done. Tools work in Claude.
Related MCP server: ts-mcp-meta
Global install:
npm install -g mcp-loaderOr as a dev dependency:
npm install --save-dev mcp-loaderOr just use npx (no install):
npx mcp-loader .claude/toolHot 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
After changing tools, refresh with /mcp in Claude Code or restart Claude Desktop.
MIT
Get detailed information about the MCP context
Inputs: no named parameters.
Track tool usage with context information
Inputs: action (required).
Execute something with timeout using AbortSignal from context
Inputs: delayMs (required).
Demo tool with enum and default value
Inputs: message (required), style, prefix.
Add two numbers
Inputs: a (required), b (required).
Divide two numbers
Inputs: a (required), b (required).
Multiply two numbers
Inputs: a (required), b (required).
Get information about the current Claude Code session
Inputs: no named parameters.
Send a notification through MCP
Inputs: message (required), level.
Make a request through MCP protocol
Inputs: method (required).
Get system information and MCP context
Inputs: no named parameters.
Test tool to verify MCP loader works
Inputs: message.
Echo back a message
Inputs: text (required).
Get current UTC time
Inputs: format.
Test that hot reload is working
Inputs: name.
Live reload test - added without restart
Inputs: no named parameters.
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
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.
Hot Module Reload (HMR) for Python with reactive programming and MCP tools
Build your own tools from chat: design, test and host them on a shareable MCP server URL.