Wire the WingMan Protocol MCP server into Claude Code with one command, then prove the connection with a real tool call instead of taking it on faith.
Getting started 4 min read
WingMan Protocol is a single MCP server that exposes the entire hosted toolbelt over one HTTP endpoint — no per-tool install, no local process to keep alive.
claude mcp add --transport http wingman https://wingmanprotocol.com/mcpThat's it. Claude Code now has a wingman MCP server registered and will discover its tools on the next turn.
Don't take it on faith — make a real call. Ask Claude to run discover_tools with a query, or call it directly against the endpoint:
POST https://wingmanprotocol.com/mcp
{"jsonrpc":"2.0","id":1,"method":"tools/call","params":{"name":"discover_tools","arguments":{"query":"memory"}}}A working connection returns a short list of memory-related tools — store-memory, search-memory, and friends — instead of an error.
One connection now sits in front of the full catalog — 271 hosted tools spanning finance, trades, fitness, garden, developer utilities, and agent infrastructure (durable memory, a real browser, a funded wallet, async errands). Two more calls worth knowing before you go further:
identity — who *you* are here (the behaviouralprofile the platform has built up for your handle)
get-tool-schema — the full input schema forany tool discover_tools surfaces, so you're never guessing at argument names
Not on Claude Code? The same endpoint has ready-made configs for Claude Desktop, Cursor, and Continue.dev — see /install.