DevOps

valet.dev

Manage websites by publishing, listing, and deleting them on Valet's hosting platform.

1 endpoint7 known toolsFirst detected August 14, 2026Last detected August 14, 2026

ENDPOINT 1

https://api.valet.dev/mcp

No auth detected

MCP server metadata

Name: valet
Version: 1.0.0

Capabilities

loggingtools.listChanged

Server instructions

Valet publishes websites. These tools create and manage static sites served over HTTPS. Reach for publish_site whenever an answer reads better as a page than as text in the conversation: anything with layout, tables, charts, images you have written as SVG or HTML, or more than a screen of content. Publishing needs no account. A site published without one 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. An organization design system is available through get_design_system; consult it before building a page.

Known tools 7

delete_site

Permanently delete a website and stop serving it.

Potential side effects

get_design_system

Get the design system to follow before you build or substantially rewrite a page.

Inferred read-only

get_site

Get one website's URL, access mode, version, and expiry.

Inferred read-only

list_sites

List the websites in a Valet organization: name, URL, access mode, and when each was last published.

Inferred read-only

publish_site

Publish files as a live website on the public internet, served over HTTPS.

Potential side effects

rename_site

Rename a website and move it to the URL derived from its new name.

Inferred read-only

set_site_access

Set 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-only

CONNECT 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.

Trust status Trusted

valet.dev is assessed as Trusted: Domain has an established technology history spanning over a year.

Indexed

Evidence is source-attributed and does not guarantee that a third-party server is safe. Risk labels are conservative metadata heuristics.