Set up xSeek with your AI assistant.
Connect the assistant you already use. It reads your site, drafts your setup in the chat, and saves it when you say yes.
How it works
3 stepsYou have explained your company to your assistant many times. Connect xSeek once and it builds your setup from that, in one conversation.
Connect
Add xSeek to your assistant with one address, then sign in on xSeek and pick your workspace.
Ask
"Set up xSeek for my company." It reads your site and drafts your brand, competitors, audiences and the questions to track.
Approve
Fix anything in the chat and say yes. It saves the draft and starts your first run.
Connect your assistant
Pick your assistant. ChatGPT and Claude take the xSeek address, Cursor and VS Code install in one click, and Claude Code takes one command.
- 1In ChatGPT, open Settings, then Apps and Connectors.
- 2Click Create. If you don't see it, turn on developer mode under Advanced settings first.
- 3Name it xSeek, paste the xSeek address and pick OAuth.
- 4Sign in on xSeek and pick your workspace.
Custom connectors depend on your ChatGPT plan and workspace settings. If you can't add one, use another assistant or set up in the browser.
Other coding agents
Then run codex mcp login xseek to sign in.
Adds xSeek to the coding agents it finds. Or add a remote MCP server with the address https://www.xseek.io/api/mcp.
No skill or plugin needed
The xSeek server ships its own instructions: your assistant receives the setup steps the moment it connects. Assistants that list server prompts also show setup_xseek ("Set up xSeek"), which starts the same steps in one click. In Claude Code it is /mcp__xseek__setup_xseek.
The xSeek plugin for Claude Code is optional. It adds the same server plus two skills, one for setup and one for working with your visibility. Agents can also read the public guide at agent-instructions.md. Running a script or a CI job instead? Create a key with only the permissions it needs in API Keys.
What your assistant can do
The same setup as the browser, from one sentence. Your assistant shows you the whole draft in one message and saves nothing until you say yes.
Set up your account
- Add your website and read it to draft the rest
- Save your brand profile: name, what you sell, market, language and brand voice
- Save your competitors, with the names AI engines use for them
- Save your audiences and the topics they ask about, each with the country the engines are asked from
- Add notes about your company that your website does not say
- Suggest the questions to track with xSeek's own generator, and save the ones you keep
- Start the first run: AI engines answer your questions, then xSeek builds your action plan
Change it later
- Edit or remove an audience, a topic or a note
- Change the market a topic is asked from, or keep a topic out of your score
- Add or remove tracked questions
Connect your tools
- Give you the link to connect Google Search Console and Analytics, and pick the Analytics property
- In a coding agent like Cursor or Claude Code: install the AI bot tracking snippet in your site and check it works
- Check your llms.txt and how readable your pages are for AI
Work with your results
- Read your visibility score, cited sources and dashboard
- Go through your action plan: mark actions done, dismiss or assign them
- Draft articles in Content Studio
- Give you the link to pick a plan, when you want daily tracking
What still needs you
Four moments stay with you, on purpose.
- Your yes. The save tools write on call, so your assistant asks before it saves.
- Google. Your assistant gives you a link. Google asks you, not your assistant, and only an owner or admin of the workspace can connect it.
- Payment. Your assistant gives you a link to the billing page. You pick a plan and pay there, in your browser, never in the chat.
- AI bot tracking. It goes in your site code. A coding agent in your site's repository can install it, or your developer can.
Permissions and sign-in
Your assistant never sees your password. The first time it calls xSeek, your browser opens xSeek's own sign-in page. You sign in (or sign up), pick the workspace it may reach, read the permissions and click Allow.
What it asks for
When your assistant does not ask for specific permissions, xSeek grants this set:
- Read websites, scores, subjects, sources, and opportunities
- Add tracked websites
- Change website settings
- Read tracking prompts and sentiment evidence
- Add tracking prompts
- Change tracking prompts
- Read articles and brand context
- Create or overwrite Content Studio articles
- Edit your brand profile, competitors, audiences and notes
- Connect Google and set up tracking
Publishing articles to your website stays off unless your assistant asks for it by name, and then the sign-in page shows it before you approve. The sign-in page always lists every permission requested.
The connection stays signed in while you use it. After 90 days without use, your assistant asks you to sign in again.
Disconnect
You can cut the connection from either side, whenever you want.
From xSeek
Open API Keys, then Connected assistants (under Organization in the sidebar) and click Disconnect next to the assistant. It loses access to the workspace right away.
From your assistant
- ChatGPT: Settings, then Apps and Connectors, then remove xSeek.
- Claude: Settings, then Connectors, then remove xSeek.
- Cursor and VS Code: remove xseek from your MCP servers.
- Claude Code: run
claude mcp remove xseek.
Removing it from your assistant stops the assistant from calling xSeek. To also end the sign-in on xSeek's side, disconnect it in xSeek.
Questions
No. The xSeek server sends its own setup instructions to your assistant when it connects, and you sign in on xSeek instead of copying a key. The xSeek plugin for Claude Code is optional: it bundles the same server with two skills.