Fyxer

Search your inbox and meeting transcripts and get email drafted in your voice.

Add to Agentman Studio

Opens Agent Studio, where connecting is one click. The connector URL below works in any MCP client.

Paste it into any MCP client. Setup docs

Resources

What the Fyxer connector does

The Fyxer MCP server connects Fyxer — an AI assistant that organises a Gmail or Outlook inbox and records meetings — to Claude, ChatGPT and any MCP-compatible agent. It exposes eight tools that search email, meetings and transcripts, and one that drafts a reply in your writing style. Nothing on this server sends mail. Sign-in is OAuth.

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.

Fyxer tools (8)

  • search_context
  • find_recordings
  • search_meetings
  • get_recording
  • get_meeting
  • get_transcript
  • draft_email
  • resolve_person

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, and draft_email uses 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

Can the Fyxer connector send an email on my behalf?

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.

Is a Fyxer draft really unsent, or does it go out automatically?

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.

What OAuth permissions does the Fyxer MCP server request?

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.

How many tools does the Fyxer MCP server have?

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.

What data can the Fyxer connector read from my accounts?

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.

Can the connector delete, archive or reply to anything in my inbox?

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.

What do I need before connecting Fyxer to Claude?

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.

Why can't my AI tool sign in to the Fyxer MCP server?

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

More Productivity connectors

  • 6sense

    Ask an AI agent about 6sense account insights, buying signals and keyword trends.

  • Adobe Workfront

    Find, create, update and delete Workfront work items from an AI agent.

Browse all MCP connectorsClaude and ChatGPT setup guideBrowse AI skills

Product names and logos belong to their owners. Agentman is not affiliated with a connector's maker unless the page says the connector is built and run by Agentman.

Use it in an agent

Put Fyxer to work.

Connect Fyxer once and your agents call these tools on their own: on a schedule, in a workflow, with nobody at the keyboard.

Open in Agentman Studio