Permissions & consent

The consent page

When your client connects, it sends you to VibeSell’s own page (vibesell.it/oauth/authorize). You sign in there — the client never sees your password — and the page shows:

• who is asking (the app’s name, for example Claude or Codex) and where you’ll be sent back;
• what it will be able to do, and what it will never do;
• the account it will act for, with a Switch link if you are signed in to another one.

You click Allow or Deny. The request expires after ten minutes.

1. Your clientCalls the MCP without a token and gets a 401 pointing to VibeSell's authorization server.
2. VibeSellRegisters the client and sends your browser to the consent page.
3. YouSign in, read the two lists, click Allow.
4. Your clientExchanges the code for a token and starts calling tools.

Two scopes: read and act

Scope	What the app can do	Granted
mcp	Read your workspace — offer, target, plan, campaign; count leads and preview real people without their email; read your sending setup, your prospects’ replies and what waits for your approval.	To every connection.
mcp:act	Also save your offer, your target, your sizing and your email sequences; prepare lead imports, domain orders and campaign launches for you to approve; write to the VibeSell team for you, in your words.	When the client asks for it or names no scope — Claude, Claude Code and Codex get it.

With mcp:act, the consent page says the app will never:

• import leads, buy anything or send an email without your click on the approval;
• pay for a plan — you pay on Stripe, yourself.

With mcp alone, it says the app will never import leads or spend lead credits, buy domains, mailboxes or a plan, or send a single email.

A read-only connection

A connection made with mcp only — a client that asked for nothing more, or one connected before the act tools existed — sees only the read tools. Its tool calls to act tools answer: “This VibeSell connection can only read.” To let it act, disconnect VibeSell in the app and connect it again, then accept on VibeSell’s page.

What an assistant sees depends on the connection

The list of tools (tools/list) is built per connection:

• Act tools appear only to a token that carries mcp:act.
• decide_approval — the tool behind the Approve and Reject buttons — appears only in the Claude app, which hides it from the model. Codex, Claude Code and other clients never receive it: there, you decide cards in the VibeSell app.
• The server instructions say the same: a read-only connection is told it can only read.

“Always allow” in Claude

Claude starts every connector’s tools on Needs approval, so it asks you before each call — read tools included. Once you trust the connection, open Settings → Connectors → VibeSell in Claude and set its tools to Always allow.

This only removes Claude’s own confirmation. Purchases, lead imports and launches still wait for your click on their approval card: that rule is enforced by VibeSell’s server, not by the client.

Disconnect an app

In the VibeSell app, open Settings → Connected apps. Each connected app shows its name, when it was connected, and whether it reads your workspace or also saves your work and prepares approval cards. Disconnect revokes its access and refresh tokens at once; the app has to ask for your consent again to come back.

You can also remove the connector from your client — that forgets the token on its side, while Disconnect in VibeSell guarantees the server refuses it.