Linear battery
Rules for 65 Linear MCP tools with per-issue, per-team, and per-project audiences, and reviewed writes.
The Linear battery covers 65 MCP tools and binds the linear audience source, which reads who may see each issue, team, project, and document from Linear itself.
Reads and mutation responses enter as suspicious. A tool that names a resource by id is labelled with that resource's readers: every full member for a public team's issue, the team's members for a private one, plus the people the issue is shared with. Writes into a resource require trusted data its readers may see and a review mark, and record their effects. Tools that name no resource, or name one by a free-text query, keep the audience.
Define as readers authorized for everything the connection can list; map and onto the source in the root config and pass the token through APPA_PROVIDER_LINEAR_TOKEN. A resource named by a display name gets no answer, so the agent names it by id.
The live replay binds human review, maps the chain onto the source, and keeps one root override for a resource whose readers Linear does not model. The review authority cannot widen an audience, so it cannot authorize publishing private Linear content to a public GitHub repository. For read-only use, connect Linear's read-only MCP endpoint.