Vyrl

io.github.solarx56Published by GitHub account solarx56v1.0.0Updated Oct 24, 2026

Inspect and edit media canvases, run existing Flows, and retrieve results. Vyrl MCP token required.

VerifiedStreamable HTTPWeb executableMedia & Design

Overview

AI-generated overview

A remote MCP server that lets an assistant inspect and edit media canvases, run existing Vyrl Flows, and retrieve results.

What you can do
Vyrl connects an assistant to Vyrl's media canvas environment over a remote HTTP endpoint. It lets the assistant inspect and edit media canvases, run Flows that already exist in the account, and retrieve the results. No individual tools are listed in the manifest, so the exact operations are not documented here.
When to use it
Useful when you already work in Vyrl and want an assistant to view or adjust media canvases, trigger existing Flows, and pull back their outputs without switching tools.
Requirements
A remote endpoint at vyrl.pro reached over streamable HTTP. Authentication is OAuth and required: an Authorization header carrying a Bearer token, a scoped Vyrl MCP token created in Vyrl profile settings. No local runtime or environment variables are declared.
Before you install
The Authorization header carries a secret scoped Vyrl MCP token; keep it private and scope it narrowly. Generative Flow runs can consume Vyrl credits, so running Flows may spend paid credit. Editing canvases changes data in your Vyrl account.

Installation

In SourceWeft

  1. Open Vyrl 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/io.github.solarx56%2Fvyrl/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": {
    "vyrl": {
      "type": "http",
      "url": "https://vyrl.pro/api/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.0LatestSep 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.