Connect AI agents to your self-hosted HQBase shared email workspace.
io.github.HQBase/hqbase MCP Server
This MCP server helps connect AI agents to a self-hosted HQBase shared email workspace. The HQBase project is an open-source shared email workspace designed to run in Cloudflare and keep mail and credentials in infrastructure controlled by the user. It targets shared-inbox style email workflows on self-hosted infrastructure.
🛠️ Key Features
Connect AI agents to HQBase shared email workspace
Self-hosted shared inbox via infrastructure the user controls
Runs in Cloudflare account (per provided description)
🚀 Use Cases
Agent access to a shared email workspace
Shared inbox operations using a self-hosted setup
Email agent integration where credentials remain on user infrastructure
⚡ Developer Benefits
Uses self-hosted infrastructure for mail and credentials
Works with Cloudflare Workers environment (topic-listed)
Relevant for developers focused on shared email workspace integration
⚠️ Limitations
Only described as connecting to HQBase; no additional tools or capabilities are specified in the provided data
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:
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
sh
pnpm install
pnpm db:migrate:local
pnpm db:seed:local
pnpm dev
Before you run the optional seed command, add these values to .dev.vars:
BETTER_AUTH_SECRET
HQBASE_LOCAL_SEED_PASSWORD with 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 owner@hqbase.test 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:
sh
pnpm db:reset:local
pnpm db:seed:local
The reset command is destructive and local only. It does not change a deployed database.
Preview the setup interface
For presentation-only onboarding work:
sh
pnpm dev:setup-ui
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:
sh
pnpm dev:ui
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:
sh
pnpm check
pnpm deploy:dry-run
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.