The MCP server
Connect Claude, ChatGPT, or any MCP-capable assistant to your RankYak account.
The Model Context Protocol (MCP) is an open standard that lets an AI assistant connect to outside tools and act through them. RankYak hosts an MCP server, so an assistant you already use, such as Claude, may read and manage your RankYak sites from its own chat: looking up keywords, scheduling articles, or publishing changes, without you opening the app.
Connecting a client
The server is available at https://rankyak.com/mcp. Any MCP-capable client may connect; add the URL wherever your client configures remote MCP servers, typically under connectors or integrations in its settings. The URL is all RankYak needs. You may also find these instructions on the MCP page in your site settings.
The first time the client connects, it opens a RankYak page in your browser. Sign in if you are not already, review the request, and click Authorize; the window closes on its own and the client is connected. There is no API key to create or paste. The authorization is granted to that specific client, and you may repeat the flow on as many clients as you like.
ChatGPT
Open Settings, then Connectors, and enable Developer mode under the advanced settings; custom connectors require a paid ChatGPT plan. Then click Create, name the connector RankYak, paste the server URL, and save it. ChatGPT opens the authorization page the first time it connects.
Claude
Open Settings, then Connectors, on the claude.ai website or in the desktop app, and click Add custom connector. Name it RankYak, paste the server URL, and click Add; the authorization page opens once the connector is added.
Claude Code
Run the following command in your terminal:
claude mcp add --transport http rankyak https://rankyak.com/mcp
Then run /mcp inside Claude Code and pick RankYak to authorize the connection.
Cursor
Open Cursor Settings, then MCP, and click Add new MCP server. Alternatively, add the server to your mcp.json file:
{
"mcpServers": {
"rankyak": {
"url": "https://rankyak.com/mcp"
}
}
}
Cursor asks you to authorize the connection the first time it connects.
Other clients
Any client that supports remote MCP servers may connect the same way: add the server URL where the client configures connectors or integrations, and authorize when the RankYak page opens. If the client asks for a transport type, you should choose HTTP.
What a connected assistant may do
A connected assistant receives the same tool set as the copilot inside the app, so it works with your account through the same actions and the same checks. A few abilities remain copilot-only, such as proposing inline edits in the editor and searching your past copilot conversations.
| Area | What the assistant may do |
|---|---|
| Sites | List your sites and update site settings, including the article schedule, automation toggles, image options, and the Developer zone (article feed, API access, webhook). |
| Performance | Read the site's search impressions and clicks from Google Search Console, which keyword clusters are already covered by an article or a ranking page, how well each money page is linked from your own content, and backlink counts. |
| Topics and clusters | Read the topical map: topics, the keyword clusters under them, and the keywords inside each cluster. Add keywords, star or archive them, archive or restore a whole cluster, and archive or restore topics. |
| Keyword research | Start a research run from a description of the business, read what a run proposes, reject the clusters that do not fit, and approve the rest. |
| Content plan | Read the calendar, plan a keyword on an upcoming date, swap the keyword a slot holds, move a planned article to another date, remove a planned article, and regenerate the plan. |
| Articles | Read articles, their research, and their SEO analysis; edit an article's title, text, meta title, and meta description; record feedback; browse or restore revisions; generate a new header image or pick one from the site's image library. |
| Publishing | Publish an article, push edits to your connected platform, deliver an article to your webhook, or record the URL where you published an article yourself. |
| Site Guard | Choose the pages Site Guard checks, review the findings, and generate, apply, or dismiss fix suggestions. |
| Money pages | Create, update, and delete money pages, and accept or dismiss the pages RankYak suggests. |
| Integrations | Connect WordPress, Webflow, Duda, Ghost, Lovable, Replit, or Next.js, list the collections, authors, categories, or sites the platform offers, finish the integration's setup, disconnect an integration, and manage the Google Search Console property. |
| Organizations | See an organization's members, invite new ones or cancel pending invitations, rename an organization, and check what each site costs and what it may do. |
| Help center | Search and read the help center, so the assistant answers questions about RankYak from the documentation. |
The same mechanics apply as in the app. Every article comes off the content plan and is written on its scheduled date, so an assistant asked for an article will add the keyword and put it on the first available day; asked for one sooner, it moves the item to an earlier day rather than writing outside the calendar. An edit the assistant makes to an article is saved with a revision, so you may restore the earlier version, and it reaches your website when the assistant publishes the changes or when you click Publish changes. Until then, automatic republishing skips that article, so an edit never goes live before you publish it. Shopify connects through a custom app that you install in a Shopify window, and Wix and WordPress.com connect through their own sign-in flows, so those integrations may only be set up in the RankYak app.
What stays in the app
Billing and subscriptions, including adding Site Guard to a site, are handled only in the RankYak app, as is deleting sites, organizations, or members, and regenerating a site's API key. A connected assistant knows this and will direct you to the right page rather than attempt it.
Access and expiry
An authorization is tied to your user account, so a connected assistant sees exactly the organizations and sites you may access yourself. While the client is in regular use, its access renews automatically. An authorization that goes unused for thirty days expires, and the client will ask you to authorize again the next time it connects. To disconnect an assistant sooner, remove the RankYak server from the assistant's own settings; RankYak does not currently list connected assistants in the app.
If you would like to build your own integration rather than connect an assistant, see the API.
Still need help?
Ask the copilot inside RankYak for an instant answer about your own account, or send us an email and a human will get back to you.