Bootstrap Linear projects from natural language — milestones, epics, issues, and dependencies.
Describe a project in plain language, get a fully structured Linear project — milestones, epics, issues, labels, and dependency chains. The server reads your team's existing conventions (workflow states, labels, cycles) and generates plans that fit how your team already works. Existing labels are reused, not duplicated. Issues start in your team's default state. Project names avoid collisions…
Inferred from the transports this listing declares (stdio). A client not listed here hasn’t been ruled out — it just isn’t something Forge can confirm.
Verification confirms publisher identity (repo ownership), not code safety. The security scan covers known CVEs and suspicious install scripts.
Read out of the source npm actually ships, at scan time. The package was never executed. Tools registered dynamically at runtime, or hidden inside bundled or minified code, can be missed — so this is a floor on the tool surface, not a complete census of it.
generate-planNo description publishedThis tool published no description. Forge does not invent one.
validate-planNo description publishedThis tool published no description. Forge does not invent one.
bootstrap-projectNo description publishedThis tool published no description. Forge does not invent one.
add-epicNo description publishedThis tool published no description. Forge does not invent one.
introspect-workspaceNo description publishedThis tool published no description. Forge does not invent one.
generate-and-bootstrapNo description publishedThis tool published no description. Forge does not invent one.
list-teamsNo description publishedThis tool published no description. Forge does not invent one.
0 of 7 tools published a description.
Tool names and descriptions are written by the publisher and shown verbatim as inert text. They are the strings an MCP client passes to a model, so Forge scans them for prompt-injection patterns — any finding appears with the security scan above. “Privileged” is a keyword match on the tool name, not an audit of what the tool does: a benign-sounding name can still do anything.
Describe a project in plain language, get a fully structured Linear project — milestones, epics, issues, labels, and dependency chains. The server reads your team's existing conventions (workflow states, labels, cycles) and generates plans that fit how your team already works. Existing labels are reused, not duplicated. Issues start in your team's default state. Project names avoid collisions with active work. Environment Variables (self-hosted) "Set up a Linear project for building a todo CLI…
Linked names open Forge’s index of every entry observed exposing that tool. Browse all indexed tools.
This package was last scanned before Forge began storing the resolved tree. The next scan will record it.