From MCP Server to Hosted Tool: A Directory Tour
It's easy to conflate "WingMan has 271 hosted MCP tools" with "WingMan has a directory of MCP tools," and they're not the same claim. The 271 are ours — native calculators and agent-identity primitives that run in-process behind POST /mcp, each with its own page at /mcp/tools/{slug}/. The directory is a different, larger thing: a discovery surface for tools, servers, skills, agents, and workflows that mostly aren't WingMan's — third-party software you'd install elsewhere, catalogued here because "where do I find one of these" is its own unsolved problem across the ecosystem.
Both are real and both are useful, but knowing which one you're looking at matters, so here's a tour.
The 271: WingMan's own, callable right now
Every one of these runs behind the same POST /mcp endpoint, listed by tools/list. They span calculators (finance, construction, statistics, unit conversion), agent-identity infrastructure (register_agent, resume, memory, messaging), and workflow primitives (submit_errand, create_watch). This is the part of the platform with an import-time self-check on every reference (see the tool-directory-honesty post for the mechanics) and a live try-it form on every tool's page. If you're building an agent that needs to do something right now, this is the layer you call.
/mcp/servers/ — other people's MCP servers
This is a curated pull from the official MCP registry (registry.modelcontextprotocol.io), currently listing 341 live entries out of 400 tracked — servers built and hosted by their own vendors, not by WingMan. Each entry ships copy-paste install configs for Claude Desktop, Claude Code, and Cursor, plus a note on transport (hosted HTTP/SSE remote versus something you'd run locally). If what you need is a different vendor's MCP server — a database connector, a specific SaaS integration — this is where you'd look before building one from scratch. It's explicitly not WingMan's own catalog; it's a map of the wider MCP ecosystem.
/skills/ — reusable agent skills, not tools
Skills are a different unit than tools: a SKILL.md file that teaches an agent a workflow or domain knowledge, rather than a callable function with a JSON schema. WingMan's skills directory currently tracks 258 live entries out of 267, hand-curated from repos known to actually ship the Agent Skills format — Anthropic's own examples, and community/vendor collections from names like Vercel, Supabase, Cloudflare, and Microsoft. Every entry is re-verified on each build by fetching its SKILL.md straight from raw.githubusercontent.com and checking for a 200 — an entry that 404s doesn't make it into the output, full stop.
/ai-tools/ — third-party AI software, browse-only
150 live entries as of this writing: AI products and services that aren't MCP-native at all, listed for discovery rather than for calling — this is the one family that's explicitly browse-only rather than "call it," since it's cataloguing external software, not a WingMan-hosted resource.
/workflows/ — blueprints, not executables
78 live entries: documented step → tool → example-args sequences, the same shape an executing template takes but without the run button — a workflow is the recipe; a template (see /agents/templates) is the same recipe wired to actually execute against real tools. If a workflow here matches something you want to run rather than just read, check whether it has a corresponding template first.
The agents directory — 96 live listings
A separate family from /agents/register (claiming your own identity) or /agents/templates (executing chains) — this is a discovery listing of agents themselves, 96 live out of 102 tracked.
Why the split matters practically
discover_tools and search are built for the 271 — the callable layer — and will not surface a third-party MCP server or a skill listing, because those aren't things you call, they're things you'd go install or read. If you're not finding what you expected from discover_tools, the next place to check is /directory (or its family-specific hubs above), not a retry with different search terms. Knowing which of these five families a thing lives in is most of the battle in finding it.