Skip to content
Documentation

AI assistants

Connect Claude and other AI assistants

Let an AI assistant build, change and publish your Vorx projects for you, over MCP.

Connect Vorx to an AI assistant and it can build, change and publish your Vorx projects from the conversation. You describe what you want in plain English, and the assistant does the work in Vorx for you.

This uses the Model Context Protocol (MCP), the open standard assistants use to connect to other services. Vorx runs an MCP server at:

https://www.vorx.com/mcp

What the connection can do

Once connected, your assistant can:

  • Create a project from a brief, the same way you would on the Launch page.
  • Change an existing project, as if you had typed the request into its chat.
  • Check a build: whether it is running, finished or failed, and the preview address.
  • List your projects in the workspace you connected.
  • Publish a project to its public Vorx address.

Builds take several minutes. The assistant starts the work, checks on it until it finishes, and then tells you where to see the preview.

Building and changing projects uses your workspace's credits, exactly as it does in the Vorx app. Publishing is not charged. The connection never charges a card.

Daily limits

Each connection, and each API key, has its own limits per day. A day is counted in UTC and resets at 00:00 UTC.

  • 50 builds started: every request to create or change a project counts, whether or not it succeeds or changes anything.
  • 100 credits charged: once a connection has been charged 100 credits in a day, it cannot start another build that day. The check happens when a build starts, so a build already running can take the day past 100.
  • 20 publishes.

A request over a limit is refused before anything starts, and nothing is charged. Your assistant is told which limit was reached, and a refused change to an existing project also gets a reply in that project's chat. If Vorx cannot count the day's usage at that moment, it refuses rather than guessing; try again in a minute.

These limits sit on top of your workspace's credits: a build still needs credits in the workspace. You cannot yet see how much of a day's limit a connection has used, or change its limits.

Connect

When you add Vorx, your assistant opens a Vorx page in your browser. Sign in if you are asked to, choose which workspace to connect, and click Allow. The page shows where the connection returns to, so you can check it is the assistant you started it from.

Claude Code

Run this in your terminal:

claude mcp add --transport http vorx https://www.vorx.com/mcp

Then, in Claude Code, run /mcp, choose vorx and Authenticate.

Other assistants

In any assistant that can connect to a remote MCP server, add a custom connector with the address https://www.vorx.com/mcp. The assistant finds Vorx's sign-in page by itself, so there are no keys to copy.

Things to try

Once you are connected, ask for things in your own words. For example:

  • "Using Vorx, build a one-page website for a dog-walking business called Paws Around Town, with services, prices and a contact form."
  • "What's the status of my latest Vorx build? Send me the preview link when it's done."
  • "In my Vorx project Paws Around Town, change the headline to 'Happy dogs, happy owners' and make the buttons green."

Disconnect

Every connection is listed under Settings → Personal → API keys with the assistant's name. Revoke it there and the assistant loses access immediately. You can connect again at any time. An assistant can also end its own connection through the standard OAuth revoke endpoint (https://www.vorx.com/oauth/revoke).

Using an API key instead

If a tool cannot sign in this way, create a key under Settings → Personal → API keys and tick Let AI assistants use this key (Claude, ChatGPT), and send it as a Bearer token to the same address. See Using the Vorx API for how keys work.