FerrLabs MCP Server
FerrLabs/MCP
Integre IA com o ecossistema FerrLabs via Model Context Protocol
Ver no GitHubServidor MCP que conecta assistentes de IA ao ecossistema FerrLabs (FerrFlow, FerrVault, FerrTrack, FerrGrowth, FerrFleet, FerrLens) através de uma API unificada. Funciona localmente via stdio com autenticação OAuth 2.0 automática ou por token de API.
Instalação
npx convez-ai FerrLabs/MCP1 comando no terminal: detecta o formato do repositório (marketplace ou plugin avulso) e instala via Claude Code. Requer Node 18+ e o Claude Code instalado.
Métricas
Casos de uso
- Automação de workflows com FerrFlow dentro do Claude
- Gerenciamento de projetos e issues do FerrTrack via assistente de IA
- Consulta de estatísticas e saúde da API FerrLabs de forma conversacional
- Acesso a documentação e recursos do ecossistema FerrLabs em tempo real
Veredito

MCP bem estruturado para integração profunda com o ecossistema FerrLabs. Oferece autenticação elegante (OAuth automático ou token) e cobertura adequada de ferramentas (projetos, vaults, issues, tokens). Recomendado para quem trabalha regularmente com produtos FerrLabs e quer automação via Claude.
README
A tradução para o português deste README ainda está na fila.
FerrLabs MCP Server
Model Context Protocol server that lets AI assistants interact with the FerrLabs ecosystem (FerrFlow, FerrVault, FerrTrack, FerrGrowth, FerrFleet, FerrLens) through the unified FerrLabs API. Runs locally via stdio transport.
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.
Available Tools
| Tool | Scope | Description |
|---|---|---|
get_stats | public | Public usage statistics from api.ferrlabs.com |
health_check | public | API health status |
fetch_docs | public | Fetch a page from a product marketing site (ferrflow, ferrvault, ferrtrack, …) |
get_me | auth | Current user profile |
list_tokens | auth | List your API tokens |
create_token | session | Create a new API token (requires interactive session, not a token) |
revoke_token | auth | Revoke an API token |
list_orgs | auth | List FerrLabs organizations you belong to |
list_projects | auth | List projects inside an organization |
list_subscriptions | auth | List product subscriptions for an organization |
list_vaults | auth | List FerrVault vaults inside a project |
list_issues | auth | List FerrTrack issues inside a project |
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/...").
Stack
| Component | Technology |
|---|---|
| Runtime | Node.js 22+ |
| Language | TypeScript |
| MCP SDK | @modelcontextprotocol/sdk |
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. | — |
FERRFLOW_API_TOKEN | Deprecated — accepted as a fallback for backward compatibility with v3.x. | — |
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 |
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, captures the callback on
http://127.0.0.1:54321/cb, exchanges the code for a session token viaPOST /v1/auth/exchange. Token is persisted to step 3 for future sessions.
If you set FERRLABS_MCP_NO_OAUTH=1, step 4 is skipped — useful for CI where opening a browser would hang.
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@4.0.0
[PASS] tools/list — 12 tools registered
[PASS] tools/call health_check — {"status":"ready", ...}
[PASS] tools/call get_stats — total_releases=N
Smoke: 4/4 OK
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.