myvibekit-mcp
v1.0.1
Published
MCP Server for My Vibe Kit — access UI templates, dashboards, and landing pages from Cursor, Claude Desktop, and other AI coding tools.
Maintainers
Readme
My Vibe Kit MCP Server
MCP server that exposes My Vibe Kit templates to Cursor (and other MCP clients) via get_kits, search_kits, and get_kit_prompt.
Setup
- Install dependencies:
npm install - Build:
npm run build - Configure in Cursor: Settings → MCP → Add server with command:
node /path/to/mvk/mcp-server/dist/index.js - Optional: set
MVK_API_URLandMVK_API_KEYin your MCP server env for premium kit prompts.
Server ID in Cursor (important for AI/agents)
Cursor registers MCP servers with an internal identifier that may differ from the display name:
- User-level install (Settings → MCP): the server is often registered as
user-my-vibe-kit. - Workspace-level install (project MCP config): the server may be registered as
my-vibe-kit.
If an AI or script calls a tool and gets "MCP server does not exist", the caller should try the other identifier (e.g. try user-my-vibe-kit if my-vibe-kit failed, or vice versa). The exact ID is shown in Cursor’s MCP panel when the server is expanded.
Tools
| Tool | Description |
|------|-------------|
| get_kits | List all available templates. |
| search_kits | Search by query and optional category (landing, dashboard, form, theme). |
| get_kit_prompt | Get the React/Tailwind prompt for a kit by ID (requires MVK_API_KEY for premium kits). |
Troubleshooting
- "MCP server does not exist" when calling a tool: use server ID
user-my-vibe-kit(ormy-vibe-kit) as appropriate for your install; see Server ID in Cursor above. - Unauthorized / 403 on get_kit_prompt: set
MVK_API_KEYin the server’s environment or upgrade at myvibekit.com.
