Use with AI tools
Our SDK and the Velvet Live API are new, so AI assistants don't know them yet and tend to invent method names. Give your assistant our docs and it writes working Velvet code instead. No account is needed for either option below.
Connect the MCP server (recommended)
Add this URL once and your assistant looks up our docs by itself whenever Velvet comes up:
https://developer.velvetrituals.com/api/mcp
It's a read-only MCP server over Streamable HTTP. It can't control a toy, and it doesn't need a key. Testers on the dev portal use https://dev-portal.thinkbeyondcorporate.com/api/mcp instead.
Claude Code
claude mcp add --transport http velvet https://developer.velvetrituals.com/api/mcp
Cursor
Add to Cursor, or put this in .cursor/mcp.json (one project) or ~/.cursor/mcp.json (every project):
{
"mcpServers": {
"velvet": { "url": "https://developer.velvetrituals.com/api/mcp" }
}
}
VS Code (Copilot)
Put this in .vscode/mcp.json:
{
"servers": {
"velvet": { "type": "http", "url": "https://developer.velvetrituals.com/api/mcp" }
}
}
Claude Desktop and claude.ai
In Settings → Connectors, choose Add custom connector, name it Velvet and paste the URL.
What it gives your assistant
- Tools:
search_docs(search the Toy SDK and Velvet Live docs),get_doc(one whole page),get_recipes(the cookbook patterns with their code) andget_toy_kinds(the four toy kinds, their models and the command limits). - Prompts:
integrate_toy_sdkandintegrate_velvet_livestart a guided integration in clients that show prompts as slash commands. - Our rules: the server tells your assistant to add a working Stop button wherever a toy is controlled, to check capabilities with
toy.infoinstead of model names, and to keep secret keys on your server.
Try these
- "Add a button that connects my Velvet toy and buzzes it at 70 for 3 seconds."
- "When the player loses a round, play the heartbeat pattern from the Velvet cookbook."
- "Sync my toy to this
<video>with a toy track." - "Wire Velvet Live tips into my PHP cam site: mint the model token on the server and load live.js on her page."
The two prompts work as slash commands too. In Claude Code, type /mcp__velvet__integrate_toy_sdk or /mcp__velvet__integrate_velvet_live.
Not working?
- Your assistant still invents method names. It loads servers when a session starts, so start a new session after adding Velvet. In Claude Code,
claude mcp listshould showvelvet … ✔ Connected. In Cursor, look for the green dot under Settings → MCP. - It's connected but doesn't look anything up. Name Velvet in your request, or ask it to "check the Velvet docs first".
429 Too Many Requests. The server takes 10 requests every 10 seconds from one IP. Wait a few seconds and ask again.
What we log
For every tool call we log the tool, what was searched or opened, and how long it took. It shows us what's missing from these docs. We don't store your IP address, an account or any key: the server doesn't know who you are. Cloudflare sees your IP only to count requests for the rate limit. Details are in our privacy policy.
Or paste the docs
Every docs page is also plain Markdown, in the llms.txt format:
- /llms.txt: an index of every page, with links.
- /llms-full.txt: all the docs in one file.
- Any page as Markdown: add
.md, for example /docs/quickstart.md.
Paste one of these URLs into your assistant's chat, or add it as a docs source in your editor (in Cursor: @Docs → Add new doc).
Check what it writes
An assistant can still get things wrong. Before you ship, check the safety rules: a Stop button on every page that controls a toy, strength 0–100 with a durationMs on every command, and no secret key (vr_sk_…) in page code.