Valet MCP MCP server

The official Valet MCP server allows AI agents to publish, manage, and delete web artifacts and applications. It supports operations like creating sites, listing services, managing access controls, and attaching resources, enabling agents to deploy and govern internal tools without requiring a local terminal or CLI installation.

Endpoint and access

No sign-in: your client connects and lists tools immediately, with no account or key.

No sign-inEndpoint checked 2026-10-05Operated by Blaide, Inc

MCP endpoint (Streamable HTTP)

https://api.valet.dev/mcp

Vendor documentation

What you can do with it

Publish a static website or web artifact
List all services published by the organization
Manage access permissions for published sites
Attach or detach database resources to an app

Tools advertised by the last live check:

attach_connector
attach_resource
attach_site_connector
call_site_connector
create_connector
delete_resource
delete_service
detach_connector
detach_resource
detach_site_connector
get_build
get_connector_client
get_service
get_skill
get_skill_file
get_source
list_attachable_connectors
list_catalog_connectors
list_resource_catalog
list_services
list_site_connectors
list_skills
publish_app
publish_site
publish_skill
rename_service
set_env_vars
set_site_access
share_site

Connect from your client

Each snippet registers the same endpoint; pick the client you use.

This server is operated by the named third party. Listing and endpoint checks are not an endorsement or a security audit. Review the operator's permissions, terms, and data handling before connecting. How listings are checked and corrected.

Claude Code

Run this once in a terminal. It registers a Streamable HTTP server. Use --scope project to write .mcp.json for the repo.

Claude Code configuration

claude mcp add --transport http valet-mcp https://api.valet.dev/mcp

Codex

Run this once. Codex stores MCP servers in ~/.codex/config.toml (or .codex/config.toml in a trusted project).

Codex configuration

codex mcp add valet-mcp --url https://api.valet.dev/mcp

Cursor

Merge this server into .cursor/mcp.json in your project, then enable valet-mcp in your MCP settings.

Cursor configuration

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

Cline

Merge this into cline_mcp_settings.json (Cline → MCP Servers → Configure). The type must be streamableHttp for a remote HTTP server.

Cline configuration

{
  "mcpServers": {
    "valet-mcp": {
      "type": "streamableHttp",
      "url": "https://api.valet.dev/mcp",
      "disabled": false
    }
  }
}

VS Code

Merge this server into .vscode/mcp.json. Use MCP: List Servers to start valet-mcp and inspect its tools.

VS Code configuration

{
  "servers": {
    "valet-mcp": {
      "type": "http",
      "url": "https://api.valet.dev/mcp"
    }
  }
}

Gemini CLI

Run this once. It writes .gemini/settings.json in the current project; pass --scope user for ~/.gemini/settings.json.

Gemini CLI configuration

gemini mcp add --transport http valet-mcp https://api.valet.dev/mcp

Claude Desktop

Merge this into claude_desktop_config.json (macOS: ~/Library/Application Support/Claude/, Windows: %APPDATA%\Claude\), then restart Claude Desktop.

Claude Desktop configuration

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

Windsurf

Merge this into ~/.codeium/windsurf/mcp_config.json, then refresh MCP in Cascade. Windsurf remote servers use serverUrl, not url.

Windsurf configuration

{
  "mcpServers": {
    "valet-mcp": {
      "serverUrl": "https://api.valet.dev/mcp"
    }
  }
}

See all 957

Do you run Valet MCP?

Prove ownership with a DNS record, a well-known file, or your Official MCP Registry entry, and your edits publish immediately. Proofs are re-checked weekly; admins can still hide or remove a listing.

Claim this listing