mcp-man
Postman for MCP servers — inspect tools, test live, browse 150+ servers
A local web UI and CLI for browsing, inspecting, and live-testing MCP servers -- the tools that connect AI assistants like Claude to databases, file systems, and APIs. Covers a registry of 156 servers with an auth setup wizard for 78 of them.
MCP (Model Context Protocol) is the standard way for AI assistants like Claude to connect to external tools, such as database clients, file systems, web search, and GitHub integrations. Each tool provider runs an MCP server, and there are hundreds of them available. The problem is that figuring out what any given server does, what parameters its tools accept, and what credentials it needs typically requires digging through GitHub READMEs and guessing.
mcp-man is a browser-based UI and command-line tool that solves this. Install it with npm, run mcp-man ui, and you get a local web interface with a registry of 156 MCP servers you can search by name or tag. Pick one, paste in the startup command, and mcp-man connects to it and shows you every tool it exposes, the full input schema for each tool, required parameters, and types. From the same UI you can call any tool live with JSON arguments and see the raw response, without needing to wire the server into an AI assistant first.
For servers that need API keys or other credentials, mcp-man includes an auth wizard that covers 78 servers and provides direct links to get each required token.
Everything in the UI is also available from the command line. You can search for servers, inspect a server's tools, and call a specific tool all from the terminal.
The project is open to adding new servers: edit the registry JSON file and open a pull request. If a server requires credentials, add an env array and the auth wizard picks it up automatically. The project is MIT licensed and written in TypeScript.
Where it fits
- Browse a registry of 156 MCP servers, inspect every tool's full input schema and parameter types, and call tools live with JSON arguments before wiring anything into an AI assistant.
- Use the auth wizard to get API keys and credentials for 78 MCP servers, with direct links to each provider's token page.
- Search MCP server tools and call them from the command line to quickly verify a server works without opening the web UI.
- Add a new MCP server to the shared registry by editing a JSON file and opening a pull request, including an env array so the auth wizard picks up any required credentials.