DevOps
valet.dev
Manage websites by publishing, listing, and deleting them on Valet's hosting platform.
ENDPOINT 1
https://api.valet.dev/mcp
MCP server metadata
- Name
- valet
- Version
- 1.0.0
Valet publishes websites. These tools create and manage static sites served over HTTPS. Reach for publish_site whenever an answer reads better at a live URL than as text in the conversation: a report, essay, slide-like narrative, dashboard, marketing surface, or other static artifact. Honor an artifact form the user requests. Otherwise choose the artifact form and treatment from its audience, job, and material. A request for a live URL chooses delivery, not one long scrolling page. Every publish names the site: title and description are required, and a call missing either is refused before anything is published. title is what a person would call the page, and description is one sentence saying what it holds. Publishing uses a connected Valet account by default. Pass anonymous: true only when the user explicitly wants a temporary public site. An anonymous site is public to anyone who has the link and may be removed 36 hours after it is created, unless it is claimed; the result carries a claim URL that makes it permanent. Before building or substantially rewriting an artifact, call get_design_system. The organization design system supplies identity, not structure. Follow it wherever it speaks. Artifact guidance and model judgment decide the remaining choices; do not layer the default design system beneath it. Safety, accessibility, and medium correctness may adapt an identity choice. When the artifact is HTML, render it at 390px and verify the document itself does not overflow. Give wide flex or grid children min-width: 0. Use minmax(0, 1fr) for flexible tracks so local scrollers stay local. When a local scroller is necessary, show a visible cue when more content is available. For a table, keep the identifying column visible when practical or use another narrow-screen representation. Inspect computed foreground and background colors and verify rendered text contrast on every surface; safe tokens do not prove the intended selectors matched. Valet may place a bottom-center dock over the published page. When the page scrolls vertically, give its main scroll container bottom padding or equivalent clearance of about calc(6rem + env(safe-area-inset-bottom)) so the final content can scroll fully above the dock. Do not introduce scrolling solely to create this clearance. For fixed-height or slide-like artifacts, keep essential content and controls away from the bottom center when the composition allows. A page can show live data — analytics, uptime, anything an organization connector serves. The path is: list_attachable_connectors to see what the organization has, list_catalog_connectors and create_connector when it has nothing that fits, attach_site_connector to grant one to the site, list_site_connectors for its tools and schemas, and call_site_connector to sample a tool's real answer before writing page code. The page itself calls the connector same-origin; call get_connector_client for the contract and a ready-to-paste helper (the full valet-publish skill, for humans: https://raw.githubusercontent.com/valetdotdev/skills/main/skills/valet-publish/SKILL.md).
Known tools 16
attach_site_connectorAttach an organization connector to a website so pages served from that site can call the connector's tools.
Inferred read-onlycall_site_connectorRun one tool on a connector attached to a website and return what the connector answered.
Inferred read-onlydetach_site_connectorDetach a connector from a website, so pages served from that site can no longer call it.
Inferred read-onlyget_connector_clientGet how a page served from a Valet site talks to the connectors attached to it.
Inferred read-onlyget_design_systemGet the identity brief to follow before you build or substantially rewrite an artifact.
Inferred read-onlylist_attachable_connectorsList the organization connectors a website can hold — the discovery step before attach_site_connector.
Inferred read-onlylist_catalog_connectorsList the connectors Valet curates — the catalog an organization creates a connector from.
Inferred read-onlylist_site_connectorsList the connectors attached to a website, each with the tools a page served from that site can call.
Inferred read-onlylist_sitesList the websites in a Valet organization: name, URL, access mode, and when each was last published.
Inferred read-onlypublish_sitePublish files as a live website on the public internet, served over HTTPS.
Potential side effectsset_site_accessSet who can reach a website: public serves it to anyone who has the link, private serves it only to members of the organization that owns it, and password serves it to anyone who enters a shared visitor password.
Inferred read-onlyshare_siteShare a website with specific people by email, whether it is private or password-protected — sharing does not change who else can reach it.
Potential side effectsCONNECT WITH APPROVAL
Client installation
Review this server and its permissions before adding it. Secret placeholders must be set locally.
Codex
~/.codex/config.toml
[mcp_servers.valet]
url = "https://api.valet.dev/mcp"
enabled = true
Claude Code
.mcp.json
{
"mcpServers": {
"valet": {
"type": "http",
"url": "https://api.valet.dev/mcp"
}
}
}
Claude Desktop
Settings → Connectors → Add custom connector
Name: valet
Remote MCP URL: https://api.valet.dev/mcp
Add this remote URL as a custom connector in Claude Desktop. Availability depends on the user plan and workspace policy.
Cursor
.cursor/mcp.json
{
"mcpServers": {
"valet": {
"url": "https://api.valet.dev/mcp"
}
}
}
Visual Studio Code
.vscode/mcp.json
Add to Visual Studio Code{
"servers": {
"valet": {
"type": "http",
"url": "https://api.valet.dev/mcp"
}
}
}
Generic MCP
Client-specific MCP configuration
{
"name": "valet",
"transport": "streamable-http",
"url": "https://api.valet.dev/mcp"
}
MCP Inspector
Run the official MCP Inspector locally and enter the indexed Streamable HTTP endpoint.
TRUST AND VERIFICATION EVIDENCE
Trust Data Available
BuiltWith Trust API v2 evidence for valet.dev was fetched 2026-08-17T05:07:35.061Z and is being refreshed.
valet.dev is assessed as Trusted: Domain has an established technology history spanning over a year.
Evidence is source-attributed and does not guarantee that a third-party server is safe. Risk labels are conservative metadata heuristics.