[Feature Request] Built-in Termic MCP Server for automated Workspace & Git Worktree provisioning

[javadkh2]

Problem

Starting a new ticket requires manual overhead: creating a new project folder, configuring a fresh workspace in Termic, and manually entering details like the workspace name, target branch, source branch, and path settings.

Proposed Solution

Introduce a built-in Termic MCP Server that allows agents (like Claude Code) to dynamically provision and configure workspaces on the fly.

The Workflow

1. Context: You share a Linear ticket link with Claude Code inside Termic.
2. Trigger: The agent parses the ticket, identifies the correct repository, and calls a native Termic MCP tool: termic_create_worktree_workspace(repo, branch_name, source_branch).
3. Execution: Termic's Rust/Tauri backend executes the git worktree command, registers the new path as a UI workspace with the correct configurations, applies sandbox boundaries, and hands control back to the agent.

Why this fits Termic

It completely automates the workspace setup phase, perfectly aligning with Termic’s core pillars of supporting isolated, parallel exploration paths without manual boilerplate.

[simion]

I like this. workspaces created by agents from other sessions.
Maybe even feed an initial prompt into the new worktree post launch, to delegate a task to a new workspace, or in the main checkout.
Awesome. Will do 🤟

Untill then, i will release a quite big refactor on the terminology and launching new worktrees experience. It allows ultra-fast worktree creation.
Here's a sneak peek:

The worktree vs main checkout setting is persisted. So the workflow: **1 click -> name the task -> enter**. Done

[MHohlios]

I'd vote for exposing this as a CLI command rather than an MCP server. Agents can call a CLI just as easily, but MCP tool definitions consume context window in every session whether they're used or not, while a CLI has zero overhead until invoked. A termic create-worktree-workspace command would cover this use case with less bloat — and an MCP wrapper could always be added later if needed.

[simion]

@MHohlios i avoid using MCPs if i can too, exactly for this reason, to avoid bloating the context.

Anyway, look at the above screenshot. It will be super easy to launch a new worktree once i release this.
We'll see how it goes and how we'll allow an agent to start a new worktree. CLIs might be simplier since they dont require MCP server registration and a process to always listen for calls. We just need to find a way for agents to know about this CLI tool

[javadkh2]

thank you @simion, I like this new design. Can't wait to use it!
Also either a cli or a MCP would be great. it helps me to automate my workflow. So, I'd drag a ticket into the chat and my workspace will be there ready :) .