library · linear
Linear, with the caller's name on every issue.
Linear's own MCP server gives an agent its issues, projects and comments. Through the gateway, each person authorizes Linear once with their own account, so an issue the agent creates is created by them, and the call that created it is on the record before Linear saw it.
Defaults as shipped.
What changes when it runs through the gateway.
A preset can allow only some of Linear's tools and the rest vanish from the catalog. It can restrict which argument keys an agent may send, or pin one to a value that is injected into every call and recorded as injected. Which tools exist is what Linear publishes; the names appear in your catalog the moment the server connects.
Every create and update needs a goal in force and passes the evidence check. An agent that keeps re-opening the same kind of issue while the number you care about goes the wrong way is refused, with the evidence, and told to put it to you.
Two caveats.
Which Linear tools count as reads is decided by Linear's own annotations. A library reference cannot add names, so if Linear marks nothing, the gateway treats every Linear tool as a write: refused without a goal, blocked in testing mode, and unable to measure a goal. That is the safe side. If you need a hard read-only Linear, Linear also serves one at a separate read-only endpoint; add that URL as a custom server.
Linear publishes no rate limit we could find. If it starts refusing, the refusal is logged as a downstream failure with the reason, not retried silently.
Add it.
- addservers page, add from library, Linear
- authorizeeach person clicks authorize and signs in to Linear once
- assigngive a person or a group the presets they should have; nobody else sees the server