Higgs Hub
pro.higgshubPublished by higgshub.proOfficial publisherv1.0.0Updated Oct 24, 2026
Gmail, Outlook, Drive, OneDrive and calendars for AI agents. Many accounts, one endpoint, audit log.
Overview
A remote MCP endpoint that gives an AI assistant access to Gmail, Outlook, Drive, OneDrive and calendars, with many accounts behind one endpoint and an audit日志.
- What you can do
- Work with email in Gmail and Outlook accounts through the assistant, as the description states email support alongside Drive, OneDrive and calendars; the manifest lists no individual tools, so exact actions are not documented here. Access files and folders in Drive and OneDrive. Read and manage calendars. Connect multiple accounts through a single endpoint. Keep an audit log of activity.
- When to use it
- When you want an assistant to work across email, cloud storage and calendars from several accounts without setting up a separate connection for each one, and you value an audit trail of what it did.
- Requirements
- A remote streamable HTTP endpoint at higgshub.pro; no local package or runtime is needed. OAuth authentication is required, so you need an account with the provider and must complete the OAuth consent flow. No environment variables or headers are declared.
Installation
In SourceWeft
- Open Higgs Hub in the dashboard and add it to a workspace.
- Connect the required credentials. They are stored privately and never shown on public pages.
- 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/pro.higgshub%2Fhiggs-hub/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.Other MCP clients
Add this to your client's mcpServers config. The client completes OAuth sign-in on first connect.
{
"mcpServers": {
"higgs-hub": {
"type": "http",
"url": "https://higgshub.pro/api/mcp/mcp"
}
}
}Tools
0Version history
1- v1.0.0LatestSep 25, 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.