Workwae

com.workwaePublished by workwae.comOfficial publisherv1.1.1Updated Oct 31, 2026

Email, calendar and contacts for AI agents: Gmail, Microsoft 365 and IMAP accounts behind one API.

VerifiedStreamable HTTPWeb executableProductivity & WorkflowCommunication & Collaboration

Overview

AI-generated overview

Workwae is a remote MCP server that gives an assistant unified access to email, calendar and contacts across Gmail, Microsoft 365 and IMAP accounts.

What you can do
  • Connect Gmail, Microsoft 365 and IMAP mail accounts behind one API.
  • Work with email, calendar and contacts through a single interface for AI agents.
  • No tool list is published, so the exact actions available are not documented in the supplied material.
When to use it
Useful when an assistant needs to work across several mail and calendar providers without separate integrations, for example reading and handling email or coordinating schedules and contacts.
Requirements
A remote endpoint at api.workwae.com over streamable HTTP. Authentication is required: either a Workwae API key sent as a Bearer token in the Authorization header, or OAuth sign-in if the header is omitted. No local runtime or environment variables are needed.
Before you install
The server reaches email, calendar and contacts, which are sensitive personal and business data. The Authorization header carries a Workwae API key, so treat it as a secret. Signing in with OAuth grants the assistant access to connected accounts. The published material does not list tools, so confirm which actions can read, send, change or delete data before connecting accounts.

Installation

In SourceWeft

  1. Open Workwae in the dashboard and add it to a workspace.
  2. Connect the required credentials. They are stored privately and never shown on public pages.
  3. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/com.workwae%2Fmcp/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config. The client completes OAuth sign-in on first connect.

{
  "mcpServers": {
    "workwae": {
      "type": "http",
      "url": "https://api.workwae.com/mcp"
    }
  }
}

Tools

0
This server asks you to sign in, so SourceWeft could not read its tools without an account and has not indexed them. What a connected account sees can depend on that account and its permissions.

Version history

2
  1. v1.1.1LatestOct 31, 2026
  2. v1.1.0Oct 17, 2026

Score

67% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • LicenseNot applicable

    A hosted service is used under its provider's terms, so no license is expected here. This check is left out of the percentage.

Other Workwae integrations