Hopper AI LogoHopper AI
IntegrationMarch 10, 2026·5 min read

How to Use Linear with Hopper on Your Watch

Linear is a fast, streamlined issue tracker built for modern software teams, and with Hopper AI on your Wear OS watch, you can create issues, check your backlog, and update tickets directly from your wrist using voice commands — no phone needed.

Overview

The Linear integration connects Hopper to your Linear workspace through the official Linear MCP server. Once connected, you can:

  • Create issues with a title, description, team assignment, priority, and labels
  • View assigned issues filtered by status, team, or priority
  • Update issues to change status, priority, or assignee
  • Search issues by keyword or identifier across your workspace
  • Track projects and monitor milestone progress

All of this works through simple voice commands on your watch.

Setup

Connecting Linear to Hopper takes about a minute.

  1. Open the Hopper companion app on your phone.
  2. Tap the Tools icon in the bottom navigation bar.
  3. Tap Add MCP Server in the top right.
  4. Enter the Linear MCP server URL:
https://mcp.linear.app/mcp
  1. Tap Connect. You'll be redirected to Linear's login page.
  2. Sign in to your Linear account and approve the permissions.
  3. Once authorized, you'll be taken back to the Hopper app. The Linear MCP server is now connected.

That's it — Hopper can now read, create, and update your Linear issues and projects.

For more details on the Linear MCP server, see the official Linear MCP documentation.

Use Cases

Create an Issue

File new issues with natural language. You can include a title, description, team, priority, and labels — all in one command.

Try saying What Hopper does
"Create an issue called fix login bug on the Platform team" Creates an issue assigned to the Platform team
"File a high priority issue: API latency regression" Creates an urgent issue with the given title
"Create a bug in Mobile team: push notifications not arriving, priority 1" Creates a P1 bug on the Mobile team
"New issue: update onboarding flow, add label design-review" Creates an issue with a label attached

View Your Issues

Check what's assigned to you — filtered by status, team, or priority.

Try saying What Hopper does
"What issues are assigned to me?" Lists your open assigned issues
"Show my in-progress issues" Filters your issues by In Progress status
"What are my high priority issues?" Shows your P1 and P2 issues
"Show my issues on the Platform team" Lists your issues for a specific team
"What's in my backlog?" Shows issues in Backlog status

Update an Issue

Change status, priority, or assignee without opening your laptop.

Try saying What Hopper does
"Move fix login bug to in progress" Updates the issue status to In Progress
"Set API latency regression to priority 1" Raises the issue priority to Urgent
"Assign the onboarding issue to Sarah" Changes the issue assignee
"Mark fix login bug as done" Moves the issue to Done status

Search Issues

Find any issue across your workspace by keyword or identifier.

Try saying What Hopper does
"Find issues about authentication" Searches issue titles and descriptions
"Look up issue PLT-342" Fetches a specific issue by identifier
"Search for issues labeled bug on the Backend team" Filters by label and team
"Are there any open issues about onboarding?" Searches open issues by keyword

Manage Projects

Track project progress and milestones at a glance.

Try saying What Hopper does
"Show me the Q2 Launch project" Displays project details and progress
"What's the status of the API Redesign project?" Shows completion percentage and milestones
"List all active projects" Lists projects currently in progress
"How many open issues are in the Mobile Rewrite project?" Returns the issue count for a project

Tips

  • Use identifiers for precision — when updating or searching for a specific issue, saying the identifier like "PLT-342" is faster and more accurate than describing the title.
  • Specify the team upfront — if you work across multiple teams, include the team name when creating or searching issues to avoid ambiguity.
  • Combine details in one command — instead of creating an issue and then editing it, include the team, priority, and labels in a single voice command: "Create a P1 bug on Backend team called rate limiter broken with label infrastructure".

Published in Integration

By Hopper Team

Back to Blog