Connect Your Agent
Valet works from whatever tool you already build in. How you connect it depends on one thing: whether that tool can run a command.
- It can — Claude Code, Codex, Cursor, and every other coding agent. Install the Valet plugin or skill and your agent publishes for you, from the folder you are working in.
- It cannot — Claude Cowork, claude.ai, ChatGPT, and mobile. Add Valet's MCP server as a connector and the same publishing tools appear in the conversation.
The short way
If your tool has a terminal, you do not have to pick anything below. Copy these instructions, paste them in, and the agent installs the right thing for its own harness and publishes a page:
Free to try · No signup required
Tools with a terminal
Claude CodePlugin
One plugin: both skills, Valet's MCP server, and the publishing preference that fires without being asked. /plugin update keeps it current.
/plugin marketplace add valetdotdev/skills
/plugin install valet@valetRestart Claude Code to load it. To have your agent do the install instead, hand it the same thing as shell commands:
claude plugin marketplace add valetdotdev/skills
claude plugin install valet@valetCodexPlugin
Codex reads the same marketplace manifest.
codex plugin marketplace add valetdotdev/skills
codex plugin add valet@valetThis installs both skills and the MCP server, which is enough on its own. Codex has retired plugin-delivered hooks, so the publishing preference is an optional manual step there — see codex/README.md.
CursorSkill file
npx skills add valetdotdev/skills -gCursor reads the same Agent Plugins manifest Valet ships, but installs plugins from the Cursor Marketplace or a team marketplace an administrator imports — not from an arbitrary repository. Until Valet is listed there, install the skills directly.
Gemini CLI, opencode, Windsurf, Amp, Copilot CLI, and othersSkill file
npx skills add valetdotdev/skills -gAnything with a shell that npx skills supports. The -g installs for every project; drop it to install into the current one only. To take a single skill rather than both, add --skill valet-publish or --skill valet.
This installs skill files only. The MCP server the plugin declares is not part of it — add it separately if you want the fallback for sandboxes where the CLI cannot run.
Pick the plugin or the skills, not both. Codex loads skills from ~/.agents/skills/ and from installed plugins, so doing each puts two copies of the same skill in front of the model. See the Valet skill for what the two skills do.
Tools without a terminal
These connect to Valet's MCP server instead. It publishes artifacts from inside the conversation, with a smaller tool surface than the skills — no folders from disk, no binary files, no agents. The address is the same everywhere:
https://api.valet.dev/mcpClaude Cowork, claude.ai, and Claude mobileMCP connector
Settings → Connectors → Add custom connector. Paste the URL and connect. Claude registers itself, so there is no client ID or secret to create.
ChatGPTMCP connector
Custom connectors sit behind developer mode. Settings → Connectors → Advanced → turn on Developer mode. Then add a custom connector and paste the same URL.
This needs a paid plan. Developer mode is available on Plus, Pro, Business, Enterprise, and Edu. Free accounts cannot add custom connectors at all — on Free, use a tool with a terminal instead.
Any other MCP clientMCP connector
The server speaks Streamable HTTP and advertises its own authorization metadata, so a client that implements MCP needs nothing but the URL. See MCP Server for the tools it exposes and what signing in changes.
Then ask for something worth sharing
However you connected, the next step is the same: ask for a dashboard, a report, a prototype — anything that renders in a browser — and ask for it published. You get back a live URL.
No account is needed to start. The first URL is public and disappears after 36 hours, and your agent prints a claim link beside it that makes the artifact permanent and private to your organization. See Overview for that walkthrough.