EN
Explore on GitHub

YOUR MAIL. YOUR ASSISTANT. ONE PIER.

An AI assistant for work.With your work email.

Give your AI assistant a place to find the right mail. SyncPier stores company mail, handles search and retrieval, and keeps discussions tied to messages and topics.

Follow the story

Your information warehouse · MCP / API

THE CONNECTION, AT A GLANCE
Company mailThe inbox you already use
IMAP
SyncPierA shared point of connection
MCP / API
Your AI assistant
IMAP · Gmail · Zoho · Proton Bridge

THE SYNCPIER FIELD GUIDE

Go beyond the introduction.

Explore source connections, search, AI preparation, shared work and the choices behind running SyncPier.

Explore all 12 chapters
04Search and reading 06Discussion and decisions 09Your AI assistants 10Hosting and operations

01 / THE MISSING CONTEXT

You brought in an AI assistant for work.
It couldn’t read your work email.

The conversations, attachments and decisions it needs are already in your mailbox. If your assistant has no connector for that provider and no configured IMAP integration, it cannot retrieve them directly. The same gap affects personal IMAP accounts; company mail makes the consequence especially clear.

An awkward detour

  1. Company inbox
  2. Forward to Gmail
  3. AI assistant

Forwarding work mail to Gmail,
just so your assistant can read it?

You wanted help with work. Now you are routing company mail through a second inbox just to make it readable. Why should getting help with your own mail take this detour?

What if your mail could stay where it belongs?

02 / A PLACE TO CONNECT

Keep your inbox.
Open the conversation.

SyncPier collects mail from the accounts you connect into a service you run. An assistant with an MCP client or a custom API integration can work with that context.

Start with the mail you use

Choose a source to explore the connection.

Company mail
IMAP
SyncPier
MCP / API
Your AI assistant
YOUR EXISTING ACCOUNTYOUR OWN SERVICEYOUR ASSISTANT

Company Mail

Your company’s IMAP mailbox connects to SyncPier. Keep your existing mail account; forwarding to Gmail is not required for this path.

Gmail

Gmail can join the same service through native REST or explicitly configured IMAP. Bring personal and work context together within the permissions you grant.

Zoho

Connect a Zoho account using its supported REST or configured IMAP/SMTP transport. Provider setup remains an explicit step.

Proton Bridge

Connect through a separately running Proton Bridge. The Bridge is a prerequisite for this mail path.

Mail enters SyncPier through its source connection. Assistants use a supported MCP client or a configured API integration. The comparison below explains six products’ different connection paths.

MANY WAYS IN. MANY WAYS OUT.

Information from everywhere.
Context in one place.

Work includes company mail, messages, calendars and discoveries made by other assistants. SyncPier connects each source through its own protocol and gives assistants and apps a common place to retrieve what they need.

Where information arrives

Mail accountsIMAP · Gmail · Zoho · JMAP
Mail protocol / API
SMSMessages and their receiving context
Webhook
Agents & automationResearch · discoveries · work reports
Report API
CalendarsEvents and time across connected accounts
Calendar API
SyncPier

Store · Prepare · Search · Discuss

Where context goes

MCP
Grok BotResearch and follow-up
MCP
ChatGPT DotsAn assistant with work context
MCP
Hermes AgentYour directly connected agent
HTTP API
Apps & custom toolsDashboards · automation · CLI
Different entry points retain their sources. More assistants can work with the same originals and topics.

One topic, across accounts

Group related messages into one topic even when an address changes or mail arrives in different accounts. Every message keeps its source identity and access rules.

An assistant’s findings become reusable context

Store discoveries from Grok Bot or work reports from another agent as originals. The next assistant can search those results and review them alongside the relevant mail.

03 / LET SYNCPIER DO THE FINDING

Ask for the mail you need.
Leave the search to SyncPier.

Your assistant delegates search and filtering, then retrieves the content it needs. The examples below illustrate that exchange; they are not a live inbox or product screenshot.

01/ 03

The assistant asks. SyncPier searches.

An assistant can pass a search query through MCP or the API. SyncPier searches stored mail and available extracted text, including prepared attachment text, and returns results tied to their sources.

Search runs where the mail is stored
ILLUSTRATIVE RETRIEVAL
Assistant ↔ SyncPier
Request to your assistant

Find the mail that mentions “delivery window.”

Your assistant delegates the query to SyncPier and receives matching stored messages. It does not have to download the whole mailbox to search it.

Search result · Company mail

Re: Atlas delivery window

Please confirm the receiving window before we dispatch. The revised schedule is attached.

MATCH WITH A SOURCE
02/ 03

Get the mail that meets the conditions.

Narrow the reading list by topic, mail date, work state or the assistant’s own reading state. Retrieve matching results in pages and keep each request focused.

Choose the scope before fetching the content
ILLUSTRATIVE RETRIEVAL
Assistant ↔ SyncPier
Request to your assistant

Show this week’s Atlas mail that you have not read yet.

SyncPier applies the supported topic, date and reading filters. The assistant receives the matching list and can request the messages it needs.

Filtered list · Atlas topic

This week · Not yet read by this assistant

Re: Atlas delivery window
Re: Updated receiving schedule

A FOCUSED READING LIST
03/ 03

Read the source, or an available summary.

Retrieve original mail content or an already prepared summary, with a reference back to the message. The archive remains available as the assistant moves from one task to the next.

Bring the relevant context into the conversation
ILLUSTRATIVE RETRIEVAL
Assistant ↔ SyncPier
Request to your assistant

Open the original. Also get its summary if one is ready.

SyncPier serves the requested content. Reading an existing summary does not start a new analysis job.

Original mail + prepared summary

Atlas delivery window

Original: the sender asks us to confirm a receiving window.
Prepared summary: Friday is proposed; the receiving time is still open.

CONTEXT ON REQUEST

04 / THE ARCHIVE BEHIND THE ASSISTANT

A large mail archive.
Focused context for AI.

Mail services have storage and feature limits. SyncPier provides the storage and preparation layer between those services and your assistant, so an AI provider’s storage does not have to become the home for your mail archive.

STORED AND PREPARED IN SYNCPIER
01

Original mail & attachments

Keep collected originals and their source identities in storage you operate.

ARCHIVE
02

Searchable text & summaries

Extract content, prepare summaries under your configuration, and serve the material an assistant needs.

PREPARATION
03

Embeddings for semantic retrieval

Prepare and store mail vectors to find relevant context even when you cannot remember the exact words.

SEMANTIC SEARCH
Search results · Selected content · Prepared summaries

SyncPier keeps originals, summaries and embeddings. Analysis with your chosen model sends permitted content to that provider. Where information lives and how AI processes it are separate choices.

FROM COLLECTED INFORMATION TO USABLE CONTEXT

Prepare the information.
Then let the assistant read.

A large mailbox does not need to fit into every conversation. SyncPier stores originals, extracts their contents and prepares ways to find them. Your assistant starts with what the question needs.

01Preserve the original and its sourceMail, attachments and receiving context together

Keep the account and message identity so search results and discussions lead back to the original. External reports enter the same preservation flow.

02Extract text from mail and attachmentsFind information inside the document, too

Extract text from supported documents and search it alongside the message. Unreadable or skipped attachments retain their outcome, so the assistant knows the limits of its evidence.

03Classify and identify what mattersCategories · tags · importance · review

Configured analysis and tagging bots organize the mail. Personal classifications and judgments stay separate, while human corrections help keep the work list useful.

04Prepare summaries and embeddingsRead briefly. Find by meaning.

Summaries provide a quick view; embeddings find related information even when the wording differs. Originals, summaries and search vectors live with SyncPier, reducing dependence on an AI service’s hosted storage.

05Return the context that matchesDelegate the search. Retrieve the evidence.

The assistant narrows by query, date, topic and its own reading or work state. It chooses summaries or originals from the results, then records its judgment on the same topic.

AN ILLUSTRATIVE MESSAGE JOURNEY

Atlas delivery update

“Friday works for delivery, but please confirm the receiving time.”
Source
Company mail / Atlas topic
Extract & summary
Friday works. Receiving time still open.
Classification
Logistics / schedule to confirm
Semantic search
“Delivery conditions still unresolved”
For the assistant
Relevant summary + original reference

The evidence for a decision, without the entire mailbox.

05 / COLLABORATION ACROSS AI SERVICES

Different AI assistants.
One shared thread.

Bring the assistants you run on different AI services into the same mail or topic. With access granted through SyncPier, they can share evidence, question each other’s conclusions and keep the work moving.

01

A shared place for the work

Discuss one mail, or attach several messages to a topic. The conversation and its sources stay together across AI services.

02

Each assistant keeps its own state

One assistant can consider its work complete while another is still checking. Reading progress and work state belong to each assistant.

03

“Done” can deserve another look

Another assistant can point out a gap and direct a recheck request to the first. The first reads the evidence again and decides how to continue.

CROSS-SERVICE COLLABORATION / FICTIONAL EXAMPLE

YOUR CONNECTED ASSISTANTS

Delivery assistantAI service A
Review assistantAI service B

Same mail or topic · Shared through SyncPier

Atlas delivery

Time still unconfirmed

SHARED MAIL EVIDENCE

  • Re: Atlas delivery window
  • Re: Updated receiving schedule

COMPLETE → QUESTION → RECHECK

  1. A · Delivery assistantMy work: complete

    Friday’s delivery is confirmed. I’ve marked my work complete.

  2. B · Review assistantRecheck requested → A

    A, the mail confirms Friday, but still asks us to confirm a receiving time. That part is unfinished. Please check again.

  3. A · Delivery assistantMy work: back in progress

    I reread the source. You’re right: the time is still missing. I’m resuming my work to follow up on it.

  4. Decision recorded

    Friday stays. The receiving time remains open, with the evidence and discussion kept in this topic.

Assistants participate through MCP support or an API integration, with permission to read the mail or topic. Each checks new discussion and recheck requests through its tools; its own reasoning drives any work-state change. This collaboration is within your private workspace; cross-user collaboration is planned separately.

BEYOND ONE ASSISTANT’S CHAT

Individual work.
Shared decisions.

Your assistants, agents from other services, colleagues and their assistants can work around the same mail or topic. Bring the right participants to the evidence and keep the discussion there.

The right context for each project.

Separate personal work, customer support and projects into workspaces, each with its assigned accounts and assistants. Notes, analysis, reading and work state keep their own context even when they refer to the same mail.

Personal workAtlas projectCustomer support

The same mail · The same topic · A continuing decision record

Reuse originals while keeping personal judgments and work records in their own spaces.

Different strengths, working on one topic.

A research assistant finds evidence, a delivery assistant records progress and a reviewer checks for missing conditions. Explicitly share the material they need so collaboration can continue across services.

Research assistantDelivery assistantReview assistant

The same mail · The same topic · A continuing decision record

One assistant marking its work complete does not change another assistant’s reading or work state.

A decision record people and assistants can follow.

Colleagues and their agents discuss within organization-granted account access and the audience of the shared topic. Keep personal conversations separate and publish the evidence and decisions that belong with the team.

You & your assistantsColleagues & their assistantsShared topic

The same mail · The same topic · A continuing decision record

Joining a topic does not grant access to every original. Source permissions still apply.

The next step stays visible after the chat closes.

Connect new mail, external reports, analysis results, discussion changes and work outcomes through events. Configured subscriptions and webhooks notify assistants or apps, which continue within the access you grant.

  1. 01
    New evidence arrives

    The receiving time changes in a new mail

  2. 02
    Notify the subscribed assistant

    Surface the update to the relevant topic

  3. 03
    Review and record

    Read the original, update the decision and state

Read the discussion, the activity, or both together. Follow what changed and why it needs another look. Reading history stays personal, with selected facts shared explicitly.

06 / YOUR PIER, YOUR RULES

Bring your context.
Keep your say.

01

Run it yourself

SyncPier is a service you operate, with a local mail archive and access you configure.

02

Return to the original

Keep original messages and their source identities available while you search, discuss and prepare work.

03

Choose what AI can access

Optional analysis and connected assistants can send selected content to a provider. Choose accounts, permissions and data-egress settings deliberately.

AS THE WORK ADDS UP

An archive that stays useful
as information grows.

Mailbox capacity, model context limits and the lifetime of work records are different concerns. SyncPier lets you manage storage, processing and access separately, and connect them where the work needs it.

01

Separate mailbox capacity from record retention

After checking preservation and backup, remove selected mail or attachments from the provider to manage space. Restore selected items to the provider when needed, with deletion grace and retention policies guiding the archive.

02

Choose the models and cost of analysis

Configure models, credential pools, fallback routes and budgets for summaries, classification and judgments. Delegate bounded analysis to a connected agent with consent, retaining its results and provenance.

03

Connect the mail to the calendar

Read connected calendars together, check availability and export the combined view as ICS for other tools. Treat times without reliable collection as unknown.

04

Carry the record into another environment

Back up, verify, restore and migrate originals and work records. Preserve account lineage, sources and sharing scope, then validate connections and authority in the destination before resuming operations.

BUILT FOR THE CONNECTION

A useful layer
for builders, too.

Delegate search, filtered reading and content retrieval through MCP or the HTTP API. Connect mail and topic discussions to your assistant while collection and preparation continue independently of its chat session.

MCPHTTP APICLIRust
Read the setup guide Explore the MCP interface
CONNECTION MODEL
Your MCP client / integrationSyncPier · self-hosted serviceIMAP · Gmail · Zoho · Proton Bridge
  1. 01
    Run the service

    Start the daemon in your own environment.

  2. 02
    Connect your accounts

    Configure providers and grant scoped access.

  3. 03
    Connect your assistant

    Use an MCP client or build an API integration.

Company mail policies and provider configuration still apply. SyncPier does not bypass your organization’s access controls.

Connect the assistants
you already use.

Which AI assistants can I connect?

Grok Bot and Hermes document custom MCP connections; ChatGPT Dots uses supported installed plugins, including the custom MCP route provided by ChatGPT. OpenClaw, Claude Duet and Microsoft Copilot have different mail and extension paths. The comparison below separates those paths instead of assuming every assistant connects in the same way.

Grok Bot

Documented mail access

Gmail and Outlook are named in the Bot documentation. Its own agent email address is a separate inbox. A built-in form for connecting an arbitrary IMAP account is not documented in the reviewed Bot guides. Custom MCP servers can be added by URL or computer command. This is the documented route for exposing SyncPier tools.

Grok Bot apps Mail attachments

ChatGPT Dots

Documented mail access

The Dots guide documents Gmail. An October 2026 Dots update also records an Outlook setup fix; it does not specify every Outlook account type or action. Generic IMAP account setup is not documented in the reviewed Dots guides. Dots use supported installed plugins. ChatGPT supports custom MCP plugins; account policy and the plugin’s authentication determine the usable route.

Dots apps Outlook setup update Custom MCP plugins

Claude Duet

Documented mail access

Gmail is documented. Duet’s current help explicitly excludes Microsoft 365, even though other Claude products may support it. Generic IMAP account setup is not documented in the reviewed Duet guides. Connectors, plugins and a cloud browser are documented. A Duet-specific SyncPier MCP connection has not been established by this review.

Claude Duet help

OpenClaw

Documented mail access

The bundled gog skill provides Gmail operations through a separately installed CLI and Google OAuth. Gmail event hooks use Pub/Sub. Yes, through the bundled Himalaya skill, with the external CLI, mailbox configuration and supported authentication. Mail access does not require SyncPier. A custom skill or API adapter can add SyncPier’s archive and topics; the adapter must be supplied and configured.

Himalaya skill Gmail skill Gmail events

Hermes Agent

Documented mail access

The bundled Google Workspace skill provides Gmail API operations. Its email gateway receives messages for the agent and replies through IMAP/SMTP. Yes. The gateway receives agent mail; the separate Himalaya skill manages a mailbox using an installed CLI and account configuration. Hermes supports configured HTTP or stdio MCP servers. SyncPier can expose tools through that route; Telegram is not required.

Email gateway Himalaya skill Gmail skill MCP configuration

Microsoft Copilot

Documented mail access

Microsoft 365 Copilot uses Exchange Online for organizational mailbox grounding. Personal Microsoft Copilot documents Gmail and Outlook.com connectors. No universal IMAP support is established. Some Outlook clients extend Copilot to connected Gmail, Yahoo and iCloud; feature and license rules differ. Copilot Studio can add an MCP server to a custom agent. This requires an authored agent and publishing, rather than a universal Copilot mailbox connector.

Microsoft 365 requirements Personal Copilot connectors Copilot in Outlook Outlook FAQ Copilot Studio MCP

Official documentation and repositories reviewed · 2026-10-29These are documented connection paths, not live-account tests with SyncPier. “Not documented” means the reviewed sources do not establish that feature; it does not mean a custom integration is impossible.

Can assistants from different services work together?

Yes. Give each assistant access to the same mail or topic in SyncPier. They can discuss the evidence, record decisions and request a recheck, while keeping their own reading and work state.

Where are my mail and AI processing kept?

SyncPier stores original mail, extracted text and prepared summaries in your environment. You choose the accounts and tools each assistant can access. Selected content goes to an external model when your chosen assistant or analysis configuration uses one.

How do I get started?

Install SyncPier from the source and setup guide, connect a mail account, then configure your assistant’s MCP connection and permissions. Begin with search and retrieval, and add summaries, topic discussions and event connections.

LET YOUR ASSISTANT IN ON THE STORY

Your work email
belongs in the conversation.

Keep the mailbox that works for your company. Build the connection your assistant needs.

Explore SyncPier Read the documentation

Your information warehouse · MCP / API