التعرّف على mcp CLI

The mcp command-line tool came with the [cli] extra. It's how you run, test, and ship servers without writing extra glue code. 🛠️

The CLI centers on three verbs: dev, install, and run. Each handles a different stage of working with your server, from testing to shipping.

Because the tool lives in your project's environment, you call it with uv run. That guarantees the right Python and packages are used every time.

The fastest way to try a server is mcp dev. It launches your server and opens the MCP Inspector so you can poke at it interactively.

With mcp dev you see your tools and resources live, call them by hand, and watch responses. It's the tightest possible feedback loop. 🔍

When a server is ready for daily use, mcp install wires it straight into Claude Desktop's config so the app loads it on startup.

Pass a friendly label with the --name flag so it's easy to spot inside Claude. A clear name beats a raw file path every time.

The plain mcp run command executes a server directly, no Inspector attached. It's the simple way to launch a FastMCP server for a client.

Reach for mcp dev while building and debugging, and switch to mcp run once you just need the server up. Same server, different intent.

Forgot an option? Every command supports --help, which prints its arguments and usage. It's the quickest reference you'll always have on hand.

Together these commands cover the lifecycle: test with dev, ship with install, launch with run. You rarely need anything else to operate a server. 🔄

You want to test a new server and click through its tools interactively.

You can now dev to test, install to add a server to Claude, and run to launch it. Three commands give you full control of your server. 🎉