Point your assistant at one address, approve it once, and it can run scans, read the results and draft proposals in your workspace without you opening the app.
Signed in with OAuth, scoped to one workspace, spends that workspace's credits.
find_leads starts a scan, check_status follows it, list_results reads what it found, find_contact works out who to email there, verify_email proves the address is deliverable, and generate_proposal writes the document. That is the whole prospecting loop from inside a conversation.
The connection is scoped to one workspace. Everything the assistant does happens on your account, with your data and your credit balance, and shows up in the app exactly as if you had done it by hand.
The assistant you already work in becomes the front end. Ask for leads in a market, get the list back, and ask for the proposal, without switching windows.
Add it as a custom connector in the Claude app, as an MCP server in Claude Code, or as a developer mode connector in ChatGPT. There is no key to generate and nothing to paste into a config file.
The assistant sends you to SellSEO to sign in and approve the connection. That approval is what decides which workspace it can see, and you can revoke it from Integrations at any time.
Ask for leads in a niche and a city, follow the scan, read the results and generate a proposal, all without leaving the assistant.
MCP is the protocol assistants use to call external tools. SellSEO exposes one authenticated endpoint that speaks it, so an assistant like Claude can call SellSEO functions directly instead of you copying data between a chat window and the app.
Six things: start a lead scan for a niche and city, check the status of a running job, list the businesses a finished scan found with their scores, find the contact address and phone for one of them, verify that an address is deliverable, and generate a proposal. It cannot send anything, change your settings or touch your billing, and nothing more destructive is exposed.
Yes. A scan started through the endpoint is a scan, and it spends the same credits at the same rate as one you start in the app: five or more per scan, one per contact found and only when a verified address lands, and the usual cost per proposal. Caps work the same way, so you can bound what an assistant is able to spend.
With OAuth. The assistant never holds a password or a key you typed; it gets a token only after you sign in and approve it on a SellSEO screen, that token is scoped to one workspace, and disconnecting the app on the Integrations screen kills it immediately.
The Claude desktop, web and mobile apps as a custom connector, Claude Code as a standard MCP server, ChatGPT in developer mode, and anything else that speaks MCP over HTTP. They all use the same address and the same sign in.
Yes. Anything the assistant does is a normal action in your workspace. Scans appear in Lead Finder, businesses land in your pipeline, and proposals are editable in the app like any other.
Run one scan on your own niche tonight and see who in your city is bleeding search traffic. If the audit reports do not impress you, you have spent nothing.
25 trial credits, no card.