mcpkit

Development workflow

Move through the current mcpkit workflow from scaffold to release.

The most useful mental model is:

init → dev → test → validate → doctor → build → ship
  1. create the project with init
  2. run the generated project script or mcpkit dev
  3. use package scripts or mcpkit test
  4. run mcpkit validate for quick entry-file heuristics
  5. run mcpkit doctor when structure or environment feels off
  6. run mcpkit build
  7. use mcpkit ship when you are ready to publish

Why the docs emphasize this sequence

The product story is strongest when these commands are treated as one system instead of disconnected commands.

Guides

Task-oriented guides for working effectively with the current mcpkit workflow.

Testing MCP servers

Test generated projects using the scripts and commands the repository currently provides.

On this page

Recommended flowWhy the docs emphasize this sequence