Connect an MCP client

RankMeFast exposes a remote MCP endpoint for compatible coding agents, IDEs, and command-line clients that support Streamable HTTP with a custom bearer header. Account defaults and per-key scopes intersect, so you can limit tools, sites, and whether the audit-start action may spend allowance.

Before you start

• A Starter, Pro, or Agency account with MCP access.
• A client that supports remote Streamable HTTP and an Authorization header.

Follow these steps

1. 1

   Create an API key

   Open Account, choose API keys, create a clearly named key, and copy the full value when it appears. RankMeFast shows the secret only once.

2. 2

   Restrict the key

   Optionally limit the key to selected tools, owned sites, and non-spending actions. A key scope can narrow account defaults but cannot override an account restriction.

3. 3

   Set account permissions

   Open the MCP tab, choose the tools and sites allowed for the account, decide whether spending actions are allowed, and save. Disallowed tools are omitted from discovery.

4. 4

   Copy the endpoint and configuration

   Use the Quick start card to copy the environment-derived endpoint and a supported client example. Never replace it with a hardcoded deployment URL from someone else's installation.

5. 5

   Configure Streamable HTTP

   Add the endpoint and `Authorization: Bearer` key to your client's private user settings or secret input. Choose Streamable HTTP, not local stdio or legacy SSE.

6. 6

   Verify and rotate safely

   Restart the client and ask it to run `list_sites`. To rotate, create and verify a new key in every client before revoking the old one.

What you get

• A remote MCP connection using the deployment's public endpoint.
• Effective permissions formed by account and per-key restrictions.
• Immediate key revocation without exposing another account's resources.

Common questions

Related guides