Connecting Claude, Cursor and other AI assistants (MCP)

Roiva can answer questions inside the AI assistant your team already uses. Connect Claude Code, Cursor, or another client that speaks the Model Context Protocol (MCP), and it can look up your initiatives, costs, approved value, and ROI while you work ("Which of our initiatives are live, and what's the ROI on each?"), with a link to the initiative or page in Roiva where it found one.

What it can and can't do

• It reads initiatives, costs, approved value, ROI, and the status of your integrations.
• It can also read Roiva's help articles and each platform's setup guide, so it can answer how Roiva works or how to connect a platform from Roiva's own instructions. It can also search your account the way the search at the top of the page does: initiatives, pages, metrics, connections, vendors, people, templates and help articles.
• It can't change anything in Roiva. Recording costs, approving value, and moving initiatives through their stages stay in Roiva itself.
• Value counts only approved entries, the same as on the ROI dashboard. ROI covers all time unless you name a period ("ROI over the last year"), also as the dashboard does.
• Every lookup it makes is recorded in your audit log.

Organization Settings → MCP Access lists exactly what a connected assistant can read.

Who can set it up

MCP access is included on paid plans. An account Owner or Admin issues a token. The token reads what any member of the account can see, whatever the role of the person who issued it, and stops working if they leave the account.

Set it up

1. Open Organization Settings → MCP Access. Organization Settings is in the menu under your name at the bottom of the sidebar.
2. Under Issue a token, give it a name you'll recognize later, such as "Claude Code on my laptop", and how many days until it expires (90 unless you change it, up to 365). Then choose Issue.
3. Copy the token right away. Roiva keeps only a one-way fingerprint of it and can't show it again.
4. Add Roiva to your assistant:
   • Claude Code: run the claude mcp add command shown with your new token.
   • Cursor: paste the JSON shown with your new token into your mcp.json.
   • Another MCP client: point it at the server URL shown on the page, and send the token as Authorization: Bearer <token>.
5. Ask it something, such as "What's our portfolio ROI over the last year?"

Revoking a token

On Organization Settings → MCP Access, choose Revoke next to the token. An Owner or Admin can revoke any token in the account, not only their own. Any assistant using it is cut off on its next request. A token also stops working when it expires, when the person who issued it leaves the account or can no longer sign in, or if your plan no longer includes MCP access.

Where your data goes

The answers Roiva returns go to your assistant and its AI provider, under your organization's own agreement with that provider. Roiva doesn't choose or control it, so check that your agreement covers this data before you connect. The AI transparency page has more detail.

Troubleshooting

• 401 Unauthorized: the token is missing, wrong, expired, or revoked, or the person who issued it has left the account. An Owner or Admin can issue a new one on Organization Settings → MCP Access.
• 403 Forbidden: your plan doesn't include MCP access.
• 429 Too Many Requests: the assistant is calling Roiva faster than the rate limit allows, which is 120 requests a minute for each token. Wait a minute and try again.