95+ tools — 5 production packages on PyPI

MCP tools that actually work.

A framework for building MCP servers. A proxy for running them.
And a growing catalog of production-ready tool packages.

Get Started Browse Tools →

$ pip install mcp-shell-tools
$ mcp-shell-tools
✓ MCP Shell Tools v4.0.1 — 26 tools, stdio ready

# Or use the proxy to load multiple plugins
$ mcp-proxy serve --config config.yaml
✓ Proxy ready: 5 plugins, 95 tools
✓ Shell (26) + Playwright (43) + WeKan (18) + Image (6) + Echo (2)

Architecture

Three components. One ecosystem.

Framework for building, Factory for assembling, Proxy for running.

Framework

mcp-server-framework

The library. Config loading, transport (stdio + HTTP), health endpoint, OAuth, plugin system.

$ pip install mcp-server-framework
# Your plugin:
def register(mcp, config):
    @mcp.tool()
    def my_tool(x: str):
        return f"done: {x}"

Factory

mcp-factory

Static plugin loading at startup. Pick your plugins, get a configured MCP server. CLI included.

$ mcp-factory \
    --plugins shell wekan \
    --http 12201

✓ 2 plugins, 44 tools
✓ HTTP on :12201

Proxy

mcp-proxy

Dynamic plugin loading at runtime. Load, unload, reload without restart. Management API. OAuth.

$ mcp-proxy serve --config proxy.yaml

✓ 5 plugins, 95 tools
✓ Dynamic dispatch enabled
✓ Management API on :12299

Tool Catalog

Production-ready MCP tools.

Each package works standalone or as a proxy plugin. Dual-use: MCP server + Python library.

mcp-shell-tools

26 tools — Filesystem, editor, search, shell, system. The workstation toolkit.

pip install mcp-shell-tools

mcp-playwright-tools

43 tools — Browser automation. Navigation, interaction, content extraction, semantic locators.

pip install mcp-playwright-tools

mcp-wekan-tools

18 tools — Kanban board management. Cards, lists, checklists, labels, swimlanes.

pip install mcp-wekan-tools

mcp-homematic-tools

60 tools — HomeMatic CCU3 smart home. Devices, channels, programs, climate, system variables.

pip install mcp-homematic-tools

mcp-image-tools

6 tools — Image processing. Read, resize, crop, convert, screenshot. Base64 output.

pip install mcp-image-tools

mcp-wikipedia-tools

6 tools — Wikipedia REST + MediaWiki API. Search, articles, summaries. Multilingual.

pip install mcp-wikipedia-tools

How it works

Every package follows the same pattern.

One interface. Standalone or plugin. MCP server or Python library.

Install

Each tool package is on PyPI. One pip install, ready to use.

$ pip install mcp-shell-tools
$ mcp-shell-tools
✓ 26 tools, stdio ready

Use as library

Every tool works as a Python function. No MCP needed.

from mcp_shell_tools.shell import tools

result = tools.file_read("/etc/hosts")
files = tools.glob_search("**/*.py")

Load in proxy

Combine tools from multiple packages. One server, many capabilities.

# proxy.yaml
autoload:
  - mcp_shell_tools.shell
  - mcp_playwright_tools.playwright
  - mcp_wekan_tools.wekan
  - mcp_image_tools.image

Plugin interface

Build your own in minutes.

One function. That's the entire plugin API.

      # my_tools/__init__.py

      def register(mcp, config: dict) -> None:

          """Register your tools as MCP tools."""

          @mcp.tool()

          def greet(name: str) -> str:

              """Say hello."""

              return f"Hello, {name}!"

          @mcp.tool()

          def add(a: int, b: int) -> str:

              """Add two numbers."""

              return str(a + b)

      # That's it. Works standalone and as proxy plugin.

FAQ

Common questions.

"What's the difference between Framework, Factory, and Proxy?"

Framework is the library you build on. Factory assembles plugins at startup. Proxy loads and unloads plugins at runtime. Most users need Framework + one tool package.

"Can I use a tool package without the framework?"

Yes. Every package exports pure Python functions. Import and call directly — no MCP, no server, no overhead.

"How do I build my own tool package?"

Implement register(mcp, config). That's the entire API. Add @mcp.tool() decorated functions inside. Your package works standalone and as a proxy plugin.

"Does it work with Claude Desktop / Claude Code?"

Yes. Every tool package runs as a stdio MCP server. Add it to your Claude Desktop config and it just works.