Connecting Rankability to AI assistants with MCP

Connect an MCP-compatible assistant to Rankability's hosted endpoint with OAuth or a scoped API key, then use the current client, content, tracking, optimization, and audit tools.

Connect an MCP-compatible assistant to Rankability's hosted endpoint with OAuth or a scoped API key, then use the current client, content, tracking, optimization, and audit tools.

Rankability hosts a remote Model Context Protocol server. Use it to give an MCP-compatible assistant scoped access to your organization’s Rankability data and actions.

Hosted MCP endpoint

https://app.rankability.com/mcp

No local installation is required. The hosted endpoint supports OAuth access tokens and Rankability API keys that begin with rk_live_.

Connect Claude Desktop with OAuth

1. Open Settings → Connectors → Add custom connector.
2. Enter https://app.rankability.com/mcp and leave the token field blank.
3. Complete Rankability sign-in and consent in the browser.
4. Confirm the active organization and requested scopes before allowing access.

The OAuth token is bound to the organization that was active during consent. Claude refreshes access automatically until you revoke the connected app or authorize a different organization.

Connect Cursor, Windsurf, or VS Code Copilot with an API key

1. Open organization Settings → API keys.
2. Create a key with only the scopes the assistant needs.
3. Add the hosted endpoint and Bearer header to the client’s MCP configuration.

{
  "mcpServers": {
    "rankability": {
      "url": "https://app.rankability.com/mcp",
      "headers": {
        "Authorization": "Bearer rk_live_YOUR_API_KEY"
      }
    }
  }
}

Store the key as a secret. Never commit it or put it in browser-delivered code.

Current tools

The server currently exposes the following tools. Availability depends on the scopes granted to the connection.

Clients and account

• list_clients, get_client, create_client, and create_client_connect_link
• get_credit_balance

Copywriter and Autopilot

• list_content_projects, get_content_project, and get_content_artifacts
• create_content_auto, create_content_stepped, and approve_brief
• create_content_autopilot and get_autopilot_status

Tracking and optimization

• list_reporter_projects, get_reporter_project, get_reporter_summary, and get_notifications
• trigger_scan and optimize_page

Page and site auditing

• page_audit_run, page_audit_get, page_audit_list, and page_audit_delete
• site_audit_run, site_audit_get, site_audit_list, site_audit_cancel, and site_audit_delete

Credits and limits

MCP uses the Agent API’s current 60-request-per-minute paid-plan limit and the same operation-specific credit rules. Read tools do not start metered work merely by returning existing data. Run and write tools can reserve or consume credits; review the assistant’s proposed action and the credit costs reference before approval.

Manage or revoke access

• Manage OAuth clients under Settings → Connected apps. Revoking an app invalidates its access and refresh tokens.
• Manage API-key connections under Settings → API keys. Delete or rotate the key to revoke that connection.

Security

• Use least-privilege scopes.
• Confirm the active organization during OAuth consent.
• Review consequential or credit-consuming actions before approval.
• Revoke connections that are no longer used.

Troubleshooting

• No tools appear: Restart the MCP client, then confirm the endpoint and authentication.
• A tool is missing: Confirm the connection has the corresponding read, run, or write scope.
• Unauthorized: Reauthorize the OAuth client or replace an expired, revoked, or malformed API key.
• Wrong organization: Revoke the OAuth connection, switch to the intended Rankability organization, and authorize again.
• Rate limited: Back off after 429 and use returned rate or quota headers.

Related articles

• Getting started with the API
• Authentication and API scopes
• API credits, rate limits, and errors