Connect RankGlide with MCP

RankGlide exposes a remote Model Context Protocol (MCP) server for supported AI clients. MCP access is available to a workspace only when its active plan enables it; the current product UI identifies this as a Business feature.

Before connecting

You need:

• a RankGlide account with access to the target workspace;
• an active workspace plan with MCP access;
• an MCP client that supports remote HTTP servers and browser-based OAuth authorization;
• an Owner, Admin, or Member role for read access. Write scopes are offered only to Owners and Admins.

Find the endpoint

Open the workspace, go to Settings, and find Remote MCP. Copy the endpoint displayed there. It uses the RankGlide portal host and ends in /mcp.

Add this endpoint as a remote MCP server in Codex, Cursor, Claude, or another OAuth-capable client. Client interfaces differ, so choose its option for adding a remote server URL rather than a local command. Do not paste RankGlide passwords or tokens into the client configuration.

Authorize a workspace

On first connection, the client opens RankGlide in your browser. Sign in if needed, select the workspace, review the client name and requested permissions, and authorize only the access you expect. Each authorization connects one client to one workspace.

RankGlide supports these scopes:

Members can authorize read scopes. logos:write, project:create, projects:write, rows:write, and visualizations:write require the connected user to be a workspace Owner or Admin. Existing connections must be authorized again before they can receive a newly added scope.

Available tools

Read tools can return workspace context, list projects, inspect a project schema, list project rows in pages of up to 50, list project visualizations, and retrieve view or embed analytics.

Project-tag tools return the complete ordered catalog with stable keys, English and Czech labels, and the selected state for one project. Updates replace the complete tag list with zero to five unique catalog keys and require projects:write approval; an empty list removes every tag. MCP project creation can include the same optional tag-key list in its existing creation approval.

Write workflows never create a project or append rows from the initial request alone. The client first stages and validates the operation, then returns a RankGlide approval URL. Open that URL, review the normalized summary or row preview, and approve it in RankGlide. The approval expires after 30 minutes. The client can execute an approved operation exactly once and check its status.

MCP row imports accept CSV or structured rows, use the project's existing schema, append rather than replace data, and reject invalid input. The serialized request is limited to 750 KB; the normal row-count limit also applies. Values for calculated columns are ignored and computed by RankGlide.

Item-logo tools list exact and inherited logo status for a project frame and stage batches of 1–50 public HTTPS PNG or WebP URLs. RankGlide validates and normalizes each image before approval, rechecks its content during execution, and applies the logos from the selected existing frame onward. Only explicitly selected project visualizations have logo display enabled.

get_visualization_flag_context, prepare_visualization_flag_update, get_visualization_flag_update_approval, and execute_visualization_flag_update inspect eligible Text columns and stage selection or removal of a flag column. Values are trimmed, matched case-insensitively against RankGlide’s bundled two-letter country codes, and replace item logos for that visualization. MCP project creation can set the same optional flagColumnKey role.

Visualization-branding tools return the effective project logos as image content together with the selected visualization’s current canvas header, canvas background, playback, attribution, and loading presentation. The client can make the canvas-header band transparent; edit every loading-screen setting; edit the attribution name, four-side padding, maximum logo height, shadow visibility, colors, and background; edit every playback-button setting; edit a progress bar’s name, track thickness, thumb size, and colors; set playback bar and tooltip border widths; derive an accessible palette; and stage exact color changes. A zero-pixel width removes a border without discarding its configured color. The client can also replace the complete ordered layer stack for the canvas, loading screen, or attribution strip, including solid and gradient layers, direction and balance, opacity, and visibility. The first layer is topmost, and omitting an existing layer removes it. Legacy color patches continue to preserve every non-color setting. Because these assets can be shared, the approval page lists every affected visualization; execution is atomic and rejected if the assets changed after preparation.

Canvas-tooltip tools can list every tooltip in a project, inspect all visualizations using one tooltip, and stage partial changes to its name, colors, border width, four-corner radius, and four-side padding. Approval shows the complete current and proposed appearance plus every affected visualization. Execution is rejected if the tooltip or its shared-use list changed after preparation.

Canvas-header tools can list every header in a project, inspect its eligible subtitle columns and all visualizations that share it, and stage partial changes to its name, background color or transparency, four-side padding, content gap, logo variant, and subtitle column. Approval shows the complete current and proposed appearance plus every affected visualization. Execution is rejected if the header, eligible columns, or shared-use list changed after preparation.

Playback-control tools can list every control in a project and edit every field available on its detail page: name, four-side padding, linked button, progress bar and tooltip, control gap, bar colors, border width, and four-corner radius. The selected button and progress bar are checked for compatible sizes before approval. Approval lists every affected visualization, and execution is rejected if the control, selected basic assets, or shared-use list changed after preparation.

Usage, limits, and revocation

Workspace Settings → Remote MCP shows active client connections and usage for the last 7, 30, or 90 days, including calls, errors, transferred bytes, and approved writes. Service security and abuse rate limits still apply even when there is no monthly MCP quota.

Revoke any connection you no longer recognize or use. Revocation invalidates that client's RankGlide connection; remove the server from the client as well if appropriate. Authorize again to create a new connection.

Troubleshooting

• Business plan required: confirm the selected workspace has an active plan with MCP access.
• Authorization does not open: verify that the client supports remote MCP OAuth and that the copied endpoint ends in /mcp.
• Requested write scope is missing: connect as a workspace Owner or Admin.
• Approval unavailable or expired: stage the operation again and approve it within 30 minutes.
• Rows are rejected: compare the input with the project's current column schema and correct every validation error.
• Rate-limit response: wait before retrying and reduce repeated or concurrent calls.
• Wrong workspace: revoke the connection and authorize the intended workspace as a new connection.