Wiv

ai.wivPublished by wiv.aiOfficial publisherv5.0.1Updated Oct 24, 2026

Automate FinOps workflows, cases, and cloud ops via the Wiv Workflow API.

VerifiedStreamable HTTPWeb executableCloud & InfrastructureFinance

Overview

AI-generated overview

Wiv is a remote MCP server that lets an assistant automate FinOps workflows, cases, and cloud operations through the Wiv Workflow API.

What you can do
Wiv exposes the Wiv Workflow API to an assistant over a remote streamable HTTP endpoint. According to its registry description, it is meant for automating FinOps workflows, cases, and cloud operations. No individual tools are listed in the supplied manifest, so the exact operations available are not documented here.
When to use it
Consider it when an assistant needs to drive FinOps or cloud operations work, such as handling cases or running workflow steps, from a hosted endpoint rather than a locally installed package.
Requirements
A remote MCP endpoint at over streamable HTTP. The manifest declares no authentication, environment variables, headers, or packages, so no credentials are documented; network access to the endpoint is required.
Before you install
The manifest declares no authentication, so it is unclear how access to the endpoint is controlled or who can invoke it. The description mentions automating workflows and cases, which may change or act on cloud and financial operations data; confirm what the tools actually do and what data leaves your environment before connecting.

Installation

In SourceWeft

  1. Open Wiv 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.wiv%2Fmcp/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": {
    "wiv": {
      "type": "http",
      "url": "https://mcp.wiv.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. v5.0.1LatestSep 16, 2026

Score

67% 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

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • 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.