The homepage sells one SDK and one cloud, with "npx create-mcpfy-app" and "mcpfy dev" as the quick start. A developer who clicks "Docs" lands on "Create a Server", which describes the earlier product: find "Generate MCP" in the sidebar and paste cURL commands. The SDK getting-started page installs with npm install and never mentions create-mcpfy-app, and deploying from GitHub is a separate guide. The path from "this looks good" to a first deployed server breaks on the first page, and npm shows it: create-mcpfy-app had 42 downloads in the last 30 days.
First action
Make the SDK quick start the docs home page and move the cURL guide under "From an API".
How to measure it
Sign-up to first deploy
- Now
- –
- Target
- 40%
- By
- 60 days
Steps
Write the quick start
Scaffold, run, push, deploy, inspect, connect, with expected output for each step.
Developer Advocate 2 days
Reorder the docs
Quick start first; cURL and OpenAPI under "From an API".
Developer Advocate 1 day
Match the homepage
Same commands and wording on the homepage, SDK page and README.
Growth Engineer 1 day
Instrument it
Events for scaffold, first deploy and first tool call.
Founding Engineer 2 days
Test it cold
Five developers new to Mcpfy run it while you watch.
Growth Engineer 1 week
Fix the drop-offs
Rewrite or automate the step where most people stop.
Founding Engineer 1 week
Report weekly
Funnel from sign-up to first deploy.
Growth Engineer weekly
Why it works
Replace the docs landing page with one quick start that matches the homepage: npx create-mcpfy-app, mcpfy dev, push to GitHub, get a live MCP URL, open it in the Cloud Inspector, then connect it to Claude or ChatGPT. Keep the OpenAPI and cURL route as a second path ("Already have an API?"). Put a time on each step, show the expected terminal output, and end with "Your server is live" plus a link to publishing. Track each step (scaffold, first deploy, first tool call in the Inspector) so you can see where people stop.
For a developer tool, the first docs page is the onboarding. When it matches what the homepage promised, more visitors reach a live server, and a live server is the point where free users start to upgrade.
Ready to use
ChecklistFive-minute quick start
[ ] npx create-mcpfy-app my-server [ ] cd my-server && mcpfy dev (expect: ready on :4141, N tools registered) [ ] git push to a connected GitHub repo [ ] Copy the live MCP URL from the dashboard [ ] Call one tool in the Cloud Inspector [ ] Add the URL as a connector in Claude or ChatGPT [ ] Next: publishing checks and submission pack
Risks and how to handle them
Breaking links to the old guide
Keep the cURL page at its URL, linked from the new quick start.
Quick start drifts from the CLI
Run it in CI on each SDK release.
Evidence
- Your websiteHomepage: "Build and deploy MCP servers and apps. One SDK, one cloud, every client. Ship to ChatGPT and Claude, run for your own agents, and see every tool call in production." Quick start shown as "npx create-mcpfy-app" then "mcpfy dev ready on :4141"; three ways in: from a Git repository, from an OpenAPI spec, or from a template; calls to action "Start deploying" and "Book a call".Source
- Your docsThe "Docs" link opens "Create a Server - MCPfy AI", the getting-started page, which describes the earlier flow: log in, "look for the 'Generate MCP' option in the sidebar", "Paste the cURL commands of the APIs that you need to add as tools", test and deploy. The SDK getting-started page installs with "npm install mcpfy-sdk" and never mentions create-mcpfy-app or mcpfy dev; deploy-from-GitHub is a separate guide.Source
- Your docsThe docs index (llms.txt) lists 22 pages: Create a Server, Support, one GitHub deployment guide, 12 SDK pages (server, client, tools, prompts, resources, widgets, React widgets, authentication, Claude skill), 4 Pulse SDK telemetry pages for TypeScript and Python servers ("built on mcpfy-sdk or the official @modelcontextprotocol/sdk", "FastMCP or the official mcp SDK") and 3 API reference pages. There are no guides for publishing to the ChatGPT Apps store or Claude connectors, cross-client tests or the Inspector.Source
- Open source and npmGitHub mcpfyy/mcpfy ("A SDK for building MCP tools, prompts, resources, and widgets", MIT, created July 2026): 23 stars, 8 forks, 7 open issues, last push September 15, 2026. Mcpfy/skills: 6 stars. npm last 30 days (to November 3, 2026): mcpfy-sdk 48 downloads, create-mcpfy-app 42; latest SDK 0.4.0 published September 15, 2026.Source