Connectors
One-click connections to the apps you already use — official MCP servers that give your crew live reach into 45 tools, no middleman.
Connectors give the crew eyes into the rest of your stack. Each one is a direct, one-click connection to an app's official MCP server — you approve access on the app's own consent screen, Fokus talks to the app directly, and no third-party service ever sits in between. Find them at the bottom of Settings → Crew Tasks.
Connecting an app
The catalog covers 45 apps, grouped the way you think — project management, calendars, email, tasks, messaging, CRM, dev tools, signing, meetings, travel, marketing, and more.
Press Connect on any card. OAuth apps redirect you to that app's own sign-in and consent page; approve, and you land back in Fokus connected.
Cards marked no account connect instantly — knowledge and travel servers like DeepWiki, Hugging Face, and lastminute.com need no login at all.
Once connected, the card shows how many tools the app exposes. Disconnect any time with the trash icon — the crew loses access immediately.
Have an app that isn't listed? Paste any MCP server URL into the custom connector field — the same OAuth flow applies. Time-management tools like Clockwise, Akiflow, and Sunsama provide per-account server URLs in their own settings that work this way.
What the crew does with them
- Connector tasks — the Work with connectors catalog: 22 predefined tasks that read from your connected apps on a schedule. Most work with any app in their group — connect Linear or Jira or Notion and Project Pulse reads whichever it finds. Task cards show the connector logos, with the ones you've connected lit up.
- Custom skills — your own gathering steps can call connector tools too.
- Captain Fokus, live in chat — "what's sitting in my Linear inbox?" queries the app on the spot; "add a comment to FOO-12" works too, but only after you approve that exact action on the card the chat shows you.
During a run, the crew picks a suitable read-only tool from the app (list, search, get) and queries it live. The result feeds that run's note — nothing is imported, stored, or synced.
Reads are free, writes are asked
Anything running unattended — crew tasks, custom skills — is strictly read-only: it can look, never touch. Writes exist only in chat, where Captain Fokus shows you exactly what it's about to do and waits for your approval, one action at a time.
Connectors vs. native integrations
Fokus has two ways to link an app, and they solve different problems:
| Native integrations | Connectors | |
|---|---|---|
| Where | Settings → Integrations | Settings → Crew Tasks |
| What they do | Deep, continuous two-way sync — your Jira issues become Fokus tasks, your Google Calendar events appear in your planner, Slack gets your briefings | Broad, read-only reach — the crew queries the app live during a run |
| Data in Fokus | Yes — items are imported and kept in sync (webhooks, background sync) | No — results only appear inside the note a run produces |
| Direction | Both ways: Fokus can create and update in the connected app | Reads freely; writes only in chat, each one approved by you |
| Depth vs. breadth | Deep features per service (bots, triage, two-way edits), ~20 services | Lighter touch, 45+ apps and growing |
| Setup | Per-service setup, sometimes with options to configure | One click, OAuth on the app's own page |
Rule of thumb: if you want an app's items to live inside Fokus — tasks synced, calendar merged, messages delivered — use the native integration. If you want the crew to check on an app for briefings and digests, a connector is enough. They coexist happily: keep the GitHub integration syncing your issues while Build & Ship reads your PRs through the connector.
Not to be confused with…
The MCP & AI Agents section is the same technology pointing the other way — it's how external agents like Claude use Fokus's tools. Connectors are Fokus reaching out; that section is the world reaching in.
How is this guide?