# Connect your agent to Sightkick Your user wants you to work in Sightkick, the agentic SEO and GEO platform: you read their AI visibility, Search Console, keywords and pages, and you do the work, each change attributed to you. This connects you to Sightkick's MCP server. About a minute. - Server: https://app.sightkick.so/mcp - Transport: streamable HTTP. Auth: OAuth 2.1 with dynamic client registration, no API key. Name the server "sightkick". - The sign-in opens in your user's browser. They sign in to Sightkick and pick the workspace for their site. - No Sightkick account yet? Follow https://sightkick.so/llms.txt instead: it starts with the account. - A free account (the free AI visibility report, no card) connects the same way, with no trial. Reads work: the report's AI visibility, its prompts and answers, the reports, and Search Console once your user connects it in Settings → Search Console. Everything else waits for the plan: get_workspace says contentEnabled false, and a call that needs the plan answers no_plan. ## 1. Add the server Find yourself below. If you can run commands or change your own config, do it. If you can't, tell your user the steps. ### Claude Code ``` claude mcp add --transport http sightkick https://app.sightkick.so/mcp ``` Sightkick lists its tools without a sign-in and asks for it at your first tool call. When it does, ask your user to type /mcp, pick sightkick and approve the sign-in. If sightkick isn't listed there, restart Claude Code. ### Grok Bot - Ask Grok Bot to add a custom MCP server named Sightkick, and paste the endpoint. - Sign in to Sightkick when Grok Bot asks. ### Codex ``` codex mcp add sightkick --url https://app.sightkick.so/mcp codex mcp login sightkick ``` The first line adds the server and opens the sign-in. If it doesn't, the second does. Codex connects at the start of its next task, and `codex mcp list` shows the server with OAuth. The same server in ~/.codex/config.toml: ``` [mcp_servers.sightkick] url = "https://app.sightkick.so/mcp" ``` ### Hermes ``` hermes mcp add sightkick --url https://app.sightkick.so/mcp --auth oauth ``` It signs in and finds Sightkick's tools. The sign-in needs a terminal: in one without, add the server to ~/.hermes/config.yaml under mcp_servers (url: "https://app.sightkick.so/mcp", auth: oauth), run `hermes mcp login sightkick`, and give it the address the browser lands on after the sign-in. If it says the MCP SDK isn't available: `pip install "hermes-agent[mcp]"`. ### OpenClaw ``` openclaw gateway stop openclaw mcp add sightkick --url https://app.sightkick.so/mcp --transport streamable-http --auth oauth openclaw mcp login sightkick openclaw gateway start ``` OpenClaw adds a server and signs in only while its Gateway is stopped, so the first line stops it and the last starts it again. If you run inside that Gateway, don't run these yourself, since stopping it stops you: ask your user to run them in a terminal, or to add the server in the Control UI instead, where an admin adds it under Settings → MCP (Add server) and signs in with Sign in, with the Gateway running. Open the link the login line prints. If the browser can't get back to it, rerun the login line with --code and the code from the address. `openclaw mcp probe sightkick`, run before the Gateway starts again, lists the tools. ### Muse - Ask Muse to create a custom connector for Sightkick's MCP server, and paste the endpoint. - Sign in to Sightkick when Muse asks. ### Claude (claude.ai or the desktop app) You can't add a connector yourself. Ask your user to: - Open Customize → Connectors. - Choose “+ Add”, then “Add custom connector”, paste the endpoint, and continue to the sign-in. On Team and Enterprise an owner adds it once, in Organization settings → Connectors (Add, then Custom → Web), and each member connects it from Customize → Connectors. ### ChatGPT You can't add a connector yourself. Ask your user to: - In ChatGPT on the web, open Plugins, choose + and then “Add custom MCP server”. - Name it Sightkick, paste the endpoint under Connection and pick OAuth for the sign-in. Tick “I understand and want to continue”, then “Create as a plugin”. - Install the plugin and sign in to Sightkick. In a new chat, type @ to use it. Web only, no Developer mode needed. On Business only an admin or owner can add it. Sightkick's changes need Business, Enterprise or Edu: Pro connects read-only. ### Any other agent Add a remote MCP server at https://app.sightkick.so/mcp, transport streamable HTTP, auth OAuth. ## If Sightkick says no workspace A new account's sign-in can finish before its workspace exists. Then every tool answers that the connection isn't tied to a Sightkick workspace yet. Ask your user to finish setting up at https://app.sightkick.so/start (sign in, confirm the site, start the trial or the plan), then reconnect: run the sign-in again (in Claude Code, /mcp), or remove the server and add it back. ## No browser for the sign-in If you run where nobody can open a browser (a server, a scheduled job, a headless box), ask your user for an API key instead: in Sightkick, Settings → Agents, then New key. Send it on every request as `Authorization: Bearer `. It is a secret: keep it in your environment (SIGHTKICK_API_KEY), out of code, commits and anything you share. With a key you can also skip MCP: the CLI (`npx -y sightkick`, https://sightkick.so/connect/cli.md) and the HTTP API (https://sightkick.so/connect/api.md) run the same tools. ## 2. Check it works Call get_workspace. It returns the workspace, the plan's amounts and what's left this month, each of Sightkick's jobs, what setup still lacks, and whatsNew since your last session. Sightkick's "Connect your agent" popup ticks off when your first call arrives, under your name. ## How the tools work Each tool does one kind of thing. Reads are get_* and take a `view`, changes take an `action`, and each tool's description lists them with their fields. You are a user, as your user is: whatever they can do in the app you can do, at any time, except signing in, entering their first card, ending a trial early (Start my plan now) and deciding who gets access. Sightkick's job settings (Auto, Manual, Off) and its own rules only govern what Sightkick does by itself, and no call asks for a confirm. Actions that delete something, take a page down or send an email are marked destructive. The playbook is in the server's instructions and get_guidance. The same method as skills, if you read skills: seo-geo-skills (https://github.com/fabio-bergmann/seo-geo-skills, `npx skills add fabio-bergmann/seo-geo-skills`) has five SEO and GEO skills that work with no account, and a sightkick skill that says which call does each of their steps. ## 3. Tell your user Say you're connected and to which workspace. Then ask what they want first, or offer one of these: - What changed in their AI visibility this week (get_visibility summary) - Plan next week's pages (get_keywords topics, then schedule_page) - Find sites to pitch for backlinks (get_outreach prospects)