Quick Configuration
Choose the setup that matches your environment.
Before You Start
- Confirm you have the account, endpoint, or API key required for Linear.
- Start with minimum scopes and read-only access where possible.
- Keep secrets in environment variables instead of hardcoding them in JSON.
Last verified: 2026-06-13
Environment: Official Linear remote MCP (https://mcp.linear.app/sse) via mcp-remote with OAuth
Install command:
npx -y mcp-remote https://mcp.linear.app/sseLocal config
JSON Local config json
{
"linear": {
"command": "npx",
"args": ["-y", "mcp-remote", "https://mcp.linear.app/sse"]
}
}After copying
Check the Linear JSON before running it in OpenClaw, then verify the server with a real prompt.
Verify prompt
List the issues assigned to me in the current cycle and group them by status.
Expected success output
A browser OAuth prompt opens on first run; then you see your assigned issues grouped by status.
Common Pitfalls & Fixes
- ⚠️ Watch out: API token scopes and mapping between teams, projects, and cycles.
- 🔑 Always store API keys in environment variables, never hardcode them in JSON.
- 🛡️ Start with read-only scopes if available to verify connection safely.
Security checklist
- Auth is OAuth in your browser; no API token is stored in the config file.
- Grant the Linear app the minimum workspace access you actually need.
Common errors
| Error | Cause | Fix |
|---|---|---|
Authentication required | The first-run OAuth flow was not completed. | Finish the browser sign-in for Linear, then retry the request. |
command not found: npx | Node.js is not installed. | Install Node.js 18+ so npx can run mcp-remote. |
Connection closed / 401 | The OAuth session expired. | Re-run to refresh the Linear OAuth token. |
Example Prompts
Once connected, try these prompts to test capabilities:
- List issues assigned to me due this week and summarize priorities.
- Find blockers across the current cycle and propose a resolution plan.
- Create a new issue titled "Investigate build failure" and assign it to me.
Verification Checklist
- Run 1-2 real prompts to confirm Linear returns usable data.
- Check that error messages are clear enough for troubleshooting.
- Document the required scopes, dependencies, and env vars for future reuse.