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

AI-Setup CLI Tool Automatically Generates AI Configuration Files for Local LLM Stacks
AI-Setup is a CLI tool that scans codebases and automatically generates AI configuration files like .cursorrules and claude.md. It detects your stack to eliminate manual rule writing for each new project.

Query Your Jira Sprint Via Claude MCP: Instant Status, Unassigned Issues, and Blocked Items
A Reddit user connected Jira to Claude via MCP, then asked plain‑language questions about their sprint and got instant clean tables — no clicking through boards.

Travel Hacking Toolkit: AI Skills and MCP Servers for Points and Miles Search
A GitHub repository provides 7 markdown skills and 6 MCP servers that teach Claude Code and OpenCode to search award flights across 25+ mileage programs, compare cash prices, pull loyalty balances, and find hotels and ferries. Setup requires cloning the repo and running setup.sh.

ZSE: Open-source LLM inference engine with 3.9-second cold starts
ZSE is an open-source LLM inference engine that reduces 32B model memory requirements from 64GB to 19.3GB VRAM and achieves 3.9-second cold starts for 7B models using a pre-quantized .zse format with memory-mapped weights.