# Valet [Health: Active]

**Category:** 💻 Developer Tools  
**Repository:** https://github.com/valetdotdev/skills  
**GitHub Stars:** 0  
**Views:** 2  
**Installs:** 0  
**Upvotes:** 1  
**Directory Page:** https://allmcps.com/mcp/valet

## Description
Get share links, publish and manage websites, artifacts and agents. No account needed.

## Claude Desktop Quick Installation
Remote MCP endpoint (confidence: high). Install path detected from listing signals. Add as a URL/SSE server in your client:

```json
"mcpServers": {
  "valet": {
    "url": "https://api.valet.dev/mcp"
  }
}
```

## Documentation

## 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:

```text
/plugin marketplace add valetdotdev/skills
/plugin install valet@valet
```

Codex can use the same marketplace manifest:

```text
codex plugin marketplace add valetdotdev/skills
codex plugin add valet@valet
```

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.

_Full upstream README: https://allmcps.com/mcp/valet/readme_