Phersa

com.phersaPublished by phersa.comOfficial publisherv1.0.0Updated Oct 24, 2026

Find viral videos, make your own with your AI persona on your API keys, monetize with comment-to-DM.

VerifiedStreamable HTTPWeb executableBusiness & CommerceMedia & Design

Overview

AI-generated overview

Phersa is a remote MCP server for finding viral videos, creating videos with an AI persona on your own API keys, and monetizing via comment-to-DM.

What you can do
  • The listing names no individual tools, so capabilities are described only at a high level.
  • Find viral videos for inspiration or reuse.
  • Create your own videos using an AI persona.
  • Run generation on your own API keys.
  • Monetize content through comment-to-DM flows.
When to use it
Worth considering if you want an assistant to help source viral video ideas, produce persona-based videos, and connect that content to comment-to-DM monetization within one service.
Requirements
A remote endpoint at mcp.phersa.com over streamable HTTP; OAuth authentication is required. You also need your own API keys for the AI persona video generation, and a Phersa account.
Before you install
OAuth sign-in grants the server access to your Phersa account. Video generation runs on your own API keys, so usage may incur costs billed by those providers. Comment-to-DM monetization involves messaging audiences and possibly payments; confirm what data and content are sent to third parties before use.

Installation

In SourceWeft

  1. Open Phersa 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/com.phersa%2Fphersa/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": {
    "phersa": {
      "type": "http",
      "url": "https://mcp.phersa.com/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.0LatestOct 14, 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.