One command
Add Linear to any Ashlr Stack project with a single command. Stack runs the auth flow, verifies the credential, and writes every secret slot into Phantom.
stack add linear
Or describe what you're building and let Claude pick it up via stack recommend:
stack recommend "issue tracking for my team"Auth flow
Paste a long-lived API key once. Stack verifies it against the provider's API before writing to Phantom.
How-to: Create a personal API key at https://linear.app/settings/api.
Secret slots
stack add linear writes these 1 secret
slot into your Phantom vault:
LINEAR_API_KEY
The values never leave Phantom in plaintext. Your .env file references slot
names, and stack exec -- <cmd> swaps them in at process-spawn time via
Phantom's local proxy.
MCP wiring
Linear ships an MCP server.
stack add linear auto-wires it into .mcp.json so your Claude Code / Cursor / Windsurf session can use it immediately.
mcp-linear with LINEAR_API_KEY piped from Phantom.
FAQ
Do I need a Linear account to use it with Stack?
Yes — Stack provisions Linear on your behalf, but it authenticates as you. Paste a long-lived API key once. Stack verifies it against the provider's API before writing to Phantom. If you don't have a credential yet, create one at https://linear.app and paste it once.
Where does Stack store my Linear credentials?
In Phantom Secrets, an E2E-encrypted local vault. Stack writes the secret slot names (LINEAR_API_KEY) into .stack.toml — the actual values live only in Phantom and never touch disk in plaintext.
Can I rotate or revoke this integration later?
Yes. Run `stack remove linear` to pull the Linear service back out (Phantom secrets deleted, MCP entry removed, .stack.toml cleaned up). Rotate the underlying Linear credentials in their dashboard — https://linear.app — and Stack's next `doctor --fix` will pick up the new values.