Set up Verb from VS Code

1. Connect it

Paste this into VS Code. It adds the server for you, then tells you to restart.

Install the Verb MCP server for me: add  {"servers":{"verb":{"type":"http","url":"https://app.askverb.com/api/mcp"}}}  to .vscode/mcp.json. It signs in with OAuth in the browser, so there is no token to store; keep every other setting as it is, then check that "verb" is listed. STRICTLY ASK ME TO REFRESH, OR CLOSE AND REOPEN THE SESSION, FOR THE MCP TO APPLY. Do not claim Verb's tools are available in the current session, even if the server shows as connected. Only ask me to step in earlier if a permission you need is blocked.

VS Code keys servers under servers, not mcpServers, and a remote server needs type set to http.

2. Restart, then sign in

Close and reopen the session, or reload VS Code: servers load when a session starts, so Verb is not there in the session you added it from. The first time it is used, a browser tab opens. Sign in with the same email code as the dashboard and choose Allow.

3. Ask for what you want

• “Add Verb to this app.”
• “Check my verb.md and import the tools to the test site.”
• “Switch on the tools for invoices, and leave deleting off.”
• “Give me the script tag for the test site.”
• “Add app.example.com as a domain and take the site live on it.”
• “Where does my Verb site stand?”

With the agent skill installed, VS Code writes the verb.md from your code, so "add Verb to this app" is enough to start.

What it asks first, and what it cannot do

Taking a site live on a domain and turning on real actions each happen in two steps: the first changes nothing and says exactly what will happen, and it only goes ahead once you say yes. It cannot read your users' conversations, delete or archive a site, or do anything the dashboard would not let you do. Full details are in the MCP docs.