Fyxer
by Fyxer
Search your inbox and meeting transcripts and get email drafted in your voice. Eight tools, seven of them reads. Nothing on this server sends mail. OAuth sign-in with six named scopes, five read and one write.
Verified connector
Listed by Anthropic as a partner connector in its Connectors Directory.
Connection checked by Agentman on .
Anthropic states this reflects the level of review a connector received, not a security audit.
Connect Fyxer via MCP
https://app.fyxer.com/mcpWorks in any MCP-compatible client. In Agentman Studio it is one click — no config file to edit.
Fyxer Tools & Capabilities (8)
Tool names from Anthropic's directory listing. This server requires sign-in, so we could not read tool descriptions or parameter schemas.
Limits
- Most clients cannot sign in. Fyxer supports Dynamic Client Registration for ChatGPT and Claude only. Any tool that needs to supply its own OAuth callback URL — the common shape for a cloud-hosted AI product — cannot complete the flow today.
- Fyxer publishes no tool list beyond six names. Anthropic's directory lists eight. We could diff those two lists, which is better than the no-vendor-enumeration case, but Fyxer's article is a feature table rather than a complete enumeration, so it is not proof that eight is the total.
- We could not read tool schemas or safety annotations. The endpoint returned 401 to an anonymous request, so no parameter-level detail is published here, and no dispatcher parameter can be ruled out at schema level.
- The connector reads more than it writes, by design and by scope. Five read scopes against one draft scope means a consent screen that cannot separate reading your mail from reading your transcripts. The grant is all-or-nothing across the read surface.
- Anthropic's directory labels the permissions "Read". One scope,
drafts.write, is a write scope, anddraft_emailuses it. The label understates the surface by one tool — mildly, since a draft is the least consequential write an email product has, but a reader taking "Read" literally would be wrong. - No shared or group mailboxes. Fyxer states that
support@-style shared inboxes, Microsoft 365 Shared Mailboxes and Google Group inboxes are unsupported, and that each person connects one inbox and one calendar at a time. - Meeting tools return nothing if the Notetaker is off. Fyxer states that when the Notetaker is disabled no meeting content is recorded or processed, which leaves four of the eight tools with nothing to read.
- Rate limits apply per user. Fyxer documents them only as per-user with a wait-and-retry remedy, and publishes no numeric limit, no window and no documented retry header.
- Fyxer Chat's extra abilities are not on this server. Fyxer's dashboard chat can update and delete drafts, archive threads, cancel meetings and RSVP to invitations behind an approval prompt. None of that is exposed through MCP, and reading the Chat documentation as a description of the connector would overstate what an agent can do by a wide margin.
Frequently asked questions
No. Fyxer's MCP documentation answers this directly: the draft_email tool writes the draft in the chat, and you select Open in Outlook or Gmail to save it to your inbox before you review and send it yourself. No tool among the eight carries a send verb, and Fyxer's security page states the product will never send an email on your behalf.
Really unsent, and it does not even reach your mailbox until you act. Fyxer's MCP article describes draft_email as writing the draft into the chat, with an Open in Outlook or Gmail step that saves it. That is one manual step further from delivery than Fyxer's own dashboard chat, where drafts land in your Drafts folder automatically.
Six named scopes, and the boundary sits where it should. Fyxer's RFC 9728 descriptor advertised context.read, emails.read, meetings.read, contacts.read, call_recording.read and drafts.write on 2026-08-22. Five grant reading; exactly one grants writing, and it is limited to drafts. No scope on the list authorises sending, deleting or archiving.
Eight by Anthropic's count and six by Fyxer's. Anthropic's directory lists search_context, find_recordings, search_meetings, get_recording, get_meeting, get_transcript, draft_email and resolve_person. Fyxer's own MCP article documents the same list minus find_recordings and get_recording. The scope descriptor advertises call_recording.read, which corroborates that the two recording tools are real.
Your email bodies, meeting transcripts, uploaded documents and contact records. Fyxer states the MCP accesses data only from your own connected accounts and stores nothing beyond the active session. Because inbound email and meeting speech are written by other people, that content is untrusted input flowing into your agent's context.
Not through MCP. The eight listed tools cover search, retrieval and drafting only, and the sole write scope is drafts.write. Fyxer's separate dashboard chat can update drafts, delete drafts, archive threads and cancel meetings behind an approval prompt, but those capabilities are not exposed as MCP tools and none of them appears in the listing.
A Fyxer account, one connected inbox and a connected calendar. Fyxer's MCP article names those three prerequisites, with the calendar required specifically for meeting search and transcripts. Gmail and Outlook are the supported inbox types. Shared mailboxes such as support or info addresses are not supported at all, so each person connects their own inbox.
Because Fyxer supports Dynamic Client Registration for only two clients today. Fyxer states that its OAuth 2.0 flow supports DCR for ChatGPT and Claude, and that a tool requiring its own OAuth callback URL cannot connect at present. Fyxer describes the restriction as temporary and says it is working to widen support.
Sources
- Fyxer MCP documentation (retrieved 2026-08-22). Machine-readable Markdown served at the same path with a
.mdsuffix. · retrieved 2026-08-22 - Fyxer support index,
llms.txt(retrieved 2026-08-22) · retrieved 2026-08-22 - Fyxer, "Connect Fyxer to Claude" (retrieved 2026-08-22) · retrieved 2026-08-22
- Fyxer, "Connect Fyxer to ChatGPT" (retrieved 2026-08-22) · retrieved 2026-08-22
- Fyxer, "What Fyxer needs access to and why" (retrieved 2026-08-22) · retrieved 2026-08-22
- Fyxer, "APIs and permissions Fyxer uses during setup" (retrieved 2026-08-22) · retrieved 2026-08-22
- Fyxer, "How Fyxer drafts your emails (and where to find them)" (retrieved 2026-08-22) · retrieved 2026-08-22
- Fyxer, "Using Fyxer Chat for search, answers, and drafts" (retrieved 2026-08-22) · retrieved 2026-08-22
- Fyxer, "How the meeting Notetaker works" and "Consent when using the Notetaker desktop app" — · (retrieved 2026-08-22) · retrieved 2026-08-22
- Fyxer, "Who can see your data in a team" and "Does Fyxer work with shared inboxes or shared mailboxes?" — · (retrieved 2026-08-22) · retrieved 2026-08-22
- Fyxer, "Can Fyxer draft replies from my alias email?" (retrieved 2026-08-22) · retrieved 2026-08-22
- Fyxer security page (retrieved 2026-08-22). Its
robots.txtcarriesContent-Signal: ai-train=no, search=yes, ai-input=yes, so synthesis is expressly permitted. · retrieved 2026-08-22 - Live OAuth posture check: anonymous
initializeto the endpoint returned HTTP 401 with awww-authenticateBearer header naming itsresource_metadata; RFC 9728 descriptor athttps://app.fyxer.com/.well-known/oauth-protected-resourceand authorization server metadata athttps://app.fyxer.com/.well-known/oauth-authorization-server(2026-08-22) · retrieved 2026-08-22 - Anthropic Connectors Directory entry — , read from our directory snapshot dated 2026-08-16 · retrieved 2026-08-16
- Fyxer support — · Privacy
Use in Agentman
Connect once and your agents call these tools on their own — on a schedule, in a workflow, with nobody at the keyboard.
Open in Agentman StudioServer Info
- Category
- Productivity
- Developer
- Fyxer
- Tools
- 8
- Domain
- app.fyxer.com
Using Claude Desktop or another MCP client? Setup docs — the connection URL above works anywhere.