Is this an official Linear MCP server?

No. It is Memtro's MCP server with Memtro's Linear connector behind it: the connector reads Linear through its API with the credentials you connect on Dashboard → Connections, and Linear publishes nothing here. The same endpoint carries every other system you connect and Memtro's memory tools.

Nothing on top of Memtro. One price per organisation by its number of users, from $50 a month for up to 10 users after a 7-day free trial, with every connector, the MCP server, jobs and memory included. You bring your own model keys.

Can it change anything in Linear?

Only when you ask, and only what it has been granted: create an issue in a team; comment on an issue; change an issue's state, assignee, priority, title, description or due date. Every other tool reads, searches or lists. An administrator grants each acting tool by name per team, and a personal connection acts only after its owner allows it.

Any MCP client that speaks Streamable HTTP: Claude Code, Cursor, Claude Desktop, OpenCode, Codex, Zed, Windsurf, Cline and the Anthropic and OpenAI SDKs. There is no local process to run; the server is remote and authenticated with your key.

MCP server · Work management

Linear MCP server

Linear in any MCP client, through Memtro: Linear does not publish this server. Memtro's Linear connector reads Linear through its API with the credentials you connect, and one endpoint hands those tools, every other system you connect and Memtro's memory tools to Claude Code, Cursor, Claude Desktop or anything else that speaks Streamable HTTP, as you.

What the model can do

Search issues, read issue details and comments, list teams and projects; can also create an issue, comment on one, and change its state, assignee, priority or title when you ask.

Reads

linear_search_issuesSearch Linear issues by text with optional team key, state name, assignee email and project filters.
linear_get_issueGet one issue by identifier (e.g. ENG-123) with description and comments.
linear_teamsTeams (with keys) and active projects.

Acts, when you ask

These change something in Linear. The model is told to use them only when you ask for exactly that, and each one is granted by name: per team on a shared connection, by the owner on a personal one.

linear_create_issueCreates an issue in a Linear team.
linear_commentComments on a Linear issue, by identifier (ENG-123).
linear_update_issueChanges a Linear issue — its state (by name, e.g. "In Progress" or "Done", or id), assignee, priority, title, description or due date.

Connect it

First connect Linear on Dashboard → Connections, then add Memtro to your client once. The Linear tools appear alongside the tools of everything else you have connected; nothing is configured per connector.

Claude Code

One command registers the server; the tools are then available in every session.

claude mcp add --transport http memtro https://platform.memtro.com/api/mcp \
  --header "Authorization: Bearer sk-memtro-..."

Cursor

Add the server to .cursor/mcp.json in the project, or to the global file under ~/.cursor/.

{
  "mcpServers": {
    "memtro": {
      "url": "https://platform.memtro.com/api/mcp",
      "headers": {
        "Authorization": "Bearer sk-memtro-..."
      }
    }
  }
}

Claude Desktop

Create a personal API key on Dashboard → Profile → API keys. In Claude Desktop add an MCP server of type HTTP with URL https://platform.memtro.com/api/mcp and the header Authorization: Bearer sk-memtro-…

OpenCode

A remote server in opencode.json.

{
  "mcp": {
    "memtro": {
      "type": "remote",
      "url": "https://platform.memtro.com/api/mcp",
      "headers": {
        "Authorization": "Bearer sk-memtro-..."
      }
    }
  }
}

Any other client

Add an MCP server of type HTTP (Streamable HTTP, stateless) at https://platform.memtro.com/api/mcp with the header Authorization: Bearer sk-memtro-.... Codex, Zed, Windsurf, Cline and the SDKs all take a remote server this way.

Who may use it

The key identifies the person, and the server offers that person the tools they may use everywhere else in Memtro. A shared Linear connection is used by the teams an administrator granted it to, tool by tool, on the Permissions page; a personal connection is used by its owner alone, and its tools that act stay off until the owner allows them. See Teams and permissions and Connectors.

Ask it like this

› What is left on the billing migration?
› Which issues are assigned to Priya and overdue?

Questions

Is this an official Linear MCP server?: No. It is Memtro's MCP server with Memtro's Linear connector behind it: the connector reads Linear through its API with the credentials you connect on Dashboard → Connections, and Linear publishes nothing here. The same endpoint carries every other system you connect and Memtro's memory tools.
What does it cost?: Nothing on top of Memtro. One price per organisation by its number of users, from $50 a month for up to 10 users after a 7-day free trial, with every connector, the MCP server, jobs and memory included. You bring your own model keys.
Can it change anything in Linear?: Only when you ask, and only what it has been granted: create an issue in a team; comment on an issue; change an issue's state, assignee, priority, title, description or due date. Every other tool reads, searches or lists. An administrator grants each acting tool by name per team, and a personal connection acts only after its owner allows it.
Which clients work?: Any MCP client that speaks Streamable HTTP: Claude Code, Cursor, Claude Desktop, OpenCode, Codex, Zed, Windsurf, Cline and the Anthropic and OpenAI SDKs. There is no local process to run; the server is remote and authenticated with your key.