SellSEO
An SEO MCP server for Claude and ChatGPT, so your assistant does the prospecting.
Point your assistant at one address, approve it once, and it can run scans, read the results, find contacts and order a video proposal, in the language and market you name, without you opening the app.
Signed in with OAuth, scoped to one workspace, spends that workspace's credits.
AI Integrations, explained in under a minute.
What AI Integrations changes, and why it matters.
Seven tools, one endpoint
find_leads starts a scan, check_status follows it, list_results reads what it found, find_contact works out who to email, verify_email proves the address is deliverable, generate_video_proposal orders the film, and generate_proposal the written version. The whole loop from inside a conversation.
Your workspace, your credits
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.
No new interface to learn
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.
AI Integrations, in three steps.
Give your assistant the address
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.
Approve it once
The assistant sends you to SellSEO to sign in and approve the connection. That approval decides which workspace it can see, and you can revoke it from Integrations at any time.
Work from the conversation
Ask for leads in a trade and a city, follow the scan, read the results and order the video proposal, with the service, language, market and city as optional details, all without leaving the assistant.
AI Integrations, answered.
What is an MCP server in this context?
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.
What can the assistant actually do?
Seven things: start a lead scan for a trade 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, order a video proposal (with the service to sell, the language, the market, the city and notes as optional details), and start a written proposal. It cannot send anything, change your settings or touch your billing.
Does it use my credits?
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. Caps work the same way, so you can bound what an assistant is able to spend.
How is the endpoint secured?
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.
Which assistants can connect?
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.
Will results show up in the app too?
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 yours to open like any other.
One workspace, from the first scan to the booked meeting.
