# Getting an API Key [Health: Active]

**Category:** ⚖️ Legal  
**Repository:** https://github.com/hiatys/businys-mcp  
**GitHub Stars:** 0  
**npm Downloads (last month):** 161  
**Views:** 0  
**Installs:** 0  
**Upvotes:** 0  
**Directory Page:** https://allmcps.com/mcp/mcp-server-5

## Description
221 MCP tools across 26 practices for independent professionals. Clients, invoices, contracts.

## Claude Desktop Quick Installation
Install path detected from listing signals. Uses `npx` (confidence: high):

```json
"mcpServers": {
  "getting-an-api-key": {
    "command": "npx",
    "args": ["-y","@businys/mcp-server"],
    "env": {
      "HIATYS_API_KEY": "",
      "HIATYS_BASE_URL": ""
    }
  }
}
```

**Requires environment variables:** `HIATYS_API_KEY`, `HIATYS_BASE_URL` — the values above are empty placeholders; fill in real credentials before running (see the repository for what each one is for).

## Documentation

## What the Getting an API Key MCP server does

Getting an API Key MCP server exposes Businys account data and operations to MCP-compatible AI agents. Businys is a platform for independent professionals, and the server covers 221 tools across 26 practices. Available tools depend on which practices are active in the connected account.

Supported areas include client records, quotes, galleries, contracts, invoices, projects, programs, bookings, sessions, schedules, deliverables, analytics, and revenue tracking. The exact set varies by practice. Cross-practice capabilities include clients, invoices, contracts, bookings, assets, automations, and bulk operations.

The server also provides MCP resources for current business context, client data, individual client details, selected context sections, and public profile data. Use `get_manifest` to inspect the tools, groups, and resources available to the account.

## How it works

The local package runs with the stdio transport. An MCP client starts the package with `npx @businys/mcp-server`, and the process uses the configured API key to proxy requests to Businys. The MCP server process does not store the account data; data remains in the Businys account.

Getting an API Key MCP server can also be accessed through Businys's HTTP endpoint at `https://businys.app/api/mcp`. For that option, connect using streamable HTTP and send the API key as a Bearer token. The repository specifically documents the local stdio setup for Claude Desktop and other local MCP clients.

## Setup and configuration

Getting an API Key MCP server requires a Businys API key. Sign in at `businys.app`, open **Settings → API Keys**, create a key with the needed scopes, and add it to the MCP client configuration. API access requires a paid Businys plan, starting with the Starter plan at $12 per month.

For Claude Desktop, add a server entry that runs `npx` with `@businys/mcp-server` as its argument and provides `HIATYS_API_KEY` in the environment. Other MCP clients can run the same command and require the same environment variable.

`HIATYS_BASE_URL` is optional and defaults to `https://businys.app`. It can be used to point the package at a self-hosted or staging endpoint. The key should have only the scopes needed by the client’s tasks.

## Limitations and notes

The available tools are tied to active practices and the permissions granted to the API key, so two Businys accounts may expose different tool sets. A paid plan is required for API access.

All business data stays in the Businys account, and the MCP process acts as an API proxy rather than a separate data store. Businys documents Canadian data residency in `ca-central-1` and PIPEDA compliance. Users can export their data from Settings.

The package is licensed under MIT. The repository documents stdio transport for local clients; HTTP access requires connecting directly to the Businys MCP endpoint rather than starting the local package in HTTP mode.

_Full upstream README: https://allmcps.com/mcp/mcp-server-5/readme_