valetmcpdeveloper-toolsdeployment
Build and publish AI agents, websites, artifacts, and files through Valet skills, CLI workflows, and an MCP endpoint.
Quick Install
Automated & IDE SetupCopy the AI prompt to install this server into Claude Code, Cursor, or another agent — or use 1-click editor setup below.
Manual Client & Custom JSON ConfigExpand JSON â–¾
Client Config & Setup
Remote HTTPChoose your client or environment
Target File:
💡 Paste the JSON block into your client's configuration file under mcpServers, then restart the application.
Overview
Use cases
Deploy prompt-defined agents to Valet Cloud
Publish files and folders from a coding agent
Expose Valet publishing when a shell is unavailable
Configure optional artifact publishing preferences
Key features
Streamable HTTP MCP endpoint
Agent workspace creation and deployment
File and folder publishing
OAuth-assisted account publishing
Explicit anonymous publishing
Optional publishing hooks
Capabilities & Tool Schemas
Inspect callable tools, capabilities, and parameters exposed to AI agents by Valet.
Extracted Tool Capabilities
Streamable HTTP MCP endpoint
Agent workspace creation and deployment
File and folder publishing
OAuth-assisted account publishing
Explicit anonymous publishing
Optional publishing hooks
How Valet works
What Valet does
The Valet MCP server provides a network-accessible fallback for Valet operations from coding-agent environments. It is distributed with the Valet skills repository and declared at https://api.valet.dev/mcp. The package also includes two agent skills: valet for creating and deploying skilled AI agents, and valet-publish for publishing files and folders to a live URL.
The Valet MCP server is most relevant when the agent cannot use the local CLI. The documented CLI-driven workflow remains broader: it can publish a complete directory, update a site from another location, configure password access, and transfer binary files. The MCP path does not provide those CLI capabilities.
This repository belongs to the 💻 Developer Tools category and is intended for developers configuring coding agents, agent workspaces, and deployment workflows.
How it works
The package declares the MCP endpoint in both mcp.json and .mcp.json. Agent Plugins 1.0.0 clients read the former and use the streamable-http transport; Claude Code reads the latter and uses http. The files are expected to remain synchronized, and the repository provides a lint command that checks whether the server and URL match between them.
A normal publish request can start the connector’s OAuth flow when authentication is needed. Anonymous publishing is available only when explicitly requested with anonymous: true, and is intended for a temporary public site. Claiming an anonymous site signs the user into the browser and makes that site permanent, but does not authenticate the MCP connector. A later account-first MCP request can therefore start OAuth for that client.
The Valet skills and MCP configuration can be installed together through the plugin marketplace, or the skills can be installed separately with npx skills. The plugin is all-or-nothing for the two skills; installing individual skills omits the MCP server.
Setup and configuration
For Claude Code, add the marketplace and install the plugin:
Codex can use the same marketplace manifest:
A client implementing Agent Plugins 1.0.0 can also load the package from a directory path. The repository is a generated mirror, so changes should be directed to the upstream Valet source rather than this mirror.
The optional publishing hooks use VALET_PUBLISH_HOOK. Its values are ask by default, deny to block Claude Code’s Artifact tool, and off to disable the hooks. The hooks remain silent if the Valet CLI is not available on PATH.
Tools and capabilities
The Valet MCP server supports the network-side publishing fallback included in the package. The associated skills can:
- Create an agent workspace with
SOUL.md, skills, and channels. - Help iterate on an agent defined by prompts rather than application code.
- Deploy the agent to Valet Cloud.
- Publish files and folders to a live URL through the Valet publishing workflow.
- Use account-first authentication or explicitly request anonymous publication.
The valet-publish skill drives the local Valet CLI when that CLI is available, rather than treating MCP as the primary publishing route.
Limitations and notes
The MCP connector and CLI maintain separate credentials. An anonymous site claim does not log the connector into the user’s account. The MCP tools also do not cover the CLI’s complete directory publishing, later site updates, password access, or binary-file handling.
The publishing preference hooks are client-specific extensions, not part of the portable Agent Plugins specification. Claude Code wires them through the plugin; other conformant clients receive the skills and MCP server only when they support the package format. Codex no longer uses plugin-delivered hooks automatically, so its publishing preference requires a separate manual setup described by the repository.
Choose either the plugin or standalone skill installation, not both, because installing both can place duplicate copies of the skills in the agent’s load paths.
Getting started with this Valet MCP server
Always refer to the official documentation for the most accurate and up-to-date information.
Related MCP Servers
Adoption & maintenance
Factual signals from GitHub, npm, and our automated checks — not a rating.
Last commit
9d ago
Most recent push to the default branch.
Directory activity
1 upvotes
Config copies, upvotes, and views on AllMCPs.
Reviews (1)
5.0
1 rating
51
40
30
20
10
Frequently Asked Questions about Valet
AllMCPs Directory Badge
Showcase your server listing on GitHub or your project documentation. Embed this dynamic SVG badge to highlight official listing status and live engagement.
Badge Style:
Live Dynamic SVG Preview
Markdown (GitHub README)
[](https://allmcps.com/mcp/valet)HTML Embed
<a href="https://allmcps.com/mcp/valet"><img src="https://allmcps.com/api/badge/valet?style=directory" alt="Valet on AllMCPs" /></a>Technical Specs & Signals
CategoryDeveloper Tools
PricingFreemium
12/12 checks healthy over the last 45d
45Quality signal: Fair · 45/100How this signal is calculated ▾
Server availabilityNot measured
Not scored for repo-hosted servers — we can't reach the running server, only its GitHub page. Hosted MCP endpoints are health-checked live.
Verified ownership10/20
Documentation & tools17/30
Adoption & activity4/15
Community engagement3/10
A guidance signal from public completeness & health data — not a user rating. New listings start lower and rise as they add docs, get verified, and grow adoption. Signals we can't observe for a listing are skipped, not counted against it.
Supply-chain signal
No high-severity advisories surfaced by our automated scan.
Critical 0High 0Medium 0Low 0
Scanned 24d ago via OSV.dev · https://api.valet.dev/mcp (npm)
Own this project?
This directory is pre-filled from public sources. Claim via GitHub README, site badge, or DNS TXT to unlock edit access and the Official badge — proof is checked automatically, then reviewed by our team.
Free dofollow backlink: add your website and place the AllMCPs badge on it — no claim needed. We detect it automatically and keep it verified as long as the badge stays live.
Claim & get free dofollowShare & Embed
Add our SVG badge (dark/light directory styles) or embeddable widget to your site.