Skip to content

Add a new AI-client integration #271

Description

@btsouth

Toolport writes MCP config for supported AI clients through the defs() table in src-tauri/src/clients.rs. Adding another editor/agent is a clean, self-contained contribution and a good first PR.

Pick a client that is not supported yet, add its ClientDef (per-OS config path, format variant, connector vs file), and a fixture test alongside the existing path tests (client_config_paths_are_stable_across_platforms, and client_config_paths_honor_xdg_dirs_on_linux if the client has a Linux path). Copy an existing entry such as boltai or continue as a template. See CONTRIBUTING.md for the full walkthrough, including the table of every Format variant.

Claiming one: comment here with the client you want, or open your own issue for it. Anything already supported is listed in defs(), so check there first. Previously listed candidates (Factory Droid, Crush, Kilo Code, GitHub Copilot CLI, Amp, JetBrains Junie) have all shipped.

One requirement before proposing a new client: it has to keep its MCP servers in a config file Toolport can read and write. Clients that store servers in an internal database don't round-trip; that's why Cherry Studio (#295) and 5ire (#297) were closed as not planned.

Acceptance: the client appears in the Clients view and its config round-trips through a fixture test.

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions