1. Conduid
  2. Developer Tools
  3. Bridle
MCP server · Developer Tools

Bridle

TUI / CLI config manager for agentic harnesses (Amp, Claude Code, Opencode, Goose, Copilot CLI, Crush, Droid)

77Good

Scored 10 hours ago · breakdown

About Bridle

Bridle is an MCP server published by neiii in the Developer Tools category: tUI / CLI config manager for agentic harnesses (Amp, Claude Code, Opencode, Goose, Copilot CLI, Crush, Droid).

The repository has 440 stars and 20 forks, with the last commit 10 hours ago. Recent commit activity is the strongest signal that reported issues will get attention.

Install

From source
git clone https://github.com/neiii/bridle

This server has no ConduID identity, so agent calls to it are not receipted. Pin the version you install and review the source before granting it credentials.

Ask AI

✦

Ask AI about Bridle

Powered by Claude · Grounded in docs

I know everything about Bridle. Ask me about installation, configuration, usage, or troubleshooting.

Security checks

Static checks derived from the repository 10 hours ago. Heuristics on the source, not an audit.

  • ✓README presentThe repository ships documentation.
  • ✓License declaredUsable under a stated license.
  • ✓Tests presentA test suite exists in the repository.
  • ✓Dependencies pinnedA lockfile pins dependency versions.
  • ✓No dynamic code executionSource scan found no eval, dynamic Function, or shell execution.
  • !Scoped permissionsDoesn't declare a permission scope. Assume it can do anything its process can.

Releases

skills-locate-v0.4.0skills-locate: v0.4.0 · 16 Oct 20260.4.0 (2026-10-16) Features merge harness-locate and skills-locate into workspace (#46)…
harness-locate-v0.7.0harness-locate: v0.7.0 · 16 Oct 20260.7.0 (2026-10-16) Features merge harness-locate and skills-locate into workspace (#46)…
bridle-v0.3.0bridle: v0.3.0 · 16 Oct 20260.3.0 (2026-10-16) Features improve agent readiness with CI enhancements and templates (#38)…
v0.2.9v0.2.9 · 30 Jan 2026Install bridle 0.2.9 Install prebuilt binaries via shell script curl --proto '=https' --tlsv1.2 -LsSf https://github.com/neiii/bridle/releases/download/v0.2.9/bridle-installer.sh | sh Install prebuilt binaries via powershell script…
v0.2.80.2.8 - 2026-01-20 · 20 Jan 2026Release Notes Added Crush CLI harness support - Full support for Crush CLI as a new harness Profile management (create, switch, show, delete) MCP server installation to `~/.config/crush/crush.json` Skills installation to…

README

Bridle

Bridle

Unified configuration manager for AI coding assistants. Manage profiles, install skills/agents/commands, and switch configurations across Claude Code, OpenCode, Goose, Amp, Copilot CLI, and Crush.

Installation

Try it instantly (no install)

Run once without installing:

Package Manager Command
npx npx bridle-ai
bunx bunx bridle-ai
pnpm pnpm dlx bridle-ai

Install globally

For repeated use, install once:

Node package managers:

Manager Command
npm npm install -g bridle-ai
bun bun install -g bridle-ai
pnpm pnpm add -g bridle-ai

Other methods:

# Homebrew
brew install neiii/bridle/bridle

# Cargo
cargo install bridle

# From source
git clone https://github.com/neiii/bridle && cd bridle && cargo install --path .

Quick Start

# Launch the TUI
bridle

# See what's configured across all harnesses
bridle status

# Create a profile from your current config
bridle profile create claude work --from-current

# Switch between profiles
bridle profile switch claude personal

Screenshot

"Package Manager" for your harness

With Bridle, you're able to install skills, agents, commands, and MCPs from any GitHub repository, similar to how Claude Code does it. With Bridle, however, you're not limited to just one harness; we auto-translate all the paths, namings, schemas, and configurations for you.

# Install from GitHub
bridle install owner/repo

# What happens:
# 1. Bridle scans the repo for skills, agents, commands, and MCPs
# 2. You select which components to install
# 3. You choose target harnesses and profiles
# 4. Bridle translates paths and configs for each harness automatically

Why this matters: A skill written for Claude Code uses ~/.claude/skills/. The same skill on OpenCode lives at ~/.config/opencode/skill/. MCPs follow different JSON/YAML schemas. Bridle handles all these differences for you.

Component Claude Code OpenCode Goose Copilot CLI Crush
Skills ~/.claude/skills/ ~/.config/opencode/skill/ ~/.config/goose/skills/ ~/.copilot/skills/ ~/.config/crush/skills/
Agents ~/.claude/plugins/*/agents/ ~/.config/opencode/agent/ — ~/.copilot/agents/ —
Commands ~/.claude/plugins/*/commands/ ~/.config/opencode/command/ — — —
MCPs ~/.claude/.mcp.json opencode.jsonc config.yaml ~/.copilot/mcp-config.json crush.json

Core Concepts

Harnesses are AI coding assistants: claude, opencode, goose, amp, copilot, crush

Profiles are saved configurations. Each harness can have multiple profiles (e.g., work, personal, minimal). Bridle copies the active profile's config into the harness's config directory when you switch.

Commands

Status & TUI

Command Description
bridle Launch interactive TUI
bridle status Show active profiles across all harnesses
bridle init Initialize bridle config and default profiles

Profiles

Command Description
bridle profile list <harness> List all profiles for a harness
bridle profile show <harness> <name> Show profile details (model, MCPs, plugins)
bridle profile create <harness> <name> Create empty profile
bridle profile create <harness> <name> --from-current Create profile from current config
bridle profile switch <harness> <name> Activate a profile
bridle profile edit <harness> <name> Open profile in editor
bridle profile diff <harness> <name> [other] Compare profiles
bridle profile delete <harness> <name> Delete a profile

Installing & Uninstalling

Command Description
bridle install <source> Install skills/MCPs from GitHub (owner/repo or URL)
bridle install <source> --force Overwrite existing installations
bridle uninstall <harness> <profile> Interactively remove components [experimental]

Configuration

Command Description
bridle config get <key> Get a config value
bridle config set <key> <value> Set a config value

Config keys: profile_marker, editor, tui.view, default_harness

Output Formats

All commands support -o, --output <format>:

  • text (default) — Human-readable
  • json — Machine-readable
  • auto — Text for TTY, JSON for pipes

Configuration

Bridle stores its config at ~/.config/bridle/config.toml:

profile_marker = false  # Create marker files for debugging
editor = "code --wait"  # Editor for `profile edit`
default_harness = "opencode" # Which tab to open on launch

[active]
claude = "work"
opencode = "default"

[tui]
view = "Dashboard"      # Will add more later :P 

Supported Harnesses

Harness Config Location Status
Claude Code ~/.claude/ Full support
OpenCode ~/.config/opencode/ Full support
Goose ~/.config/goose/ Full support
Amp ~/.amp/ Experimental (ish)
Copilot CLI ~/.copilot/ Full support
Crush ~/.config/crush/ Full support (skills + MCP)

Honorable Mentions

License

MIT

README fetched from the repository 10 hours ago. The original is authoritative.

Questions

About Bridle

How do I install Bridle?

No package has been published for this server, so install it from source: clone the repository and follow its README.

Is Bridle safe to use with an AI agent?

Its trust score is 77 out of 100 (good). It passes 5 of the 6 static security checks run so far; the failures are listed above. It has no ConduID identity yet, so agent calls to it are not receipted.

Is Bridle still maintained?

Yes — the latest release is skills-locate-v0.4.0 (16 Oct 2026), and the last commit was 10 hours ago. The repository has 440 stars and 13 open issues.