Profusia AI

ai.profusiaPublished by profusia.aiOfficial publisherv0.2.0Updated Oct 24, 2026

Give your AI a place to publish: living pages with live data, shareable links, no deploy pipeline.

VerifiedStreamable HTTPWeb executableProductivity & Workflow

Overview

AI-generated overview

Profusia AI lets an assistant publish living web pages with live data and shareable links, without a deploy pipeline.

What you can do
  • Publish pages: the assistant can create living pages that hold live data and hand out shareable links.
  • Update published content: pages are described as living, implying content can be refreshed rather than frozen at publish time.
  • Skip deployment: publishing happens through the hosted service instead of a build or deploy pipeline.
  • Tool-level detail is not published in the registry entry, so the exact set of actions is not documented here.
When to use it
Useful when you want an assistant to turn results, reports or data into a shareable web page that stays current, without setting up hosting or a deployment workflow.
Requirements
A remote MCP endpoint at profusia.ai over streamable HTTP; OAuth authentication is required, so a Profusia account and an OAuth sign-in flow are needed. No environment variables or headers are declared.
Before you install
Publishing creates pages reachable through shareable links, so anything placed on a page may be visible to anyone holding the link; check what data is included before publishing. Access is granted through OAuth to a third-party hosted service.

Installation

In SourceWeft

  1. Open Profusia AI 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.profusia%2Fprofusia/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": {
    "profusia-ai": {
      "type": "http",
      "url": "https://profusia.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

2
  1. v0.2.0LatestOct 10, 2026
  2. v0.1.0Sep 30, 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.