
HQBase
io.github.HQBasePublished by GitHub account HQBasev1.0.0Updated Oct 24, 2026
Connect AI agents to your self-hosted HQBase shared email workspace.
Overview
HQBase's OAuth-protected remote MCP server connects AI assistants to a self-hosted shared email workspace running in your own Cloudflare account.
- What you can do
- Connect an assistant to a team's shared email workspace hosted on the customer's own infrastructure, where mail and credentials stay under the team's control (no tool list is published, so exact actions are not documented here).
- When to use it
- When a team already runs HQBase as its shared mailbox workspace and wants an AI assistant to work with that mail environment through the built-in remote MCP endpoint.
- Requirements
- A deployed HQBase installation reachable at its installation domain over streamable HTTP, plus OAuth authentication to that installation. No local package, environment variables or headers are declared.
Installation
In SourceWeft
- Open HQBase in the dashboard and add it to a workspace.
- 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.
Other MCP clients
Follow the launch instructions in the repository.
README
HQBase
Your team's email workspace. On your infrastructure.
An open-source shared email workspace that runs in your Cloudflare account and keeps mail and credentials in infrastructure you control.
Website · Documentation · Releases · Contributing
[CI status] [Latest release] [AGPL-3.0-only license] [Join the HQBase Discord] [Follow @berman_to on X]
About HQBase
[HQBase shared inbox interface]
HQBase gives teams one place to work with shared mailboxes while keeping the application, mail, and Cloudflare credentials in customer infrastructure. It includes:
- Shared mailboxes and team access controls.
- Multi-domain setup, drafts, and audit history.
- Installation, update, backup, and recovery operations.
- An OAuth-protected remote MCP server.
See the product documentation for installation, daily use, architecture, and operations.
Made by the community
We love seeing people build around HQBase. Independent clients give you more ways to use your workspace:
- Herald — A native macOS email client for HQBase.
HQBase has tested Herald for compatibility. It is made and maintained by independent community developers, so its releases, support, and behavior remain in their care rather than HQBase's. Please review the project and decide whether it is right for your workspace.
Develop locally
Start the application
Before you run the optional seed command, add these values to .dev.vars:
BETTER_AUTH_SECRETHQBASE_LOCAL_SEED_PASSWORDwith 8 to 128 characters
The seed command writes only to local D1 and does not contact Cloudflare OAuth. Open
http://127.0.0.1:5173/ and sign in as [email protected] with that
password. Vite serves the frontend with live reload on port 5173 and proxies API requests to the
Wrangler Worker on port 8787.
To use the first-run setup flow, omit the seed command and open http://localhost:5173/setup.
Reset local data
To discard all local D1 data, rebuild the schema, and recreate the demo workspace:
The reset command is destructive and local only. It does not change a deployed database.
Preview the setup interface
For presentation-only onboarding work:
Open http://127.0.0.1:5173/__ui/setup.
Review the visual system
To inspect the shared components, interactive states, product patterns, and local screen routes:
Open http://127.0.0.1:5173/__ui/design. The gallery uses deterministic presentation fixtures
and does not call product APIs.
Verify changes
Run the full local quality gate:
Run pnpm cf:typegen after you change wrangler.jsonc.
Pushes to main run the same quality gate and deployment dry-run. Deployed staging is manual and
also runs inside the signed release workflow. A release stays in draft until the previous stable
version upgrades to the exact signed candidate and passes its checks. Customer installations and
updates verify the signed manifest and artifact digest before deployment.
Documentation
hqbase.io/docs is the public source for user and operator guides, product specifications, and maintainer procedures.
Contributing
Read the contribution guide before you open a pull request.
Security
To report a vulnerability, follow the private process in the security policy.
License
HQBase is available under the GNU Affero General Public License v3.0 only.
Source: README.md at commit a1161f1
Tools
0Version history
1- v1.0.0LatestSep 16, 2026
Score
50% 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
Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.
- Auth declaredRequired10 pts
Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.
- 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
- License10 pts