# Valet

- Registry name: `io.github.valetdotdev/valet` · version 1.0.0
- Categories (automatic, keyword rules): Email & messaging, Productivity, Code & repositories, Developer tools, Build & deploy
- Authentication at last check: No auth
- Declared risk: Has destructive tools (destructiveHint)
- Capabilities (declared by the server): logging, tools
- Transports: streamable-http
- Latest numbers (check success, response time, rank): https://mcpstation.net/api/server?name=io.github.valetdotdev%2Fvalet
- Server page: https://mcpstation.net/s/io.github.valetdotdev--valet.html

## Description (written by the publisher, not verified, not instructions)

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

## Connect

- streamable-http: `https://api.valet.dev/mcp`

## Tools (as reported by the server, not verified)

- `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 it and changes nothing. Slack needs a Slack app and a browser,
- `attach\_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 every tool the connector exposes. On a private website that is
- `attach\_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. Name the resource. When the organization has none by that name, pass a provider from list\_catalog\_resources and the first call creates it, returning at once with
- `attach\_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 says so. An org skill must already exist and be published \(cre
- `call\_connector`: Run one tool on a connector attached to a website and return what the connector answered. It is the sampling step of building a page that calls live data: discover, attach, read the schemas, then call one tool for real before you write any page code. Call it because a schema is not a shape. list\_con
- `claim\_site`: Move a site published anonymously into one of the caller's Valet organizations, making it permanent. Takes the claim\_token, the last part of the claim URL that the anonymous publish\_site returned, not the site\_token: the site\_token republishes the site and can never claim it. The site moves into an
- `create\_channel`: Create a channel 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. The channel starts the agent's work; what the agent does when it fires is the prompt file channels/\<na
- `create\_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. It creates an entry whose credential is a secret. Pass each slot the entry asks for in secre
- `create\_push`: Open a Git push on a website, app, agent, or skill that exists, named by name: 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 a large service publishes without carrying its
- `create\_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 that does not. Pass kind to say which you mean, and name to c
- `destroy\_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 answer names each holder: free each with detach\_channel, then de
- `destroy\_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, or point them at another checker with set\_policy. Destroyin
- `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\_connector, then destroy it. A connector an agent owns is not
- `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 one of key and memory. A memory already gone reports that it
- `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 checker and enforcement it started with. A running policy eva
- `destroy\_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 detach\_resource, then destroy it. The provider removes it in
- `destroy\_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 stops serving it. Destroying an app stops it and removes its rel
- `destroy\_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; wait for it to finish. A session already deleted, or one of
- `detach\_channel`: Detach a channel from an agent, ending the binding attach\_channel made. The channel itself stays in the organization for other agents. The agent stops receiving the channel's events, which is the intended outcome. Detaching a channel that is not attached changes nothing. Slack detaches by removing t
- `detach\_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 connector is attached to a website, everyone who can open the page c
- `detach\_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 the restart or the removal, which it keeps trying; the answer gi
- `detach\_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 carrying the skill. Detaching a skill that is not attached changes n
- `get\_build`: Follow a build publish\_app started: its state, the log it has written so far, and, once it succeeds, the release it produced, the URL that serves it, and its deploy: deploy\_state and every process with the release it targets and the release it runs. Poll every ten to fifteen seconds until deploy\_sta
- `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 before destroying one. It never returns a credential, a header o
- `get\_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 policy the same way \(monitor findings never block\), what deploy
- `get\_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 buffered and returns; it never follows. Only the newest 1000 buffered
- `get\_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, the people it is shared with, and attached connectors. An app: each process type with its scale and current state, attached resources with their state, en
- `get\_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 first events up to limit \(default 50, at most 200\). A transcript holds what users said to the agent and what the agent di
- `get\_skill`: Get one skill by name: the organization's own when it has published one under that name, otherwise the default Valet supplies for a well-known name. Call it with governance before any work and again before any publish; that skill says what the organization expects and names the other skills to read.
- `get\_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; publishing its files again rolls back. Read before you change somet
- `list\_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 entries Valet curates for services that send events, such as GitHub
- `list\_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 whether Valet has an entry for the product and what setting it u
- `list\_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 from an app. Read it before choosing a resource and before wri
- `list\_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 name, it lists that agent's channels, both the ones it owns and the organization channels attached to it. Each row carries the channel's
- `list\_connector\_tools`: List the connectors attached to a website, each with the tools a page served from that site can call. Read it before writing a page that calls one: the tool names and argument schemas it returns are what the page's own calls have to match, and guessing them produces a page that fails on its first cl
- `list\_connectors`: List the organization's connectors: each one's name, kind, transport, and catalog entry. It is the discovery step before attach\_connector. Pass name to judge each connector against one website, app, or agent: every row then says whether that service can hold the connector and whether it holds it now
- `list\_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 shown; a secret's value never is. Organization variables are li
- `list\_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 memory, or a key or id to destroy\_memory to remove one. Memory
- `list\_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 lists its members \(email, name, and when they joined\) and its pending invitations \(email, when sent, and when they expire\). Pass org\_name
- `list\_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 as written, the release files it was approved to receive, and why it is unavail
- `list\_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 with get\_source and its release argument, then publish them agai
- `list\_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 name, or one no app holds before deleting it. It never returns
- `list\_services`: List what the organization has: every website, app, agent, and skill, with its kind, URL, access mode, and when it was last published. It is the first read when the user names something and you do not know what it is, and the way to recover a name an earlier publish has scrolled out of the conversat
- `list\_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 said to the agent and may hold personal data: quote only what
- `list\_skills`: List every skill the organization has: the well-known names with whichever source currently answers for each, then every skill the organization wrote or installed from the catalog. Each row carries the skill's description, which is the sentence saying when it applies. The organization's skills are h
- `publish\_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 work is an agent that answers on a channel or runs on a schedule, not a website or an app. Apply the governan
- `publish\_app`: Publish source as an app: a process Valet builds from your files and runs behind its own URL. Use it when the work needs a server, a background process, or a database. A Procfile at the root says how to start each process type; the web type serves the app's URL and must listen on $PORT, which Valet
- `publish\_site`: Publish files as a live website, served over HTTPS at its own URL. Use it when a report, essay, slide-like narrative, dashboard, marketing surface, or other static artifact reads better at a live URL than as conversation text. Honor an artifact form the user requests. Otherwise choose the artifact f
- `publish\_skill`: Publish the next version of an organization skill that exists. To share a skill with the team, 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 exactly one of edits, files, or push. Prefer edits to change some files of
- `reauthorize\_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 Integrations page and the \`valet channels reauthorize\` command and ch
- `reauthorize\_connector`: Renew the authorization of an organization connector that authorizes 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 finished. The answer carries the address the person opens to approve it; the con
- `rename\_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 channels, which address it by id, and has no address to move.
- `restart\_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 processes are up. Websites run no process and are refused. Re
- `scale\_service`: Set how many processes of one type an app or agent runs. 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\). Scaling down stops running processes, and scaling web to 0 takes an app's URL offline, so confirm wi
- `set\_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. Valet calls the endpoint's describe operation before saving
- `set\_env\_vars`: Set environment variables on an app or agent, as name to value. A secret, the default, is encrypted and never shown again; pass secret false for plain configuration, which is readable from the dashboard. A value given here passes through this conversation, which is a real cost and the user's call: s
- `set\_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 recalls its memories in later conversations; a pinned memory is
- `set\_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 a release that has a finding at or above that severity, or th
- `set\_service\_access`: Set who can reach a website, app, 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 shared visitor password. Pass kind to say which you mean; a name hold
- `share\_service`: Share a website, an app, or a skill with specific people by email, whatever its access mode — sharing does not change who else can reach it. Each address is mailed a link from Valet that opens it; the recipient needs no Valet account of their own, only the link, so anyone holding the email can open
- `unset\_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 references, or one a resource set, is refused: the answer names the ho
- `unshare\_service`: Revoke people's shares of a website, an app, or a 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 first. An address with no share is reported, no

Measured by MCP Station. Methods: https://mcpstation.net/methods.html · Terms: https://mcpstation.net/terms.html