branchly

io.branchlyPublished by branchly.ioOfficial publisherv1.0.0Updated Oct 24, 2026

Connect your agent to branchly: manage content, prompts, actions, learn from analytics and insights

VerifiedStreamable HTTPWeb executableProductivity & Workflow

Overview

AI-generated overview

Branchly connects an AI assistant to a content platform to manage content, prompts and actions, and to learn from analytics and insights.

What you can do
Manage content, prompts and actions in a connected branchly account, as described in the registry entry. Review analytics and insights to learn from how that content performs. The manifest lists no individual tools, so the exact operations are not documented here.
When to use it
Worth considering when you want an assistant to work with branchly content, prompts and actions, or to pull analytics and insights from the platform into a conversation.
Requirements
A remote MCP endpoint at api.branchly.io over streamable HTTP. A branchly API key is required and sent in the x-api-key header. No local runtime or environment variables are declared.
Before you install
The server requires an API key sent as the x-api-key header; treat it as a secret and check what the key is allowed to change. The description mentions managing content, prompts and actions, which likely includes writing or changing data in your account, but the specific tools are not listed, so verify permissions before connecting.

Installation

In SourceWeft

  1. Open branchly in the dashboard and add it to a workspace.
  2. Connect x-api-key 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.branchly%2Fbranchly/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": {
    "branchly": {
      "type": "http",
      "url": "https://api.branchly.io/mcp",
      "headers": {
        "x-api-key": "<YOUR_API_KEY>"
      }
    }
  }
}

Tools

0
This server asks for a credential such as an API key, so SourceWeft could not read its tools without one and has not indexed them.

Version history

1
  1. v1.0.0LatestSep 16, 2026

Score

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

    Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.

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