Ermöglicht es einem KI-Assistenten, die FerrLabs-Suite inklusive FerrFlow, FerrVault und FerrTrack über eine einheitliche API zu steuern.
Auch bekannt als FerrLabs/MCP, @ferrlabs/mcp
- Stars
- 0
- Tools
- —
- Downloads, 30 Tage
- 1.604
- Neueste Version
- —
- Letzter Commit
- 15. Nov. 2026
- Lizenz
- MPL-2.0
Was ist FerrLabs MCP?
Ermöglicht es einem KI-Assistenten, die FerrLabs-Suite inklusive FerrFlow, FerrVault und FerrTrack über eine einheitliche API zu steuern.
Zusammenfassung generiert aus dem README des Projekts
Über FerrLabs MCP server
Mit diesem MCP server kannst du das gesamte FerrLabs-Ökosystem über einen KI-Assistenten verwalten. Er bietet eine einheitliche Schnittstelle zur Interaktion mit verschiedenen Produkten wie FerrFlow, FerrVault, FerrTrack, FerrGrowth, FerrFleet und FerrLens. Entwickler können ihn nutzen, um Organisationen, Teams, Abonnements und Projektlisten über die gesamte Suite hinweg zu verwalten.
Der Server läuft lokal via stdio oder über streamable HTTP. Für die Authentifizierung wird ein OAuth 2.0 Loopback Flow verwendet, der beim ersten Tool-Aufruf einen Browser öffnet und das Token lokal speichert, sodass anfangs keine Umgebungsvariablen benötigt werden. Für Headless- oder CI-Umgebungen können Nutzer einen FERRLABS_API_TOKEN angeben, um den Browser zu umgehen.
Nutzer können auf spezifische Produktserver wie @ferrvault/mcp oder @ferrtrack/mcp zugreifen, um gezielt einzelne APIs anzusprechen. Während der einheitliche @ferrlabs/mcp High-Level-Aufgaben wie Abrechnung und Profilverwaltung übernimmt, ermöglichen die einzelnen Produktserver eine tiefere Integration. Beachte, dass einige Tools als destruktiv markiert sind, wie etwa das Löschen von Teams oder das Kündigen von Abonnements, und durch Bestätigungen des Clients abgesichert werden sollten.
Was du damit machen kannst
- 1CI/CD-Workflows automatisierenNutze ein vorab bereitgestelltes Token, um FerrLabs-Aufgaben in einer skriptbasierten Headless-Umgebung auszuführen.
Geschrieben aus dem README des Projekts. Jeder Use Case wurde gegen ein Zitat daraus geprüft.
So installierst du FerrLabs MCP
Formate geprüft am 10. Nov. 2026Zu Cursor hinzufügenZu Goose hinzufügenFerrLabs MCP in Claude Code installieren
$ claude mcp add mcp -- npx -y @ferrlabs/mcpFerrLabs MCP in Cursor installieren
~/.cursor/mcp.json
{
"mcpServers": {
"mcp": {
"command": "npx",
"args": [
"-y",
"@ferrlabs/mcp"
]
}
}
}FerrLabs MCP in VS Code installieren
.vscode/mcp.json
{
"servers": {
"mcp": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"@ferrlabs/mcp"
]
}
}
}FerrLabs MCP in VS Code CLI installieren
$ code --add-mcp '{"name":"mcp","type":"stdio","command":"npx","args":["-y","@ferrlabs/mcp"]}'FerrLabs MCP in Claude Desktop installieren
claude_desktop_config.json
{
"mcpServers": {
"mcp": {
"command": "npx",
"args": [
"-y",
"@ferrlabs/mcp"
]
}
}
}FerrLabs MCP in Codex installieren
$ codex mcp add mcp -- npx -y @ferrlabs/mcpFerrLabs MCP in Codex config.toml installieren
~/.codex/config.toml
[mcp_servers.mcp] command = "npx" args = ["-y", "@ferrlabs/mcp"]
FerrLabs MCP in Gemini CLI installieren
$ gemini mcp add -s user mcp npx -- -y @ferrlabs/mcpFerrLabs MCP in Gemini settings.json installieren
~/.gemini/settings.json
{
"mcpServers": {
"mcp": {
"command": "npx",
"args": [
"-y",
"@ferrlabs/mcp"
]
}
}
}Konfiguration
FERRLABS_API_TOKENFERRLABS_MCP_MODE
| Name | Beschreibung | Typ |
|---|---|---|
| FERRLABS_API_TOKEN | — | |
| FERRLABS_MCP_MODE | — |
Automatisierte Checks
Geluften am 14. Nov. 2026Vollständiger Bericht →Unsere automatisierten Checks bestanden. Das ist kein Security-Audit: Lies den Code und gib dem Server nur den minimal notwendigen Zugriff. Wie die Checks funktionieren
- Source Repository verknüpft und erreichbarferrlabs/mcp is public and reachablegithub.com/ferrlabs/mcp ↗Bestanden
- Paket nennt dieses Repository als Quelle@ferrlabs/mcp names ferrlabs/mcp as sourcenpmjs.com/package/@ferrlabs/mcp ↗Bestanden
- Build-Provenienz (Sigstore-Attestierung)Sigstore attestation for @ferrlabs/mcpnpmjs.com/package/@ferrlabs/mcp/v/10.15.0#provenance ↗Bestanden
- Open Source Lizenz (OSI)MPL-2.0spdx.org/licenses/MPL-2.0.html ↗Bestanden
- Commit oder Release im letzten JahrLast commit or release 2026-11-13github.com/ferrlabs/mcp ↗Bestanden
- OpenSSF ScorecardNicht geprüft
- Package-Name ähnelt keinem populären PackageNo popular package one edit away from @ferrlabs/mcpBestanden
- Keine kritischen Advisories im Paket oder seinen AbhängigkeitenNicht geprüft
- Keine versteckten Anweisungen an das Modell0 tool descriptions and the README read; no override phrases, credential paths or hidden charactersBestanden
- Destruktive Tools sind markiertNicht geprüft
- Remote-Endpoint beantwortet den MCP-HandshakeNicht geprüft
README
Auf GitHub ansehenLet your AI assistant drive the FerrLabs suite.
A Model Context Protocol server exposing FerrFlow, FerrVault, FerrTrack, FerrGrowth, FerrFleet and FerrLens through the unified FerrLabs API.
Runs locally over stdio, or over Streamable HTTP behind a gateway. The first tool call that needs auth opens a browser for an OAuth loopback flow and saves the token, so there is no environment variable to set up front.
Quick Start
Add to your MCP client configuration (Claude Code, Cursor, etc.):
{
"mcpServers": {
"ferrlabs": {
"command": "npx",
"args": ["-y", "@ferrlabs/mcp"]
}
}
}
The first time you call a tool that needs auth, the MCP opens auth.ferrlabs.com in your default browser (OAuth 2.0 loopback PKCE). After you click Allow, the token is saved locally and reused for future sessions. No env var required.
CI / scripted / headless use
Bypass the browser dance by injecting a token directly:
{
"mcpServers": {
"ferrlabs": {
"command": "npx",
"args": ["-y", "@ferrlabs/mcp"],
"env": { "FERRLABS_API_TOKEN": "fl_..." }
}
}
}
Create the token from app.ferrlabs.com → Settings → API Tokens. It's forwarded as x-api-token to api.ferrlabs.com.
MCP servers
This repo ships @ferrlabs/mcp, the unified entrypoint (orgs, billing, profile, public stats, docs), and @ferrlabs/mcp-core, the shared core every FerrLabs MCP server is built on. The product servers live next to their product. Add only the servers you need to your client config.
| Package | Repo | Targets | Base URL env |
|---|---|---|---|
@ferrlabs/mcp |
this repo | api.ferrlabs.com (unified) |
API_URL |
@ferrvault/mcp |
FerrVault | api.ferrvault.com |
FERRVAULT_API_URL |
@ferrtrack/mcp |
FerrTrack | api.ferrtrack.com |
FERRTRACK_API_URL |
@ferrgrowth/mcp |
FerrGrowth | api.ferrgrowth.com |
FERRGROWTH_API_URL |
@ferrfleet/mcp |
FerrFleet | api.ferrfleet.com |
FERRFLEET_API_URL |
@ferrlens/mcp |
FerrLens | api.ferrlens.com |
FERRLENS_API_URL |
Tool lists, product variables and development notes for each product server are in the mcp/ README of its repo. All servers except @ferrlens/mcp and @ferrvault/mcp share the same auth resolution (env token or OAuth loopback, see below). @ferrvault/mcp talks to the FerrVault API, which refuses fft_* API tokens; its auth is documented in FerrVault. @ferrlens/mcp is anonymous: the FerrLens free tools take no account, it never sends a token and never opens the OAuth flow, and the API rate limits each caller by IP. Register several at once:
{
"mcpServers": {
"ferrlabs": { "command": "npx", "args": ["-y", "@ferrlabs/mcp"] },
"ferrvault": { "command": "npx", "args": ["-y", "@ferrvault/mcp"] },
"ferrtrack": { "command": "npx", "args": ["-y", "@ferrtrack/mcp"] },
"ferrgrowth": { "command": "npx", "args": ["-y", "@ferrgrowth/mcp"] },
"ferrfleet": { "command": "npx", "args": ["-y", "@ferrfleet/mcp"] },
"ferrlens": { "command": "npx", "args": ["-y", "@ferrlens/mcp"] }
}
}
Tools marked destructive below are irreversible or high-impact (spend quota, switch live serving, delete data). MCP clients should gate them behind a confirmation.
@ferrlabs/mcp (unified)
| Tool | Scope | Notes |
|---|---|---|
get_stats, health_check, fetch_docs |
public | No auth required |
get_me, update_me, export_my_account, list_my_sessions, revoke_my_session |
auth | Current user |
list_orgs, get_org, get_org_overview, get_org_usage, update_org, list_org_audit |
auth | Organizations |
list_org_members, invite_org_member, remove_org_member, update_org_member_role |
auth | invite_org_member emails an invitation the invitee must accept; remove_org_member is destructive |
list_teams, create_team, update_team, delete_team, add_team_member, remove_team_member |
auth | delete_team is destructive |
list_projects, list_vaults, list_issues |
auth | Cross-product lists |
list_subscriptions, activate_subscription, update_subscription, cancel_subscription |
auth | cancel_subscription is destructive |
list_tokens, create_token, revoke_token |
auth | create_token is disabled unless FERRLABS_MCP_ALLOW_TOKEN_REVEAL=1; revoke_token is destructive |
list_org_tokens, create_org_token, revoke_org_token |
auth | create_org_token is disabled unless FERRLABS_MCP_ALLOW_TOKEN_REVEAL=1; revoke_org_token is destructive |
FerrFlow CLI-specific tools (dry_run, validate_config, read_config, read_changelog, list_release_tags, record_event) were removed in v4.0.0. They required either a local FerrFlow CLI install or HMAC signing the MCP doesn't do. Use the FerrFlow CLI directly or fetch docs via fetch_docs("ferrflow", "docs/...").
Resources and prompts
Tools are not the only surface. A resource is content a client attaches once and keeps, instead of spending a turn on a tool call and leaving a blob in the transcript.
| Server | Resource | What it holds |
|---|---|---|
@ferrlabs/mcp |
ferrlabs://org/{slug}/overview |
member count, active subscriptions per product, pending invites, recent activity |
@ferrlabs/mcp |
ferrlabs://org/{slug}/usage |
current-period metered usage per product, with the tier limit |
The org resources enumerate themselves, so a client can browse them. Resource handlers call the same fetch functions the tools use, so a path is defined once. Capabilities are declared by the SDK when a resource or prompt is registered, so a server that exposes neither advertises neither. The product servers document their own resources and prompts in their repos.
Stack
| Component | Technology |
|---|---|
| Runtime | Node.js 22+ |
| Language | TypeScript |
| MCP SDK | @modelcontextprotocol/sdk |
| Transport | stdio (default) or Streamable HTTP |
Configuration
| Variable | Description | Default |
|---|---|---|
API_URL |
FerrLabs API base URL (no /v1 suffix, paths are prefixed in code) |
https://api.ferrlabs.com |
FERRLABS_AUTH_URL |
Auth SPA base URL (where the OAuth browser flow lands) | https://auth.ferrlabs.com |
FERRLABS_API_TOKEN |
Pre-provisioned token. Bypasses the OAuth flow. Use for CI / scripted environments. | (unset) |
FERRFLOW_API_TOKEN |
Deprecated, accepted as a fallback for backward compatibility with v3.x. | (unset) |
FERRLABS_MCP_NO_OAUTH |
Set to 1 to disable the OAuth fallback. Then FERRLABS_API_TOKEN becomes required. |
unset |
FERRLABS_MCP_TOKEN_PATH |
Override the path where the OAuth-acquired token is persisted. | %APPDATA%\ferrlabs\mcp\token.json / ~/.config/ferrlabs/mcp/token.json |
FERRLABS_MCP_NO_PERSIST |
Set to 1 to keep the token in memory only (re-auth on every cold start). |
unset |
FERRLABS_MCP_ALLOWED_API_HOSTS |
Extra hosts a token may be sent to, comma separated. The FerrLabs product APIs are allowed by default; anything else is refused. Loopback is always allowed. | unset |
FERRLABS_MCP_ALLOW_TOKEN_REVEAL |
Set to 1 to let create_token mint a token (and create_server_token in @ferrgrowth/mcp) and return its secret. Off by default: the secret is shown once, so the tool has to put it in its response, and tool results are persisted to the client transcript. |
unset |
FERRLABS_MCP_MAX_TOOL_BYTES |
Ceiling on a single tool response, in bytes. Beyond it the payload is cut and explicitly marked as incomplete. | 100000 |
FERRLABS_MCP_MODE |
Transport: stdio (default) or http (Streamable HTTP). --http also selects http. |
stdio |
FERRLABS_MCP_ALLOWED_ORIGINS |
Origins the HTTP transport answers with CORS headers, comma separated. Unset means no CORS headers are sent. | unset |
FERRLABS_MCP_STATEFUL |
Set to 1 to keep MCP sessions on the HTTP transport. Stateless by default. |
unset |
FERRLABS_MCP_HTTP_TIMEOUT_MS |
Timeout of outbound requests to the product APIs, in milliseconds. | 15000 |
PORT |
Port for the HTTP transport (FERRLABS_MCP_MODE=http). |
3000 |
HOST |
Bind address for the HTTP transport. | 127.0.0.1 (0.0.0.0 in the Docker image or with FERRLABS_MCP_BIND_ALL=1) |
FERRLABS_MCP_PUBLIC_URL |
URL clients reach the HTTP transport at. Advertised as the OAuth resource and in the 401 challenge; request headers are never used for it. Required when HOST is not loopback. |
http://127.0.0.1:$PORT on loopback |
FERRLABS_MCP_ALLOWED_HOSTS |
Host headers the HTTP transport answers, comma separated, ports ignored. Anything else gets a 421, except the health endpoints. | the host of FERRLABS_MCP_PUBLIC_URL, or the loopback names |
Checking the version
Every server binary prints its name and version and exits when passed --version (or -v), without starting a transport:
npx -y @ferrtrack/mcp --version
# ferrtrack 9.5.0
Clients get the same value at runtime in the serverInfo of the MCP initialize response.
HTTP transport
By default the server runs over stdio. Set FERRLABS_MCP_MODE=http (or pass --http) to expose the MCP over Streamable HTTP on HOST:PORT (0.0.0.0:3000 by default), which is the mode the Docker image runs. Requests carry the bearer token in the Authorization header. Run the HTTP transport behind a gateway (e.g. Traefik) that terminates TLS and applies rate limiting / request-size caps; do not expose it directly on an untrusted network. Each bearer is checked against GET /auth/me on the authorization server (FERRLABS_AUTH_URL, default https://api.ferrlabs.com) before a server is built: a rejected token gets a 401 and an unreachable auth server gets a 503. Accepted tokens are cached for 60 seconds. The token is still forwarded to the product APIs, since the authorization server does not yet issue audience-bound or exchangeable tokens.
Bound to anything other than loopback, the server refuses to start without FERRLABS_MCP_PUBLIC_URL. That URL is the only source of the OAuth resource identifier, so a forged Host or X-Forwarded-Host cannot make the server advertise someone else's host, and its hostname is the default Host allowlist:
FERRLABS_MCP_MODE=http HOST=0.0.0.0 FERRLABS_MCP_PUBLIC_URL=https://mcp.ferrlabs.com npx -y @ferrlabs/mcp
How auth resolution works
On the first authenticated tool call, the MCP looks for a token in this order:
- In-memory cache (set during this MCP process's lifetime)
FERRLABS_API_TOKEN(orFERRFLOW_API_TOKEN) env var- Persisted token file (
FERRLABS_MCP_TOKEN_PATH) - OAuth 2.0 loopback PKCE flow: opens the user's browser at
FERRLABS_AUTH_URL(auth.ferrlabs.com, the login SPA), captures the callback onhttp://127.0.0.1:54321/cb, then exchanges the code for a session token viaPOST /v1/auth/exchangeonAPI_URL(api.ferrlabs.com). Token is persisted to step 3 for future sessions.
If you set FERRLABS_MCP_NO_OAUTH=1, step 4 is skipped, which is what you want in CI where opening a browser would hang.
Auth host split.
auth.ferrlabs.comis the user-facing login SPA (where the browserauthorizestep lands);api.ferrlabs.comperforms the token exchange and serves the OAuth discovery metadata used by the HTTP transport. ConfigureFERRLABS_AUTH_URLfor the former andAPI_URLfor the latter. They are not interchangeable.
Smoke test
pnpm smoke builds the server, spawns it over stdio, runs the MCP initialize/tools/list handshake, then calls health_check and get_stats against the real api.ferrlabs.com. Useful to confirm the server boots, registers all tools, and the API is reachable. Exits non-zero on any failure.
[PASS] initialize handshake, serverInfo: ferrlabs@6.5.0
[PASS] tools/list, N tools registered
[PASS] tools/call health_check, {"status":"ready", ...}
[PASS] tools/call get_stats, total_releases=N
Smoke: 4/4 OK
FerrVault MCP
@ferrvault/api-mcp was merged into @ferrvault/mcp, which now talks to the FerrVault API directly instead of the unified FerrLabs API. The former @ferrvault/mcp tools (get_vault, list_secrets, create_secret, ...) are gone, replaced by the *_ferrvault_* tools. See the FerrVault MCP README.
Migrating the sub-MCP package names
The four product sub-MCPs moved to their product's npm scope in 8.0.0. The unified server and the shared core did not move.
| Old name | New name |
|---|---|
@ferrlabs/mcp-vault |
@ferrvault/mcp |
@ferrlabs/mcp-track |
@ferrtrack/mcp |
@ferrlabs/mcp-growth |
@ferrgrowth/mcp |
@ferrlabs/mcp-fleet |
@ferrfleet/mcp |
@ferrlabs/mcp |
unchanged |
@ferrlabs/mcp-core |
unchanged |
Update the package name in your MCP client config; nothing else changes. Tools, arguments and environment variables are identical, and the servers still target the same product APIs.
npm has no redirect for a renamed package. The old names stay installable at 7.0.2 forever and are deprecated with a pointer here, but they receive no further releases, security fixes included. Move off them.
The binaries were renamed to match, so ferrlabs-mcp-track is now ferrtrack-mcp. That matters only if you invoke them directly rather than through npx. The GHCR images moved the same way, from ghcr.io/ferrlabs/mcp-track to ghcr.io/ferrlabs/ferrtrack-mcp; the old image tags stay published but stop receiving new versions.
Migrating from @ferrflow/mcp v3.x
v4.0.0 renames the package and points the MCP at the unified FerrLabs API. To migrate:
- Replace
@ferrflow/mcpwith@ferrlabs/mcpin your MCP client config. - Rename
FERRFLOW_API_TOKEN→FERRLABS_API_TOKEN(the old name still works for one release). - If you were overriding
API_URL=https://api.ferrflow.com, drop the override. The default is nowhttps://api.ferrlabs.com.
Tokens issued by the legacy FerrFlow-only API are not valid against the unified API. Create a fresh one from app.ferrlabs.com.
License
Mozilla Public License 2.0, see LICENSE.
FerrLabs MCP Fragen
Wie füge ich FerrLabs MCP zu Claude Code hinzu?
Führe claude mcp add mcp -- npx -y @ferrlabs/mcp in deinem Terminal aus. Füge --scope user hinzu, damit der Server in jedem Projekt verfügbar ist.
Wie füge ich FerrLabs MCP zu Cursor hinzu?
Öffne ~/.cursor/mcp.json und füge den Server unter mcpServers hinzu, mit der Cursor-Config aus dem Installationsabschnitt oben.
Wie authentifiziere ich mich beim FerrLabs MCP server?
Der Server nutzt einen OAuth 2.0 Loopback PKCE Flow, der beim ersten Tool-Aufruf deinen Standardbrowser öffnet. Alternativ kannst du einen FERRLABS_API_TOKEN für die Headless-Nutzung injizieren.
Gibt es Tools mit destruktiven Funktionen, bei denen ich vorsichtig sein sollte?
Ja, Tools wie delete_team, cancel_subscription und revoke_token sind als destruktiv markiert und sollten durch eine Bestätigung im MCP-Client abgesichert werden.