Add Sightkick plugin (marketing/seo) - #13
Open
fabio-bergmann wants to merge 1 commit into
Open
Conversation
Copy link
Copy Markdown
Sorry, something went wrong.
Remote MCP server for AI-search visibility, keyword research, article writing/scoring, publishing and Search Console proof. OAuth 2.1, no API key. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What this adds
Sightkick — a plugin (content/plugins/sightkick.md). An SEO/AEO autopilot with a remote MCP server: AI-answer visibility tracking, keyword research, article writing/scoring, calendar scheduling, CMS publishing, and Google Search Console proof.
Checklist
On G2, honestly
I'm the founder submitting my own tool, so let me be precise about what "works today" covers rather than tick the box flat.
Verified end to end: the MCP server itself. It's live at https://app.sightkick.so/mcp (streamable HTTP, OAuth 2.1 with dynamic client registration), published and active in the official MCP Registry as so.sightkick/mcp, and exercised in Claude Code, Claude desktop and ChatGPT. An unauthenticated request returns 401 — that's the OAuth challenge, not a fault. Discovery card: https://app.sightkick.so/.well-known/mcp/server-card.json. The tool names in the prompt are copied from that card, not from memory.
Not verified: I have not run it inside Grok Bot specifically — I don't have a SuperGrok Heavy / Cursor Ultra seat. Since Grok Bot follows Cursor's existing plugin and MCP policy rather than having its own controls, a standard remote MCP server should connect via AddMcpServer / AuthenticateMcpServer, but I haven't personally watched it happen and won't claim I have. Happy to have that treated as the open question in review, to adjust the install steps if the real Grok Bot flow differs, or to withdraw the PR if an unverified-in-Bot entry isn't something you want to carry.
On G6
The prompt is written to be genuinely operable, not a funnel: it splits free reads from anything that spends money or publishes, and requires the bot to come back and ask before generate_article, publish_article, queue_article, reschedule_article, set_autopilot_mode, track_prompt or retire_prompt. Pricing is stated plainly in pricing_note and agent access isn't upsold — it's included in every paid plan.
Where it came from
Own product. Docs: https://sightkick.so/mcp · machine-readable reference: https://sightkick.so/llm-info · repo: https://github.com/sightkick-so/mcp