Roiva

ai.roivaPublished by roiva.aiOfficial publisherv1.0.0Updated Nov 7, 2026

AI initiative cost, cash value, freed capacity and ROI from Roiva, with drafts a person accepts

VerifiedStreamable HTTPWeb executableData & Analytics

Overview

AI-generated overview

Remote Roiva MCP server that gives an assistant AI initiative cost, cash value, freed capacity and ROI figures, with drafts a person accepts.

What you can do
  • Retrieve cost, cash value, freed capacity and ROI figures for AI initiatives from Roiva.
  • Work with draft outputs that a person reviews and accepts rather than final records.
  • No individual tools are listed in the manifest, so the exact operations are not documented here.
When to use it
Useful when you want an assistant to pull Roiva's financial view of AI initiatives — cost, cash value, freed capacity and ROI — into a conversation, for example to discuss or sanity-check business cases before a person accepts the drafts.
Requirements
A remote MCP endpoint at app.roiva.ai over streamable HTTP. OAuth authentication is required, so a Roiva account with access to the relevant workspace is needed. No environment variables or headers are declared.
Before you install
Access is granted through OAuth to your Roiva account, so the assistant can see whatever that account can. Outputs are described as drafts that a person accepts, so review them before relying on the figures. No tool list is published, so confirm what the server can read or change before connecting.

Installation

In SourceWeft

  1. Open Roiva in the dashboard and add it to a workspace.
  2. Connect the required credentials. They are stored privately and never shown on public pages.
  3. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/ai.roiva%2Froiva/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config. The client completes OAuth sign-in on first connect.

{
  "mcpServers": {
    "roiva": {
      "type": "http",
      "url": "https://app.roiva.ai/mcp"
    }
  }
}

Tools

0
This server asks you to sign in, so SourceWeft could not read its tools without an account and has not indexed them. What a connected account sees can depend on that account and its permissions.

Version history

1
  1. v1.0.0LatestNov 5, 2026

Score

83% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts
  • LicenseNot applicable

    A hosted service is used under its provider's terms, so no license is expected here. This check is left out of the percentage.