diy-tools-mcp and mcp-cli
These are complements: the DIY tools server provides dynamic tool creation capabilities that can be exposed and invoked through the mcpc CLI client, enabling users to define and execute custom functions via command-line MCP interactions.
About diy-tools-mcp
hesreallyhim/diy-tools-mcp
An MCP server that allows users to dynamically add custom tools/functions at runtime
Supports multi-language function execution (Python, JavaScript, Bash, Ruby, TypeScript) with file-based or inline code definitions, automatic JSON Schema validation, and persistent tool storage. Built on the Model Context Protocol with timeout protection and comprehensive security checks for sandbox isolation. Integrates seamlessly with Claude and other MCP clients through stdio transport, enabling runtime tool extension without server restarts.
About mcp-cli
apify/mcp-cli
mcpc is a CLI client for MCP. It supports persistent sessions, stdio/HTTP, OAuth 2.1, JSON output for code mode, proxy for AI sandboxes, and much more.
Exposes full MCP protocol capabilities—instructions, resources, prompts, async tasks, and dynamic server discovery—through intuitive shell commands and JSON output for scripting. Built as a lightweight stdio/HTTP client with persistent session management and an embedded proxy server for secure AI sandboxing. Supports OAuth 2.1 credential storage via OS keychain, x402 micropayment protocol integration, and config-file references for local MCP servers.
Related comparisons
Scores updated daily from GitHub, PyPI, and npm data. How scores work