SRG+

io.github.srgplusPublished by GitHub account srgplusv0.4.7Updated Oct 24, 2026

Manage SRG+ hubs, channels, content, assets, users, and workspaces from any MCP-aware AI agent.

VerifiedStreamable HTTPWeb executableProductivity & Workflow

Overview

AI-generated overview

Lets an assistant manage SRG+ hubs, channels, content, assets, users, and workspaces through an MCP connection.

What you can do
This server exposes SRG+ workspace administration to an MCP-aware AI agent. According to its description, it covers hubs, channels, content, assets, users, and workspaces, so an assistant can work with those resources on your behalf. The manifest does not list individual tools, so the exact operations available are not documented here.
When to use it
Reach for it when you already use SRG+ and want an AI assistant to handle workspace tasks such as organizing hubs and channels, working with content and assets, or managing users, instead of doing everything by hand in the SRG+ interface. It is less useful if you do not have an SRG+ workspace.
Requirements
Runs as a remote endpoint at over streamable HTTP, or locally via the PyPI package srgplus-mcp with uvx over stdio. Authentication is required: either OAuth, or a workspace API key passed as the SRG_API_KEYS environment variable or the X-API-Key header. Multiple workspace keys can be given comma-separated. Keys come from Settings -> Workspaces -> API Keys.
Before you install
The server requires workspace API keys, supplied as SRG_API_KEYS or the X-API-Key header; treat these as secrets and avoid exposing them in shared configuration or logs. Because it manages hubs, channels, content, assets, users, and workspaces, expect actions that can create, change, or delete workspace data. No tool list is published, so review what each tool does before granting access.

Installation

In SourceWeft

  1. Open SRG+ 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.srgplus%2Fsrgplus-mcp/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": {
    "srg": {
      "type": "http",
      "url": "https://mcp.srgplus.com/mcp"
    }
  }
}

README

This repository has no README.

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. v0.4.7LatestSep 16, 2026

Score

60% 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.

  • License10 pts

    Declare a license in the repository or the registry entry.