Revensi

com.revensiPublished by revensi.comOfficial publisherv1.0.0Updated Oct 25, 2026

Connect your AI assistant to Revensi OS agents, workflows, and business data.

VerifiedStreamable HTTPWeb executableProductivity & WorkflowKnowledge & Memory

Overview

AI-generated overview

Revensi connects an AI assistant to a Revensi workspace: published agent blueprints, saved workflows, connector catalog entries and resource metadata.

What you can do
Search and read published agent blueprints, including full specs and Markdown build briefs to adapt to your own systems, without an account for these read tools. List and inspect saved workspace workflows with their maps, effort, scores and open questions. List unanswered or deferred questions and blockers from active workflows. Browse the connector catalog and see which workflow maps mention each service. List metadata for files in the resource library, without document bodies. Create a draft workflow or a catalog connector entry, and remove a named connector or resource after confirmation.
When to use it
Useful when you want an assistant to look up Revensi agent blueprints or to read and lightly manage a Revensi workspace: comparing saved workflows, tracking open questions, or checking which connectors and resources exist.
Requirements
A remote endpoint at app.revensi.com over streamable HTTP. The published blueprint tools need no account or authentication; the workspace tools act on a Revensi workspace, so expect that workspace to be available to the connection.
Before you install
Some tools write: add_workflow creates a draft, add_connector adds a catalog entry, and remove_connector and remove_resource delete entries after confirmation. Removing a resource deletes its library copy and searchable chunks, though historical workflow quotations may remain. Connector entries are catalog records only and do not connect or grant access to external accounts, and blueprint tools return specifications, not running agents.

Installation

In SourceWeft

  1. Open Revensi in the dashboard and add it to a workspace.
  2. 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/com.revensi%2Frevensi/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.

{
  "mcpServers": {
    "revensi": {
      "type": "http",
      "url": "https://app.revensi.com/mcp"
    }
  }
}

Tools

12

search_agents

Search public agent blueprints

Search Revensi's free published agent blueprints by task, department, system or integration. No account or authentication is needed. These are specifications and fictional examples, not connected or running agents.

Parameterslimitquerycursorsystemtriggerdepartment

get_agent

Get a public agent blueprint

Read the full published blueprint, including inputs, outputs, tools, context, deliverables, review boundaries, evaluations and fictional examples. No authentication needed. Does not execute an agent or grant access to external systems.

Parametersslugrequired

get_agent_spec

Get an agent build brief

Get a published agent's Markdown build brief to adapt to the user's systems. No authentication needed. This returns a specification; it does not create, connect or run the agent.

Parametersslugrequiredhandoff

list_workflows

List Revensi workflows

Use this when the user wants to find or compare saved workflows in their Revensi workspace. Returns live workspace data, not an interview transcript.

Parameterslimitquerycursorstatusdepartment

get_workflow

Get Revensi workflow

Use this when the user wants one saved workflow's map, effort, scores, and open questions. Never returns the interview transcript.

ParametersworkflowIdrequired

list_workflow_questions

List workflow questions

Use this when the user wants unanswered or deferred questions and blockers from active, non-archived Revensi workflows. This tool does not answer them.

ParameterslimitquerystatecursorprioritydepartmentworkflowId

list_connectors

List workflow connectors

Use this when the user wants named services in the Revensi connector catalog and which workflow maps mention them. These are catalog records, not authenticated external accounts.

ParameterslimitquerycursorworkflowId

list_resources

List workflow resources

Use this when the user wants metadata for files saved in their Revensi resource library. Does not return document bodies.

Parameterslimitcursor

add_workflow

Save a new workflow draft

Use this only after the user reviews and approves a complete conversation-drafted workflow. Creates one draft; it does not publish or run the workflow.

ParametersmaprequirednamerequiredoriginrequiredperiodpurposerunUnitfrequencyrequestIdrequireddepartmentminutesPerRunopenQuestions

add_connector

Add a connector catalog entry

Use this when the user wants to name an external service in Revensi's connector catalog. This does not connect an account or grant access.

Parametersnamerequiredcategory

remove_connector

Remove a connector catalog entry

Use this only after the user clearly asks to remove the exact named catalog entry. Refuses entries still referenced by any workflow; does not disconnect external accounts.

ParametersconfirmNamerequiredconnectorIdrequired

remove_resource

Remove a resource file

Use this only after the user confirms the exact named resource. Deletes its library copy and searchable chunks; historical workflow quotations may remain.

ParametersresourceIdrequiredconfirmNamerequired

Version history

1
  1. v1.0.0LatestSep 16, 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 listedRequired15 pts
  • 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.