MCP Recipe
Draft a weekly Linear update with Linear and Memory
Influzer starter recipe: pull this week’s Linear issue activity, store durable team context in Memory, and draft a short status update you can paste into Slack or email.
Productivity
MCP servers used
Compatible clients (author-reported, not verified by Influzer): Cursor, Claude Desktop, Claude Code
Prerequisites
- Linear workspace access via the official Linear remote MCP (OAuth)- Memory MCP installed locally (
@modelcontextprotocol/server-memoryor your client’s Memory integration)- Agreement on which Linear team/project to summarize
Required permissions
Linear OAuth scopes for reading issues/projects. Memory writes local persistent entities — avoid storing secrets, tokens, or private customer data.
Setup
1.
Connect Linear (remote) and Memory (local)
Add Linear as a remote MCP at https://mcp.linear.app/mcp and complete OAuth. Add Memory as a local/stdio MCP in Cursor or Claude Desktop.
2.
Example Cursor config
· json
{ "mcpServers": { "linear": { "url": "https://mcp.linear.app/mcp" }, "memory": { "command": "npx", "args": ["-y", "@modelcontextprotocol/server-memory"] } }}
3.
Gather, remember, draft
· markdown
Using Linear, list issues updated in the last 7 days for my primary team. Group them into shipped, in progress, and blocked.Store a Memory entity for this week’s themes (no secrets).Draft a 8–12 sentence weekly update in plain language for stakeholders.Expected result
A concise weekly update (shipped / in progress / blocked) plus Memory entities you can reuse next week.
Sample output
Weekly updateShipped: …In progress: …Blocked: …Memory: created entity “TeamAlphaWeekly” with relations to active projects.
Troubleshooting
- Linear OAuth loop: remove and re-add
https://mcp.linear.app/mcp- Memory is stdio/local — remote-only clients like ChatGPT may not support it- If the draft is too noisy, constrain the prompt to one team or label