Account, plan & data

Connect Rivly to Claude, ChatGPT or Cursor

Enter the address https://mcp.rivly.de in your assistant, sign in to Rivly, choose the projects and permissions. After that your assistant reads the values of your projects straight from Rivly, without an export and without copying. The server is in Germany.

How the connection works

Claude, ChatGPT, Cursor and Claude Code need nothing but the address https://mcp.rivly.de. When you connect for the first time, a Rivly page opens: you sign in, choose the projects and permissions and click “Allow”. Only your own agents, for example in n8n or Make, need a key.

  1. “Read only” is enough for analyses and text drafts. “Read and write” additionally lets the assistant tick off steps of a recommendation and add to the measurement plan.
  2. “All projects, future ones included” gives the assistant every project you can open in Rivly, including those added later. With “Selected projects” you choose single ones. In the conversation you name the project by its name or domain, without it the assistant takes the default project.
  3. Team members connect their own assistant as well. It may never do more than their role: whoever may only read connects with “Read only”.
  4. You can change projects and permissions later in the “MCP & agents” tab with “Edit” on the connection, without signing in again in the assistant.

Claude

The quickest way is “Add to Claude” in the “MCP & agents” tab: Claude opens the custom connector dialog with name and address filled in. Without the button, open the connectors in Claude (under “Customize”), click “Add”, choose a custom connector and enter Rivly as the name and the following line as the address. Keep the detected sign-in settings as they are. Then click “Connect” and sign in to Rivly. The connection then works in Claude on the web, in the desktop app and on the phone. The free Claude plan allows one custom connector, in Team and Enterprise accounts the owner adds it for everyone.

https://mcp.rivly.de

ChatGPT

On chatgpt.com/plugins, use the plus sign to add a custom MCP server. Name Rivly, the following line as the server address, OAuth as the authentication. Confirm the note about unverified servers, create and install it, then sign in to Rivly. In a chat you call Rivly with @. OpenAI decides which plans allow custom MCP servers, in company accounts the administrator often decides.

https://mcp.rivly.de

Cursor

“Add to Cursor” in the “MCP & agents” tab adds the server to Cursor directly. By hand, add a new server under Settings in the MCP section, or create or extend the file mcp.json in the folder .cursor of your user directory with the following entry. On the first call Cursor opens the Rivly sign-in.

{
  "mcpServers": {
    "rivly": { "url": "https://mcp.rivly.de" }
  }
}

Claude Code

Run the command in the terminal, with --scope user Rivly is available in every folder. Then type /mcp in Claude Code, pick rivly and sign in to Rivly.

claude mcp add --scope user --transport http rivly https://mcp.rivly.de

Your own agent

Your own agent, n8n or Make signs in with a key. The key applies to one project. The account owner creates it under Settings in the MCP & agents tab under “Own agent”: choose the project and the permissions, click “Create key” and copy the key right away. It starts with rv_live_, has 48 characters and is shown in full only once. After that Rivly shows a shortened form with dots in the middle, which is not a key. If you no longer have it: “Create new key”. The call below lists the tools and thereby checks whether the key works.

curl -X POST https://mcp.rivly.de \
  -H "Authorization: Bearer <YOUR-KEY>" \
  -H "Content-Type: application/json" \
  -H "Accept: application/json, text/event-stream" \
  -d '{"jsonrpc":"2.0","id":1,"method":"tools/list"}'

What the agent can do

Twenty-nine tools are available, twenty-one for reading and eight for writing. Each takes the project as an argument, list_projects names the projects of the connection, get_portfolio shows them all at a glance. The writing ones work only with the right “read and write” and only in projects where your role allows changes. If the connection reaches several projects, the assistant names the project explicitly for a change.

  1. list_projects (read): projects of this connection with ID, domain and rights, plus the default project.
  2. get_overview (read): Rivly Index, channel values and the “In short” of the current week.
  3. get_ai_answers (read): AI answers word for word per buying question and system, with sources.
  4. get_rankings (read): Google positions, Google AI Overview and search volume per term.
  5. get_competitors (read): competitors with values from all four channels.
  6. get_recommendations (read): open recommendations with steps, points and status.
  7. get_core (read): profile, offer, search queries with volume, buying questions and competitors with the reason they were added, from the core of the project.
  8. get_map (read): market map of the plan: fields with status, demand, leader and own page, plus the measures with their id.
  9. get_site_audit (read): Website and pages: technology, sitemap, llms.txt, access for AI providers and page potential.
  10. get_page_brief (read): page brief for a measure or a field: heading, sections, customer questions, schema and llms.txt line.
  11. get_llms_txt (read): draft of the llms.txt with the pages of the core, plus the lines for pages that are not online yet.
  12. get_structure (read): structure of the website against demand: demand without a page, pages not on place 1 and topics without demand.
  13. get_live_check_history (read): History of the AI Live Check: questions with the answers of ChatGPT and Gemini, source app or MCP, rest of the weekly quota.
  14. get_ads (read): Ads channel: active ads of the brand and its competitors from Meta and Google, with themes and winners.
  15. get_press (read): Press channel: editorial articles of the last 30 days, share of coverage and media that name only competitors.
  16. get_backlinks (read): Backlinks: linking domains against the competitors, strong links, gaps and missing directories, collected monthly.
  17. get_business_profile (read): Google Business: own listings checked against the website, place in Google Maps and reviews.
  18. get_history (read): History per calendar week: Rivly Index and the channels GEO, SEO, ads and press, plus events such as a new measurement basis.
  19. get_measure_plan (read): Measurement plan: which buying questions and search queries Rivly measures regularly, with the last result and free slots in the tariff.
  20. get_keyword_topics (read): focus queries by topic and by ranking page, each group with demand, places in the top 10 and target page.
  21. get_portfolio (read): every project of this connection at a glance: Rivly Index with its change, the four channels and the next step per project.
  22. update_recommendation (write): tick off a step, schedule it or report it as done.
  23. add_prompt (write): add a buying question or search query to the measurement plan.
  24. check_page (write): check one page of the website right away: reachable, sitemap, linking, search query, schema and llms.txt.
  25. mark_action_done (write): report an active measure as done, the next measurement checks the effect.
  26. ask_live_check (write): Ask ChatGPT and Gemini one question live, with the same weekly quota as the chat in the app.
  27. promote_live_check (write): Take a question from the Live Check into the measurement plan as a buying question so it is measured every week.
  28. create_page_brief (write): Have a new page brief written for a measure or a field, with the same monthly quota as the button in the Fahrplan.
  29. set_keyword_topic (write): sort search queries into a topic or take them out of it, create a new topic and set its target page.

The methodology as a resource

Besides the tools, Rivly provides a description at rivly://methodik of how to read the Rivly Index, the four channels and the measurement weeks. An assistant that supports resources can read it before the first analysis and then does not misread the numbers.

Example: building a page

This is how an assistant with the right “read and write” turns a measure from the Fahrplan into a finished page. You say, for example: “Take the first open measure from the Fahrplan, fetch the page brief and build the page. Then check it and report the measure as done.”

  1. get_map: the assistant reads the Fahrplan and picks a measure. If none is active yet, it sets one to “in progress” with update_recommendation.
  2. get_page_brief: it fetches the page brief with heading, sections, customer questions, schema and llms.txt line. If there is none yet, create_page_brief has it written. After about a minute it appears in get_page_brief.
  3. The assistant builds the page. With access to the code of your website, for example in Cursor, it creates the page right there.
  4. check_page: after publishing it checks the page right away: reachable, sitemap, linking, search query, schema and llms.txt.
  5. mark_action_done: it reports the measure as done. The next measurement checks the effect.

Security

A connection applies to the chosen projects and permissions, a key to exactly one project. Other projects stay out of reach. An assistant may never do more than the person who connected it: whatever their role may not do, Rivly also refuses through MCP. When their access to a project ends, it ends for the assistant at the same moment.

Every query is logged, with time, tool and assistant. Rivly does not store the wording of the queries and answers. To prevent misuse, the IP address of a query stays in the log for 90 days, after that Rivly deletes it.

When an assistant signs in, Rivly stores the name it gives and the address it returns to. Access is valid for an hour at a time and renews itself as long as the assistant uses it. Without use it ends after 90 days.

Connected assistants are listed in the “MCP & agents” tab under “Connected assistants”. “Edit” changes projects and permissions of your own connection, “Disconnect” ends a connection immediately. For a key, “Revoke” disconnects every agent with this key, “Create new key” does so as well and hands you the new key with the same permissions right away.

Projects someone shares with you, your agency for example, connect the same way: they appear in the project choice on the Rivly page, and your role in the project decides whether the assistant may write. In the “MCP & agents” tab of a shared project you see the address and your own connections. Keys for your own agents are created only by the owner of the account the project belongs to. The owner also sees your connection and can end your access to the project at any time.

If it does not work

  1. The Rivly page does not open: allow pop-ups for the assistant and start the connection again in the assistant, in Claude and ChatGPT with “Connect” next to the server.
  2. “The return address does not match” or “This request has expired”: start the connection again in the assistant, do not open the Rivly page from a bookmark.
  3. Rivly shows no project: you are signed in with an account without a project. Sign out with “Other account” and sign in with the right one.
  4. Dots in the middle of the key, such as rv_live_ab12cd…9f3a: that is the shortened display, not the key. Agents then report error 401 or “Cannot convert argument to a ByteString”. Create a new key in the “MCP & agents” tab and copy it right after.
  5. Error 401 with your own agent: the key is revoked, replaced or not entered in full. A complete key starts with rv_live_ and has 48 characters. Rivly names the reason in the text of the error message. With a connection by sign-in the assistant renews access itself, if the error stays, disconnect and connect again.
  6. “spawn npx ENOENT” in Claude Desktop: the older setup through mcp-remote needs Node.js. The connectors are the easier way, as described above under Claude.
  7. Error 429: more than 60 queries in one minute per connection or key. The assistant can repeat the query after a minute.
  8. “This connection may only read” or “This key may only read”: the tool writes. For a connection, set the permissions to “Read and write” in the “MCP & agents” tab with “Edit”, for a key switch them in the same tab.
  9. “This project is not part of this connection”: the project is not selected or your access to it has ended. Choose the projects again with “Edit” on the connection.
  10. “Quota reached”: ask_live_check counts like the chat in the app per week, create_page_brief like the button in the Fahrplan per month. Rivly tells the assistant the date from which there is room again. A brief that is already written stays free to open with get_page_brief.
  11. The assistant does not find Rivly: usually the restart is missing. Quit the assistant completely and open it again.

In the app

Set up MCP

See where your brand stands today.

Enter your domain, Rivly recognises the rest. First results in about 30 minutes, 14 days free, no credit card.

Hosted in Germany · official EU DSA data · GDPR compliant