v0.3.0 — MCP Server
What's New
🔌 MCP Protocol Server (/mcp/)
Web2API now includes a built-in Model Context Protocol server. Every installed recipe endpoint is automatically exposed as a native MCP tool — no configuration needed.
Connect Claude Desktop:
{
"mcpServers": {
"web2api": {
"command": "npx",
"args": ["-y", "mcp-remote", "https://your-host/mcp/"]
}
}
}Connect Claude Code:
claude mcp add --transport http web2api https://your-host/mcp/- Each recipe endpoint registers as its own tool with typed parameters
- Tools rebuild automatically when recipes are installed, uninstalled, enabled, or disabled
- Streamable HTTP transport (stateless) — compatible with any MCP client
- Tool descriptions include the recipe site URL for better AI context
🛠 MCP HTTP Bridge (/mcp/tools)
A simpler REST bridge for non-MCP consumers (also powers the web UI):
GET /mcp/tools— list all tools as JSONPOST /mcp/tools/{name}— call a tool- Path-based filtering:
/mcp/only/brave-search/tools,/mcp/exclude/allenai/tools - Query-based filtering:
?only=slug1,slug2or?exclude=slug1 - New MCP Tools tab in the web UI with copy-ready URLs
📦 Other Changes
- Git tree hash update detection — managed recipes show update availability via git tree comparison
- Endpoint params declaration — recipe endpoints can declare custom query parameters with descriptions
- UI improvements — update/up-to-date badges moved to title row, cleaner badge alignment
- Docker — port binding defaults to localhost only (for reverse proxy setups)
🧹 Cleanup
- Shared MCP utilities extracted to
mcp_utils.py - Dead code removed, duplicate helpers consolidated
mcpandhttpxadded as dependencies
Full Changelog: v0.2.0...v0.3.0