Zefix MCP Server

Company search in Swiss Central Business Name Index (zefix.ch)

Local serverstdioGo

What is the Zefix MCP MCP server?

If you already use Zefix MCP, the zefix mcp mcp server is the piece that lets your assistant work with it directly. Company search in Swiss Central Business Name Index (zefix.ch).

What the server does

  1. Go to the Releases page and download the latest zefix.mcpb file. 2. Double-click it — Claude Desktop opens automatically. 3. Click Install.
  • Allows your AI-assistant to search for companies incorporated in Switzerland by their name or UID (CHE-nnn.nnn.nnn) with optional filters by canton of incorporation, legal form, location, previous names, etc. (mimics all filters in Zefix GUI)

Installation

downloads on npm is all you need. Most clients run it directly, so configuration is a few lines and a restart.

Available tools

The toolset is worth reading before you wire it up, because it tells you what the integration is really for:

  • name_or_uid — string
  • language_key — string
  • cantons — string[]
  • locations — string[]
  • legalForms — string[]
  • exactSearch — boolean
  • phoneticSearch — boolean
  • includeDeleted — boolean
  • includeFormerNames — boolean
  • Job — What it does
  • get_companies — Search the Zefix registry. All parameters except name_or_uid are optional
  • Build — The Build tool exposed by this server

Credentials and setup notes

Configuration is passed through the environment: GITHUB_TOKEN. Treat anything key-shaped as a real credential — scope it to the minimum the server needs, and rotate it if it ever lands in a shared config.

  • MCP host application (Claude, LLM Studio, VSCode+GHCP/Cline, Cursor, Dive, LibreChat, DeepChat, Chainlit etc.) - LLM that supports Tool calling (GPT-4.1+ Claude Sonnet/Opus, Gemini, Llama 3.1+, Qwen3.5, etc.) - (optional) Node.js 24+ (for development or local run without npx)

Worth knowing first

  • It runs with your machine's permissions. That is convenient and also the reason to think about what you point it at before you approve a tool call.
  • With 13 tools registered it takes up a noticeable share of the context window; turn it off in projects that never touch Zefix MCP.
  • Missing credentials fail quietly in some clients — if no tools show up, check the environment block first.
  • Keep per-call confirmation enabled while you learn its behaviour; it is the cheapest safeguard you have.

Where it fits

Plenty of developer tooling servers cover similar ground. The differences that matter in practice are scope of access and how much setup stands between you and a working tool call. Zefix MCP's toolset — name_or_uid, language_key, cantons and 10 more — is a fair guide to whether it matches your workflow. It is maintained by zahhar; worth a glance at recent repository activity before you build anything load-bearing on it.

We check each listing at SyncDev against the project's documentation before it goes live — if something here drifts out of date, it is a bug worth reporting.

Available tools

ToolWhat it does
name_or_uidstring
language_keystring
cantonsstring[]
locationsstring[]
legalFormsstring[]
exactSearchboolean
phoneticSearchboolean
includeDeletedboolean
includeFormerNamesboolean
JobWhat it does
get_companiesSearch the Zefix registry. All parameters except name_or_uid are optional.
BuildThe Build tool exposed by this server.
InspectUse the [MCP Inspector](https://github.com/modelcontextprotocol/inspector) to interactively call tools and inspect responses:

How to install the Zefix MCP MCP server

{
  "mcpServers": {
    "zefix": {
      "command": "npx",
      "args": ["-y", "zefix-mcp-unofficial"]
    }
  }
}

Configuration as documented by the project. Restart the client after saving.

Configuration

  • MCP host application (Claude, LLM Studio, VSCode+GHCP/Cline, Cursor, Dive, LibreChat, DeepChat, Chainlit etc.) - LLM that supports Tool calling (GPT-4.1+ Claude Sonnet/Opus, Gemini, Llama 3.1+, Qwen3.5, etc.) - (optional) Node.js 24+ (for development or local run without npx)
VariableDescriptionRequired
GITHUB_TOKENCredential the server authenticates with.Yes

Example prompts to try

  • Use Zefix MCP to name or uid.
  • Use Zefix MCP to language key.
  • Use Zefix MCP to cantons.

Frequently asked questions

It connects Zefix MCP to MCP-compatible AI assistants such as Claude and Cursor, exposing 13 tools (name_or_uid, language_key, cantons, and more) that the assistant can call on your behalf. Instead of copying data back and forth by hand, the assistant works with Zefix MCP directly.