MCP, CLI, and Github integrations

Use credentials, an install script for MCP and CLI, and Github actions.

Configuration

In Uclusion under integrations go to the MCP & CLI integration. Optionally choose a view for code TODO syncing from the drop down.

Invoking the Uclusion install script will create a /usr/local/bin/uclusion Python 3.8.10 script and install Uclusion as a MCP server in the .eclipse folder if it is present. There will also be a default ~/.uclusion/uclusion.json with settings for TODO syncing.

Now add a ~/.uclusion/credentials file with the contents shown by clicking the Show CLI Secret button. These credentials will also be used for Github actions integration.

Use

uclusion -help

To see a full list of commands availabe from the CLI.


Generating a report or exporting

Create a customizable status report and upload it to a Github repo or use anywhere markdown is accepted.

Let your coding agent set up Uclusion

Bootstrap a temporary Uclusion MCP, approve one browser authorization, and let your coding agent create and connect a workspace without seeing secrets.

Code TODO CLI

A script turns code TODOs into Uclusion bugs and jobs.

Github Actions

Change job status on commit and display on a job releases where it is included.

Model Context Protocol

You Uclusion credentials also allows you to connect your AI agent to Uclusion

Poke AI

Poke your connected AI terminal from Uclusion, and how the local queue delivers those prompts.

What the agent workflow controls

The behaviour the installed Uclusion skill governs: how events are delivered, how work is assigned, which stages permit what, and how finished work is recorded, reviewed and authorized.

What the AI demo contains

The records a coding agent finds when it runs the disposable Uclusion demo, the workshop owner’s role, and what the exercise is testing.