Opsera

io.opseraPublished by opsera.ioOfficial publisherv0.5.0Updated Oct 24, 2026

Opsera AI Agent MCP server providing authenticated DevOps automation over SSE

VerifiedSSEWeb executableCloud & Infrastructure

Overview

AI-generated overview

Connects an assistant to Opsera's DevOps automation platform over an authenticated remote SSE endpoint.

What you can do
This is a remote MCP server hosted by Opsera at agent.opsera.io and reached over SSE. It exposes Opsera's DevOps automation capabilities to an AI assistant, so the assistant can work with the platform's pipelines and delivery workflows through the MCP connection. The manifest does not list individual tools, so the exact operations available are not documented here.
When to use it
Consider it when your team already uses Opsera for DevOps automation and you want an assistant to act within that platform rather than through its web interface. It is less useful if you do not have an Opsera account or need a self-hosted server.
Requirements
A remote SSE connection to agent.opsera.io and an Opsera account. A bearer token is required in the Authorization header; no environment variables or local runtime are declared.
Before you install
The server requires a bearer token in the Authorization header, so treat that credential as a secret and grant it only the access you intend. Because it is a hosted remote endpoint, requests and data pass through Opsera's service. The manifest lists no tools, so confirm what actions it can take, especially any that change pipelines or deployments, before use.

Installation

In SourceWeft

  1. Open Opsera in the dashboard and add it to a workspace.
  2. Connect Authorization token 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 SSE. 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.opsera%2Fopsera/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": {
    "opsera": {
      "type": "sse",
      "url": "https://agent.opsera.io/mcp",
      "headers": {
        "Authorization": "Bearer <YOUR_TOKEN>"
      }
    }
  }
}

README

This repository has no README.

Tools

0
SourceWeft has not read this server's tools yet.

Version history

1
  1. v0.5.0LatestSep 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 listedRequired15 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.

Other Opsera integrations