Osigu RCM

io.github.luhkas2309Published by GitHub account luhkas2309v1.0.0Updated Oct 24, 2026

Gerencie cobranças, invoices e atendimentos do RCM da Osigu diretamente do seu agente de IA.

VerifiedStreamable HTTPWeb executableBusiness & Commerce

Overview

AI-generated overview

Lets an AI assistant manage Osigu RCM billing, invoices, and customer service records through a remote endpoint.

What you can do
This server exposes the Osigu RCM (revenue cycle management) system to an AI assistant over a remote streamable HTTP endpoint. According to its registry description, it lets the assistant work with charges, invoices, and service or support interactions directly from the agent. No individual tools are listed in the manifest, so the exact operations available are not documented here.
When to use it
Consider it when you already use Osigu RCM and want an assistant to handle billing, invoice, or customer-service tasks without switching to the RCM interface. It is less useful if you do not use Osigu or need documented tool-level detail before connecting.
Requirements
A remote MCP client that supports streamable HTTP, pointed at the provider's hosted endpoint. The manifest declares no authentication, no environment variables, and no headers, so no credentials are described as needed.
Before you install
The manifest declares no authentication, which means anyone who can reach the endpoint may be able to use it; treat access to the endpoint as sensitive. The description mentions managing charges, invoices, and service records, so expect operations that create or change business data. No tool list is published, so verify what the server can actually do before relying on it.

Installation

In SourceWeft

  1. Open Osigu RCM in the dashboard and add it to a workspace.
  2. 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.luhkas2309%2Fosigu-rcm/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": {
    "osigu-rcm": {
      "type": "http",
      "url": "https://dreamsteam-production.up.railway.app/mcp"
    }
  }
}

README

This repository has no README.

Tools

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

Version history

1
  1. v1.0.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.