MCP servers
Overview
Model Context Protocol (MCP) servers give Friday tools for services outside your repo — design files, issue trackers, databases, browsers. Friday ships a catalog of built-in servers you can turn on from /mcp, and you can add your own.
Enabled MCP tools load into the main Friday agent automatically. Subagents opt in per agent with an mcp field in their definition (mcp: linear, or mcp: linear, notion for several).
Built-in servers
| Server | What it covers | Setup |
|---|---|---|
| Atlassian | Jira and Confluence issues, sprints, and pages | Sign-in |
| Context7 | Up-to-date library and framework documentation | None |
| Figma | Inspect designs, extract design tokens, read component details | API key |
| Linear | Issues, projects, cycles, and team workflows | Sign-in |
| Lucid | Diagrams, flowcharts, and visual documents | Sign-in |
| Miro | Boards, sticky notes, and visual collaboration | Sign-in |
| Notion | Read, create, and update pages, databases, and documents | Sign-in |
| Playwright | Browser automation, web scraping, and UI testing | None |
| Render | Manage services, deployments, and infrastructure | API key |
| Sentry | Error monitoring, issue tracking, and performance data | Sign-in |
| Supabase | Databases, auth, storage, and edge functions | API key |
"Sign-in" servers open a browser window to authorize Friday. "API key" servers prompt for a token you paste in. Add servers beyond this list from the same /mcp menu.
Enabling a server
Run /mcp inside Friday. The menu lists every server with its current status: ✓ for enabled, ○ for disabled. Pick one to configure or disable it, and repeat for as many servers as you want.
Friday stores the choice per working directory, so different projects can use different servers and different accounts. Once you enable a server for a directory, its tools are there every time you work in that directory.
Enabled servers initialize in the background at launch. You can start typing right away.
Using MCP tools
Ask for what you want in plain language. Friday picks the tools; you don't name them.
Example prompts:
- "Read the Notion document titled 'Tech Spec' and create Linear issues for it."
- "Can you build a UI component based on this Figma image?"
- "Create a front-end using the up-to-date Tailwind CSS docs from Context7"
- "Assign me to Linear task <NAME> and complete the task."