The same Linear workspace. Two different ways to work.
Linear CLI is designed for direct terminal commands and repository-aware workflows. Linear MCP connects compatible AI clients to Linear through standardized tools. They can be used separately or together.
You want direct, predictable terminal commands, repository context, Git or Jujutsu issue detection and GitHub pull-request support.
You want a compatible AI client to find, create or update Linear objects through natural-language requests.
You want AI-assisted planning or issue management while keeping branch creation, scripting and pull-request work inside your terminal.
Understand what actually changes
The difference is not simply “manual versus automatic.” Each approach has a different interface, context, authentication method and ideal workflow.
Commands entered directly in a terminal.
Tool calls made through a compatible AI client.
linear issue view ENG-123
“Show me the details for issue ENG-123.”
Personal API key authenticated locally through the CLI.
OAuth 2.1 interactive authorization, bearer token or API key depending on the client setup.
Detects issue context from Git branch names or Jujutsu commit trailers.
Receives context supplied by the AI client. MCP alone does not replace local Git or Jujutsu tools.
Can prepare a GitHub pull request through
linear issue pr and GitHub CLI.
Can work with Linear data, but local Git and GitHub actions depend on other tools available to the agent.
Suitable for shell scripts, repeatable commands and structured JSON output.
Suitable for agent-driven workflows and natural-language task execution.
Linear CLI is installed and executed in your local environment.
Linear’s remote MCP server is centrally hosted and accessed through a compatible client.
Developers who prefer direct terminal and repository workflows.
Users who want an AI client to interact with Linear through approved tools.
See how each workflow feels in practice
Select a task to compare the exact CLI approach with an equivalent MCP-assisted request.
Find issues related to a login problem
Enter an exact terminal command
linear issue query --search "login bug"
The command returns matching issues from the configured team.
Describe the result to your AI client
Find Linear issues related to a login bug and summarize their current statuses.
The client decides which permitted MCP tools to call and presents the result.
Begin development work on ENG-123
Connect the issue to local work
linear issue start ENG-123
The CLI can create or switch the Git branch, or add the issue trailer in Jujutsu.
Ask the client to update Linear
Show me ENG-123 and move it to the appropriate started status.
MCP can update permitted Linear data. Creating a local branch still requires local development tools.
Review project work before planning
List projects in the terminal
linear project list
Use additional commands to inspect or modify individual projects.
Request a connected overview
Review my active Linear projects, identify blocked work and summarize the next priorities.
An AI client can combine results from permitted project and issue tools into a summary.
Choose by the work you want to complete
Neither approach is universally better. The correct choice depends on the interface, context and control you need.
Give each tool only the access it needs.
Linear CLI
- Enter the API key only in your local terminal.
- Keep credentials out of repositories and screenshots.
- Review environment variables that override configuration.
Linear MCP
- Review the permissions requested by the AI client.
- Use read-only access when write tools are unnecessary.
- Keep separate authentication contexts for separate workspaces.
LinearCli.com does not connect to either method. This independent reference does not receive API keys, OAuth tokens, AI prompts or workspace information.
Start with Linear CLI installation and commands.
Install the CLI, authenticate locally and learn the commands used for repository-aware issue workflows.