Add one address to your AI assistant and work with xSeek in the chat: set up tracking, read your action plan, draft the next article. You sign in on xSeek once. No API key to paste.
One address for every assistant. You sign in on xSeek, no key to paste.
Claude
ChatGPT
Cursor
VS CodeClaude Code>_Codex>_This is the only thing your assistant needs to find xSeek.
Pick yours. Each one names the menu a little differently.
Custom connectors depend on your ChatGPT plan and workspace settings. If you can't add one, use another assistant.
Your assistant opens xSeek in the browser. Sign in, pick your workspace and approve. The consent page lists every permission the assistant asks for.
Paste this sentence. xSeek tells the assistant to read your site, show you a draft, and save it only after your yes.
You never type a tool name. You ask, and the assistant picks the right tools. A few of them, so you know what runs.
It reads your homepage, drafts your brand profile, competitors and audiences, and shows you the draft. After your yes, it saves the questions to track and starts the first run.
Ask“Set up xSeek for xseek.io.”
Your score and its change, the sources AI engines cite, the mention rate per question, and the action plan with who owns each action. Once an action is done, it shows the mention rate before and after.
Ask“What should we publish next?”
It reads your brand voice and notes, then runs the xSeek writer on an action from your plan. The draft lands in Content Studio. Each run uses one article from your monthly quota.
Ask“Write the article for our top action.”
It gives you the one link that connects Search Console and Analytics. A coding agent in your site’s repository can install the AI bot tracker and send a test visit as GPTBot. It also runs the free site checks.
Ask“Is my llms.txt live?”
OAuth 2.1 with PKCE. You sign in on xSeek and pick the workspace. You never paste a password or API key into the chat.
The consent page lists each permission the assistant requests before you approve.
Putting an article on your live site is its own permission. An assistant connection does not get it unless it asks for it by name.
Scores, mentions, citations and actions are written only by xSeek’s own measurements. No tool can set them.
When a plan is needed, the assistant gives you the billing link. Payment never happens in the chat.
In xSeek, under API Keys, Connected assistants: Disconnect revokes every token that assistant holds for your workspace.
MCP (Model Context Protocol) is the standard way AI assistants connect to outside tools. The xSeek MCP server, at https://www.xseek.io/api/mcp, gives Claude, ChatGPT, Cursor and other MCP clients a set of xSeek tools they can call for you.
ChatGPT, Claude on the web and in Claude Desktop, Cursor, VS Code, Claude Code and Codex, plus any client that connects to a remote MCP server over HTTP. In ChatGPT, custom connectors depend on your plan and workspace settings.
No. In ChatGPT or Claude you paste one address and sign in. Only installing the AI bot tracker touches your site’s code, and that step can wait, or go to whoever edits your site.
Not by default. Articles land as drafts in Content Studio, and publishing needs its own permission. The tracker is installed only when a coding agent works in your site’s repository and you let it.
A free workspace gets one first run of up to 25 questions; daily tracking needs a paid plan. Reading your homepage and suggesting questions is capped at 10 calls per workspace per 24 hours. Each writer run uses one article from your monthly quota.
Yes. Add xSeek to ChatGPT, Claude or Cursor, sign in once, and ask it to set up xSeek for your company. It drafts your competitors, audiences and the questions to track, and saves them when you say yes.
The MCP server reference lists the endpoint, the OAuth flow, every tool with the permission it needs, the scopes and the limits.