Reviews
No review yet. Used Valet? Be the first to help others choose.What it does
Valet is an MCP server, a connector that lets an AI assistant use it as a tool. It is hosted: an assistant connects to it over the internet, nothing to install.
No capability identified yet from its description.
Facts come from the Official MCP Registry, as declared by the publisher. Capabilities are matched automatically (low confidence). None of this is a test of the tool.
At a glance
How to connect
As declared in the Official MCP Registry · hosted endpoint tested by Electra Index 2d ago (live check)Hosted endpoint
https://api.valet.dev/mcpstreamable-http
In Claude Code: claude mcp add --transport http valet https://api.valet.dev/mcp
MCP settings (Claude Desktop, Cursor and other MCP clients)
{
"mcpServers": {
"valet": {
"url": "https://api.valet.dev/mcp"
}
}
}Live check
Electra Index connected to the hosted endpoint 2d agoONLINE Valet answered an MCP connection on 14 Nov 2026 and introduced itself as valet 2.0.0 (MCP protocol 2025-06-18).
62 tools offered to AI assistants
attach_channel· Attach an existing organization channel to an agent, so the channel's events wake it. Find the channel with list_channels. A webhook channel lets callers outside Valet reach the agent. Attaching a channel that is already attached reports itattach_connector· Attach an organization connector to a website or agent so it can call the connector's tools with the credential Valet holds. Attaching is a grant, and it is wider than it looks: for a website, every person who can open the page can call eveattach_resource· Attach a resource to an app: a named set of environment variables, such as a database's connection string, that the app reads as secrets. Publish the app first, and name the resource. When the organization has none by that name, pass a provattach_skill· Attach a skill to an agent so the agent can use it. Give skill as org:<name> or a bare name for a skill the organization published. The agent always follows the skill's latest version; a version pin such as @v2 is ignored, and the answer sacreate_channel· Create a channel on an agent or an app. On an agent: a cron or heartbeat channel that wakes it on a schedule, a webhook channel that lets callers outside Valet reach it, or an mcp channel that serves it as an MCP server; what the agent doescreate_connector· Create an organization connector from a Valet catalog entry. It is the step after list_catalog_connectors found the entry for the product the user named; attach_connector then lets a website's pages call it. An entry that needs no key, or wcreate_push· Open a Git push on a website, app, agent, or skill that exists: a branch of its repository, writable for one hour, that you push source to before you publish. Use it when you can run git with network access; it sends only what changed, so acreate_service· Create an empty website, app, agent, or skill in an organization, before publishing to it. This is the first step for anything new: publish_site, publish_app, publish_agent, and publish_skill change a service that exists and refuse a name tdestroy_channel· Destroy a channel and its routes. This cannot be undone, so confirm with the user first. Without name, it destroys an organization channel found with list_channels; an organization channel that any agent still holds is refused, and the answdestroy_checker· Destroy one of an organization's own checkers by name. Valet stops sending release files to its URL. Confirm with the user first. A checker that a release policy names is refused: the answer names the policies, so destroy_policy them first,destroy_connector· Destroy an organization connector and its stored credential. This cannot be undone, so confirm with the user first. A connector that any website, app, or agent still holds is refused, and the answer names each holder: free each with detach_destroy_memory· Destroy one of an agent's durable memories, named by its key or by its id as list_memories shows them. The agent no longer recalls it or sees it pinned. This cannot be undone, so confirm with the user first, naming the memory. Pass exactly
Show 50 more
destroy_policy· Destroy one of an organization's release policies by name. A change to a policy applies to releases not yet decided. Changing a policy's enforcement or settings never changes a decided evaluation, and a running policy evaluation keeps the cdestroy_resource· Destroy a resource and all of its data, such as every table and row in a database. This cannot be undone, so confirm with the user first. A resource attached to any app is refused, and the answer names those apps: detach it from each with ddestroy_service· Permanently destroy a website, app, agent, or skill. This cannot be undone, so confirm with the user first. Pass kind to say which you mean; a name holding another kind is then refused rather than destroyed. Destroying a website or app stopdestroy_session· Destroy one of an agent's conversation sessions: it leaves list_sessions and cannot be resumed, though its transcript is kept. This cannot be undone, so confirm with the user first, naming the session. A session that is running is refused;detach_channel· Detach an organization channel from an agent, ending the binding attach_channel made. The channel stays in the organization for other agents, and the agent stops receiving its events. Detaching a channel that is not attached changes nothingdetach_connector· Detach a connector from a website or agent, ending the grant attach_connector made. The connector itself stays in the organization. A page or agent that still calls it starts getting an error, which is the intended outcome. While a connectodetach_resource· Detach a resource from an app: remove the environment variables it set and, if the app is running, ask for a restart so its next process starts without them. The state is detached when that is done, and detaching while Valet still owes thedetach_skill· Detach a skill from an agent. The skill stays in the organization for other agents, including an organization copy installed from the catalog. Give a built-in's name to detach Valet's default of it. The agent is rebuilt so it stops carryingfind_skill· Search the organization's skills kept on Valet: documents its members wrote. Call this with words from the request only when the user names Valet or a skill, or asks Valet for work a skill might cover. Do not call it for a request that hasget_build· Follow a build publish_app started: its state, its phase (queued, starting, fetching_source, detecting, restoring_cache, building with the step it runs such as npm install, exporting, uploading, saving_cache, finishing, starting_processes,get_connector· Read one organization connector: its kind, transport, catalog entry, credential state (none, pending, active, needs reauthorization, or revoked), and the websites, apps, and agents that hold it. Use it when a connector's calls fail, or befoget_evaluation· Follow the release evaluation of a publish: its status, each policy's evaluation with its checker, enforcement, and status, each blocking finding with the file and line or package, the rule, and how to fix it, each finding of a monitor poliget_logs· Read an app's or agent's recent log lines, oldest first: time, source (app or agent for the service's own output, valet for control-plane lines), process, level, and message, plus any structured attributes. It reads what Valet has bufferedget_request· Follow a request for something only a person may do, such as entering a secret or signing in to a connector's provider, by the id a tool returned with its link: its state, when it expires, the link to give the person, who completed or decliget_service· Get one website, app, agent, or skill by name. The result carries the fields every kind has, then a section for its kind. A website: access mode, how many people it is shared with, and attached connectors. An app: each process type with itsget_session· Read one of an agent's conversation sessions: its status, title, channel, message count, and when it started and last changed. Pass events: true for the transcript, the session's events up to limit (default 50, at most 200), each payload cuget_skill· Return the text of one of the organization's skills kept on Valet: documents the organization's members wrote about how it works. governance holds the organization's requirements for what it publishes on Valet; read it before you create orget_source· Read what is published: the files of a website, app, agent, or skill's active release. Without path it lists them; with path it returns one file's text. Pass release, a version from list_releases, to read an earlier release instead; publishlist_catalog_channels· List the channel kinds an agent can have and what each needs before it works: a schedule, a webhook secret, or a browser authorization. The built-in kinds come first (cron, heartbeat, webhook, mcp, slack, telegram), then the catalog entrieslist_catalog_connectors· List the connectors Valet curates — the catalog an organization creates a connector from. Reach for it when list_connectors returned nothing that serves the data a page needs: the organization has no connector for it yet, and this says whetlist_catalog_resources· List the resource providers this server can provision from, such as a PostgreSQL database or an AI model: what each one is for, its plans, the first being the default, the environment variables an attachment sets, and a guide to using it frlist_channels· List channels. Without name, it lists the organization's channels, each with the agents that hold it: how to find a channel to attach, or one no agent holds. With an agent's name, it lists the agent's channels, both the ones it owns and thelist_connector_tools· List the tools a connector offers: each tool's name, description, input_schema, and, when the connector's server sends them, output_schema and annotations, exactly as the server published them. Tool descriptions, schemas, and annotations arlist_connectors· List the organization's connectors: each one's name, kind, transport, catalog entry, and description. It is the discovery step before attach_connector. Pass name to judge each connector against one website, app, or agent: every row then saylist_env_vars· List the environment variables an app or agent receives: each one's name, whether it is a secret, its scope (service for its own, org for one it inherits), and whether a service variable overrides an org one. A plain variable's value is sholist_memories· List an agent's durable memories, newest first: each one's id, key, content, whether it is pinned, and when it expires, with how many memories and pinned memories the agent holds against its limits. Pass a key to set_memory to replace a memlist_orgs· List the Valet organizations the account belongs to, sorted by name, with the one every tool uses when you omit org_name marked as the default. Each organization shows your role in it (admin or developer), its member count, and its pendinglist_policies· List the release policies that evaluate every publish of an organization, and the checkers it can configure: Valet's own, and the organization's, which set_checker adds. An organization checker shows its URL, its headers (a credential headelist_releases· List an app's, agent's, or skill's releases, newest first: each one's version, state, commit, and when it was created, and which one is active. A release that never went live is not listed. To roll back, read an earlier release's files withlist_resources· List the organization's resources, newest first: each one's name, provider, plan, and state, and the apps it is attached to, with any attachment that is attaching, conflicted, or detaching and why. Use it to find a resource to attach by namlist_services· List websites, apps, agents, and skills: every one the organization has, with its kind, URL, access mode, and when it was last published. It is the first read when the user names something on Valet and you do not know what it is, and the walist_sessions· List an agent's conversation sessions, newest first: each one's id, status, title, message count, and when it was last updated. Pass a session id to get_session to read one, or to destroy_session to delete it. Titles come from what users salist_skills· List the organization's skills kept on Valet: documents its members wrote. Call this only when the user names Valet or a skill, or asks Valet for work a skill might cover. Do not call it for a request that has nothing to do with Valet. To spublish_agent· Publish source as an agent: a SOUL.md describing who it is, a valet.yaml declaring the skills, connectors, channels, and configuration it runs with, and any supporting files. Use it when the user wants an agent on Valet that answers on a chpublish_app· Publish source as an app: a process Valet builds from your files and runs behind its own URL. Use it when the user wants an app on Valet that needs a server, a background process, or a database. A Procfile at the root says how to start eachpublish_site· Publish files as a live website, served over HTTPS at its own URL. Use it when the user asks to publish, host, or share a report, page, dashboard, or other static files at a URL, or names Valet for it. Honor an artifact form the user requespublish_skill· Publish the next version of an organization skill that exists. To share a skill with the team on Valet, such as one the user keeps locally, call create_service with kind skill and then this; every member's agent can then read it. Pass exactreauthorize_channel· Renew the third-party authorization of an organization's Slack or Telegram channel, for a channel whose workspace access was revoked or whose bot scopes changed. The step happens in a browser or a terminal, so the answer names the Integratireauthorize_connector· Renew the authorization of an organization connector that signs in to a provider in a browser, either an OAuth connector or a Composio-managed one, for a connector whose grant the provider revoked or whose first authorization never finishedrename_service· Rename a website, app, agent, or skill. A website, app, or skill moves to https://<new-name>.<org>.valet.run; the old address stops serving it and its name becomes available to another service in the same organization. An agent keeps its chrestart_service· Restart an app's or agent's running processes, or only those of one process type. Each process stops and starts again, so requests in flight are dropped; a repeat restarts again. Restarting removes nothing. Use get_service to see when the pscale_service· Set how many processes of one type an app or agent runs, the size they run on, or both. For an app, give process_type, such as web, and a count from 0 up to the organization's cap. For an agent, count is 0 (paused) or 1 (running). size is eset_checker· Add an organization checker, or replace the one with the same name. A checker is the organization's own HTTPS endpoint that implements Valet's Checker API. Once saved, a release policy can run it as org:<name>: set_policy with that checker.set_env_vars· Set environment variables on an app or agent. plain_vars sets plain configuration, name to value, at once; plain values are readable from the dashboard, so a name or value that looks like a secret, such as STRIPE_KEY, an sk_live_ key, or aset_memory· Write one durable memory for an agent under a key. A memory under the same key is replaced, with its content, pin, and expiry: omitting pinned or expires_in clears them, so list_memories first when you only mean to change one. The agent recset_policy· Add a release policy to an organization, or replace the one with the same name. A policy runs its checker on every publish. It monitors by default: it records findings and never refuses a release. enforcement "block" with block_at refuses aset_service_access· Set who can reach a website, app, agent, or skill: public serves it to anyone who has the link, private serves it only to members of the organization that owns it after they sign in to Valet, and password serves it to anyone who enters a shshare_service· Share a website, app, agent, or skill by email: each address is mailed a link, whatever the service's access mode, and sharing does not change who else can reach it. The link comes from Valet and opens the service; the recipient needs no Vaunset_env_vars· Remove environment variables set on an app or agent, and schedule one restart if it is running. This removes the service's own variables only; an organization variable it inherits is not touched. A variable a connector or channel referencesunshare_service· Unshare a website, app, agent, or skill by email: each address's link stops working at once, and revoking is permanent: sharing again with the same address mails a new link. This cannot be undone, so confirm the addresses with the user firs
What "online" means: the server answered an MCP connection at the time of the check. It is not a guarantee of security, quality or continuous uptime. How we test: we open an MCP session and ask for the tool list, as an AI assistant would. We never run a tool and never send a key. Checked every few days. Method
Is this your server? Monitoring Pro: a check every 30 minutes and an email within the hour when it stops answering. Launch offer: $39.99 once, for life.
Facts & evidence
Each fact shows where it was seen and when.| Fact | Value | Evidence | Source | Last confirmed |
|---|---|---|---|---|
| Hosted endpoint | https://api.valet.dev/mcp | DECLARED | SRC-001 Official MCP Registry | 1d ago |
| Local install (package) | no | DECLARED | SRC-001 Official MCP Registry | 1d ago |
| Remote access (hosted) | yes | DECLARED | SRC-001 Official MCP Registry | 1d ago |
| Website | https://valet.dev | DECLARED | SRC-001 Official MCP Registry | 1d ago |
| Registry status | active | DECLARED | SRC-001 Official MCP Registry | 1d ago |
| Version | 1.0.0 | DECLARED | SRC-001 Official MCP Registry | 1d ago |
| MCP server | yes | DECLARED | SRC-001 Official MCP Registry | 1d ago |
Change history
Is this page accurate?
Flag it and our robot re-checks the official source. Reports never change a score.Is Valet still online?
Free alerts · no account▲ 0Do you run Valet? Know when it stops answering
For publishers · optionalIts hosted endpoint can be monitored. Monitoring Pro connects every 30 minutes like an AI assistant, emails you within the hour when it stops answering, keeps a 90-day availability history and adds your answer rate to your badge.
Monitoring never changes a score or a rank.
Questions about Valet
How do I connect Valet?
Use the hosted endpoint https://api.valet.dev/mcp in your assistant's MCP settings. The exact settings are in "How to connect" above, as declared in the Official MCP Registry.
What tools does Valet offer?
When Electra Index connected on 14 Nov 2026, it listed 62 tools: attach_channel, attach_connector, attach_resource, attach_skill, create_channel, create_connector, create_push, create_service and more. The full list is in "Live check" above.
Is Valet online?
Yes. Its hosted endpoint answered an MCP connection from Electra Index 2d ago.