Until now, the CLI only scaffolded Streamable HTTP servers (remote, cloud-deployable). But a lot of people build local MCP servers for Claude Desktop and other local clients — and stdio is the right transport for that.
So I added it.
npx @agentailor/create-mcp-server --name=my-server --stdio
That's it. No HTTP server, no port, no Dockerfile. Just a clean stdio server ready to connect to any local MCP client.
You can also combine it with FastMCP:
npx @agentailor/create-mcp-server --name=my-server --stdio --framework=fastmcp
What the CLI now supports:
→ HTTP (Streamable) or stdio transport
→ Official MCP SDK or FastMCP
→ Stateless or stateful server modes
→ Optional OAuth (SDK + HTTP)
→ npm, pnpm, or yarn
📚 Learning Resources
If you're getting started with MCP servers, here are the guides I've written:
→ Build your first MCP server in 5 minutes
https://blog.agentailor.com/posts/create-your-first-mcp-server-in-5-minutes
→ Secure your MCP server with OAuth (Keycloak)
https://blog.agentailor.com/posts/oauth-for-mcp-servers-practical-guide-keycloak
→ Getting started with FastMCP
https://blog.agentailor.com/posts/getting-started-with-fastmcp
→ OAuth for MCP Clients (Next.js + LangGraph.js)
https://blog.agentailor.com/posts/mcp-client-oauth-nextjs-langgraph
Star the repo if this is useful 🙏
https://github.com/agentailor/create-mcp-server
Top comments (0)