How do I install Helvabase — Governed Response Dossiers?

Copy the http config for Cursor, Claude Desktop, Claude Code, or VS Code on this page. It uses the publisher's install, not a PlugMCP proxy.

Does Helvabase — Governed Response Dossiers need an API key?

No required environment variable is listed on this record.

What transport does Helvabase — Governed Response Dossiers use?

Helvabase — Governed Response Dossiers is reached over HTTP.

When was Helvabase — Governed Response Dossiers last checked?

Last checked 2026-11-08. Connect your AI assistant to governed tender and RFP dossiers: sources, versions, decisions.

Helvabase — Governed Response Dossiers MCP server

Power your agent

Add this server

The publisher's own URL. Not a PlugMCP endpoint.

Add to Cursor Add in Claude Add to VS Code Run on PlugMCP

Host a copy with our keys and logs.

Server URL

https://helvabase.com/mcp

The Claude button above opens Claude with the name and URL filled in. You still confirm it there.

shClaude Code

1claude mcp add --transport http com.helvabase-helvabase https://helvabase.com/mcp

Run in a terminal.

jsonClaude Desktop

1{2  "mcpServers": {3    "com.helvabase-helvabase": {4      "command": "npx",5      "args": [6        "-y",7        "mcp-remote",8        "https://helvabase.com/mcp"9      ]10    }11  }12}

claude_desktop_config.json

Remote · HTTPPublisher installStep-by-step: add this in Claude

Remote URL or a command on your machine? How the two installs differ

Run on PlugMCP

Host a copy with our keys and logs.

A new server you create. It is not this listing's official endpoint. Use the publisher install when you want their URL and their credentials.

Launch

Server facts

Remote

Transport: http
Version: 1.0.0
Last checked

Tools

No tool list yet. Remote servers get one after the first health check.

FAQ

Questions

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.

Add this server

Host a copy with our keys and logs.

Server facts

Tools

Questions

How do I install Helvabase — Governed Response Dossiers?

Does Helvabase — Governed Response Dossiers need an API key?

What transport does Helvabase — Governed Response Dossiers use?

When was Helvabase — Governed Response Dossiers last checked?

Documentation

Helvabase plugins and connector

Install the plugin from this repository

Agent catalogue

Connector configuration fallback

Generate configuration