MCP Server Enables Claude to Create and Run Custom Tools at Runtime

A developer has built an MCP server that allows Claude to create, update, and run new tools at runtime without requiring redeployment. Unlike standard MCP setups where tools are fixed at deploy time, this system enables dynamic tool creation.
Core Architecture
The server implements five core MCP tools:
- List Tools — returns available tools
- Get Tool — fetches full tool definition including code
- Create Tool — stores a new tool in a database registry
- Update Tool — modifies an existing tool
- Run Tool — executes any stored tool by name
Tool Execution Process
The Run Tool meta-tool works as follows:
- Looks up the requested tool in a MySQL table
- Fetches its code
- Passes parameters as context
- Runs it in a Deno subprocess with restricted permissions
- Returns the result
Sandbox Implementation
The developer evaluated Node VM, isolated-vm, and Docker before choosing Deno for sandboxing. Deno was selected because:
- Clean permission model with granular network/filesystem/subprocess control
- Native npm support
- TypeScript built-in
- ~50ms cold start vs 500ms+ for Docker
The sandbox uses these flags: --allow-net --deny-read --deny-write --deny-run --deny-ffi. This allows tool code to make HTTP requests and use npm packages, but prevents filesystem access or process spawning.
Tool Code Format
Tool code is JavaScript/TypeScript that receives a context object for parameters. Example from the source:
const response = await fetch(`https://api.example.com/${context.city}`);
const data = await response.json();
return { temp: data.temp, conditions: data.weather[0].description };
Self-Extension Capability
The system enables a self-extension loop: Claude identifies it needs a capability → creates the tool → uses it immediately → updates it if the result isn't right. This allows the system to become more capable over time without developer intervention.
The implementation is built on n8n as the MCP server with MySQL for tool storage and has been running in production for a few months.
📖 Read the full source: r/ClaudeAI
👀 See Also

LogClaw: Open-Source AI SRE for Auto-Ticketing from Logs
LogClaw is an open-source log intelligence platform that runs on Kubernetes, ingests logs via OpenTelemetry, detects anomalies using signal-based composite scoring, and automatically creates tickets with root cause analysis in about 90 seconds.

T9OS: An AI Orchestration System Built Entirely with Claude Code
An economics student built T9OS, a complete AI orchestration layer using Claude Code as the only programming tool. The system includes 18 production pipelines, a 12-state lifecycle engine, and 7 AI 'Guardians' that review every output.

Local Trello-Style Project Manager for OpenClaw Agents
A developer built a local Trello-like project management tool that runs on the same machine as their OpenClaw agent, storing cards as markdown files with YAML frontmatter. The system uses Node.js/Express for the API, React for the UI, and allows the AI agent to read/write files directly on the filesystem.

Persistent Memory for Claude: Local Stack with MCP, 39ms Retrieval, 82% Token Reduction
A developer built a persistent memory layer for Claude using local vector search (Qdrant + Qwen3) and MCP integration, achieving 82% token reduction, 39ms hot-path retrieval, and session crystallization via L4 nodes.