Unblu

io.github.detailobsessedPublished by GitHub account detailobsessedv0.10.1Updated Oct 24, 2026

Operate Unblu deployments: health checks, conversation ops, and 300+ API endpoints

VerifiedSTDIODesktop onlyCommunication & CollaborationBusiness & Commerce

Overview

AI-generated overview

Lets an assistant operate an Unblu deployment through its REST API, covering health checks, conversation operations, and many other endpoints.

What you can do
This local MCP server exposes an Unblu deployment's REST API to an assistant, described as covering health checks, conversation operations, and more than 300 API endpoints. It runs as a local process started with uvx from the unblu-mcp PyPI package and talks to the Unblu instance given by UNBLU_BASE_URL. No individual tools are listed in the supplied manifest.
When to use it
Worth adding when an assistant needs to inspect or act on a specific Unblu instance, for example checking deployment health or working with conversations, without leaving the chat. It is not useful if you do not run or administer an Unblu deployment.
Requirements
A local Python runtime able to run the unblu-mcp package via uvx. The required UNBLU_BASE_URL environment variable must point at the Unblu REST API base, for example an instance URL ending in /app/rest/v4. Authentication uses either UNBLU_API_KEY or the UNBLU_USERNAME and UNBLU_PASSWORD pair. Network access to that Unblu instance is needed.
Before you install
The server handles credentials: UNBLU_API_KEY or UNBLU_PASSWORD (with UNBLU_USERNAME) are secrets that should be supplied through the environment and not shared. Because it reaches more than 300 API endpoints, an assistant may be able to change or delete data in the Unblu deployment, not just read it; scope the credentials and review actions before allowing them.

Installation

In SourceWeft

  1. Open Unblu in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.

Other MCP clients

Follow the launch instructions in the repository.

README

This repository has no README.

Tools

0
SourceWeft has not started this package in its sandbox yet, so its tools are not known.

Version history

1
  1. v0.10.1LatestSep 16, 2026

Score

25% 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 days25 pts

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

  • Auth declared10 pts

    Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.

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