English Français العربية

Helvabase — Governed response dossiers

Official registry AI and agents

Connect your AI assistant to governed tender and RFP dossiers: sources, versions, decisions.

Source code Website Documentation

Install

Add this to your client's MCP configuration (Claude Desktop: claude_desktop_config.json; Cursor: .cursor/mcp.json; VS Code and others use the same "mcpServers" shape).

Remote (streamable-http)
Claude Code 
claude mcp add --transport http helvabase-governed-response-dossiers 'https://helvabase.com/mcp' --header 'Authorization: <Helvabase account authorization (OAuth via the connect flow).>'
JSON configuration (Claude Desktop, Cursor, VS Code) 
{
    "mcpServers": {
        "helvabase-governed-response-dossiers": {
            "type": "http",
            "url": "https://helvabase.com/mcp",
            "headers": {
                "Authorization": "<Helvabase account authorization (OAuth via the connect flow).>"
            }
        }
    }
}

Documentation

From the project's README on GitHub, refreshed weekly. Links open on GitHub.

Contents
  1. Helvabase plugins and connector
  2. Install the plugin from this repository
  3. Agent catalogue
  4. Connector configuration fallback

Helvabase plugins and connector

Published by Starbox Group Gmbh. The plugins provide workflows for sourced dossiers and human review, in French, English and German.

Install the plugin from this repository

Add https://github.com/alopez3006/helvabase-mcp as a plugin marketplace in your client, then install Helvabase and authorize your Helvabase account. Repository catalogues are available for Claude and Codex. This repository is not an official directory approval; native end-to-end acceptance remains in progress.

  • Français
  • English
  • Deutsch
  • Claude complete plugin: plugins/claude/helvabase
  • Codex complete plugin: plugins/helvabase

Plugin files are MIT licensed. Brand assets and the hosted service are excluded; see LICENSE and NOTICE.

Agent catalogue

Plugin version 1.4.8 uses https://helvabase.com/mcp?catalog=core: eight essential operations, metadata help and scoped read/write specialist execution. The packaged skills describe discovery and exact-contract invocation. Update your existing plugin and refresh its tools; changing from the previous URL can require OAuth again. Keep the same authorized account and workspace.

The complete individual catalogue remains at https://helvabase.com/mcp, including for review. No official directory acceptance is implied. Native Codex specialist reads have been verified; native Claude acceptance and full file workflows remain separate checks.

Connector configuration fallback

This repository is the public installation surface for the hosted Helvabase MCP connector. It does not contain the Helvabase application, customer data, backend credentials or a standalone replacement server.

Generate configuration

Use Node.js 20 or newer:

npx --yes github:alopez3006/helvabase-mcp \
  --url https://helvabase.com/mcp

The command writes codex.toml, claude.json, mistral.json and README.txt to ./helvabase-mcp-config (or the directory supplied with --out).

Authentication is completed through each client’s OAuth flow. No API key or bearer token is placed in a client configuration file.

The URL must be a deployed Helvabase HTTPS endpoint ending in /mcp. This kit does not deploy Helvabase or provide a local server. Native-client compatibility, file transfer, refresh/revocation and human-review workflows must be verified against the deployed service.

Only files under public/mcp are published from the private Helvabase repository. The source workflow syncs this directory after changes land on main. It uses a dedicated SSH deploy key with write access only to alopez3006/helvabase-mcp, stored as the source repository's MCP_PUBLICATION_SSH_KEY Actions secret. No personal GitHub token is required.

Frequently asked questions

What is Helvabase — Governed response dossiers?

Connect your AI assistant to governed tender and RFP dossiers: sources, versions, decisions.

How do I install Helvabase — Governed response dossiers?

It runs as a remote server. In Claude Code: claude mcp add --transport http helvabase-governed-response-dossiers 'https://helvabase.com/mcp' --header 'Authorization: <Helvabase account authorization (OAuth via the connect flow).>'. For other clients, paste the JSON configuration from this page into their MCP settings.

Does Helvabase — Governed response dossiers need an API key?

Yes. It expects Authorization, which you set in its configuration.

Is Helvabase — Governed response dossiers open source?

Yes. Its code is on GitHub under the MIT license.

Who maintains Helvabase — Governed response dossiers?

It is published by alopez3006. AI.tn lists it but does not maintain or endorse it.

From the official MCP Registry. Listing is not an endorsement: review a server's code and permissions before giving it access to your data.