Linear
Catalog name linear. A remote MCP server for Linear issues, projects and
cycles.
What it’s for
Section titled “What it’s for”An agent that starts from your one-line instruction builds what you said, not what the issue says. This connector closes that gap: it reads the issue with its description, its comments and its state, and it updates the issue when the work lands, so the board stays true without a second pass from you.
It writes as well as reads, with the rights of the account you sign in with.
Add it
Section titled “Add it”At init, or to an existing workbench:
monoceros init acme --with-mcp-servers=linearmonoceros add-mcp-server acme linearThen apply:
monoceros apply acmeSigning in
Section titled “Signing in”There is no key to fill. Linear’s server authenticates interactively, so the yml entry is one line and you sign in once from inside the container:
mcpServers: - name: linearThe per-agent step is in Servers that sign in.
Where it runs
Section titled “Where it runs”Remote (http), at https://mcp.linear.app/mcp. The request leaves the
container.
Verify it
Section titled “Verify it”monoceros check acmeMCP servers linear → Claude Code signs in interactively; authenticate once inside the containerThat line means the server is registered with every agent and waiting for a sign-in. Once you have signed in, ask the agent for an issue by its identifier.
Remove it
Section titled “Remove it”monoceros remove-mcp-server acme linearSee also
Section titled “See also”- MCP servers overview - the model behind this, and the per-agent sign-in.
- Atlassian Rovo and Notion - the same role for Jira, Confluence and Notion.