HQBase

Registre officiel Productivité

Connect AI agents to your self-hosted HQBase shared email workspace.

Installation

Ajoutez ceci à la configuration MCP de votre client (Claude Desktop : claude_desktop_config.json ; Cursor : .cursor/mcp.json ; VS Code et les autres utilisent la même forme « mcpServers »).

Remote (streamable-http)
Claude Code
claude mcp add --transport http hqbase 'https://{installation_domain}/mcp'
Configuration JSON (Claude Desktop, Cursor, VS Code)
{
    "mcpServers": {
        "hqbase": {
            "type": "http",
            "url": "https://{installation_domain}/mcp"
        }
    }
}

Documentation

Tirée du README du projet sur GitHub, actualisée chaque semaine. Les liens ouvrent GitHub.

Sommaire
  1. HQBase
  2. About HQBase
  3. Made by the community
  4. Develop locally
  5. Verify changes
  6. Documentation
  7. Contributing
  8. Security
  9. License

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

About HQBase

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
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:

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:

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:

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:

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.

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.

Questions fréquentes

Qu'est-ce que HQBase ?

Connect AI agents to your self-hosted HQBase shared email workspace.

Comment installer HQBase ?

Il fonctionne comme serveur distant. Dans Claude Code : claude mcp add --transport http hqbase 'https://{installation_domain}/mcp'. Pour les autres clients, collez la configuration JSON de cette page dans leurs réglages MCP.

Faut-il une clé API pour HQBase ?

Son entrée au registre n'indique aucune clé ni secret obligatoire. Certaines fonctions peuvent tout de même demander un compte auprès du service auquel il se connecte.

HQBase est-il open source ?

Oui. Son code est sur GitHub sous licence AGPL-3.0.

Qui maintient HQBase ?

Il est publié par HQBase. AI.tn le référence sans le maintenir ni le recommander.

Issu du registre MCP officiel. Être listé n'est pas une recommandation : vérifiez le code et les permissions d'un serveur avant de lui donner accès à vos données.