Docs · MCP

Bring your own AI to Vueplay

Vueplay runs a Model Context Protocol server. Connect Claude, Cursor or any MCP client and it can read, edit, commit and publish your projects, with the AI subscription you already have. It works on every plan, including Free.

Server URL

https://vueplay.com/mcp

Streamable HTTP. Sign in with OAuth (a Vueplay consent screen), or send a personal access token as Authorization: Bearer vp_….

Claude (claude.ai and Claude Desktop)

Add Vueplay as a custom connector. You approve it once on a Vueplay page; no token to copy.

1Open Settings → Connectors in claude.ai or Claude Desktop.
2Choose Add custom connector, name it Vueplay and paste the server URL above.
3Click Connect. A Vueplay page opens: sign in and choose Allow access.
4In a chat, enable the Vueplay connector and ask, for example: “List my Vueplay projects and add a pricing section to the landing page.”

On Team and Enterprise organizations an owner may need to add the connector first.

Claude Code

Add the server, then run /mcp in Claude Code and choose Authenticate to sign in with your browser.

claude mcp add --transport http vueplay https://vueplay.com/mcp

Or skip the browser and use a personal access token:

claude mcp add --transport http vueplay https://vueplay.com/mcp \
  --header "Authorization: Bearer vp_your_token"

Cursor

Create a personal access token, then add this to ~/.cursor/mcp.json (or .cursor/mcp.json in a project):

{
  "mcpServers": {
    "vueplay": {
      "url": "https://vueplay.com/mcp",
      "headers": {
        "Authorization": "Bearer vp_your_token"
      }
    }
  }
}

VS Code and other clients

Any client that speaks Streamable HTTP works. Clients with OAuth support discover everything from the server URL (protected resource metadata, dynamic client registration or a client ID metadata document, PKCE). Others can send a token header. VS Code, in .vscode/mcp.json:

{
  "servers": {
    "vueplay": {
      "type": "http",
      "url": "https://vueplay.com/mcp"
    }
  }
}

OAuth redirect URIs must be https, or http on localhost / 127.0.0.1. Both the 2026-07-28 protocol and the 2025 revisions are supported.

Tools

Every tool acts as you, with exactly the access you have on the website: members edit, public projects are read-only to others, paid library items stay closed until you buy them.

whoami
Your account, plan and how the client is connected.
list_projects
Your projects, with search and filters.
get_project
One project: role, head commit, files, live URL, recent deployments.
create_projectwrites
A new project from a template (Vite + Vue 3 + Tailwind, or a component).
list_files
Files at the head commit (or any commit).
read_file
A text file, whole or by line range. Binary files are refused.
search_files
Grep across a project, plain text or regex.
write_fileswrites
Several files as one atomic commit, checked against base_commit.
delete_fileswrites
Delete files as one commit (kept in history).
project_history
Recent commits.
publishwrites
Build and deploy to the project's site (production or preview).
deployment_status
Build status with the tail of the build log.
search_library
Search the component and template library.
get_library_item
Props, events, slots and usage docs; code when you have access.
remix_library_itemwrites
Copy a library item into a new private project.
studio_url
A link for you to open the project in the Studio.

Also available: the prompt vueplay_conventions (Vue + Tailwind conventions for Vueplay projects), the prompt edit_project, and files as resources at vueplay://projects/<id>/files/<path>.

How edits land

Real commits

Every write is a git commit on your project, with a message, so you can review it in the Studio and roll it back.

No lost work

Writes name the commit they were based on. If you (or someone else) saved in between, nothing is overwritten: the AI re-reads and tries again.

You stay in charge

Nothing is published unless the AI calls publish. Every build keeps its log, and you can roll back to an earlier one.

Access and limits

• Apps you connect with OAuth are listed under Settings → Access tokens and apps. Disconnect one and it loses access immediately.
• OAuth access tokens last an hour and refresh tokens rotate on every use; they only work on the MCP server, not the rest of the API.
• Connected apps can't change your password, billing or tokens.
• Limits per account: 300 requests and 60 changes (commits, new projects, remixes, publishes) a minute.
• Prefer the Studio? Its AI bar can run on your own Anthropic API key.