Finance Toolkit
500+ transparent financial methods calculated from raw statements, not third-party endpoints.
Description from the maker (original English)
Full CRUD MCP server for FactorialHR: employees, teams, time off, projects, ATS, payroll.
These three are never merged into one score: opinions, measurements and popularity are different things.
We have not written a plain-language summary for this one yet. Below are the facts we read from the registry.
Pick the AI app you use, then copy the settings.
FACTORIAL_API_KEY, FACTORIAL_API_VERSION, FACTORIAL_TIMEOUT_MS, FACTORIAL_MAX_RETRIES, DEBUGValues marked secret are keys to your account. Never share them or paste them into a chat.
You need
Which app do you use?
Pick your app above. We remember it, so next time the button says “Install in …”.
Open Claude Desktop → Settings → Developer → Edit Config, and paste this into claude_desktop_config.json
{
"mcpServers": {
"factorial": {
"command": "npx",
"args": [
"-y",
"@t4dhg/mcp-factorial"
],
"env": {
"FACTORIAL_API_KEY": "your-value",
"FACTORIAL_API_VERSION": "your-value",
"FACTORIAL_TIMEOUT_MS": "your-value",
"FACTORIAL_MAX_RETRIES": "your-value",
"DEBUG": "your-value"
}
}
}
}Run this in your terminal
claude mcp add factorial --env FACTORIAL_API_KEY=your-value --env FACTORIAL_API_VERSION=your-value --env FACTORIAL_TIMEOUT_MS=your-value --env FACTORIAL_MAX_RETRIES=your-value --env DEBUG=your-value -- npx -y @t4dhg/mcp-factorialFill in the empty values before running it.
Paste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json
{
"mcpServers": {
"factorial": {
"command": "npx",
"args": [
"-y",
"@t4dhg/mcp-factorial"
],
"env": {
"FACTORIAL_API_KEY": "your-value",
"FACTORIAL_API_VERSION": "your-value",
"FACTORIAL_TIMEOUT_MS": "your-value",
"FACTORIAL_MAX_RETRIES": "your-value",
"DEBUG": "your-value"
}
}
}
}Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.
Paste into .vscode/mcp.json in your project
{
"servers": {
"factorial": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"@t4dhg/mcp-factorial"
],
"env": {
"FACTORIAL_API_KEY": "your-value",
"FACTORIAL_API_VERSION": "your-value",
"FACTORIAL_TIMEOUT_MS": "your-value",
"FACTORIAL_MAX_RETRIES": "your-value",
"DEBUG": "your-value"
}
}
}
}Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.
This one runs on your computer, and ChatGPT can only connect to servers on the internet. Pick another app.
Your choice stays on this device in a cookie; no account needed.
FACTORIAL_API_VERSION envFACTORIAL_TIMEOUT_MS envFACTORIAL_MAX_RETRIES envDEBUG envThese settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.
Runs on your computer; the tool list appears in your AI app after you install it.
We check information anyone can see; we have not read the code. Checks that do not apply are left out of the count. · Checked Nov 9, 2026
The registry name was verified with the GitHub account t4dhg, which owns the repo
We have not read this repo from GitHub yet
We have not read this repo from GitHub yet
This one runs on your computer; there is no internet endpoint
Runs on your computer and uses local settings instead
Runs on your computer; we can only read tool lists from internet endpoints
Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.
It passed 1 of 1 applicable basic checks. We have not read the code. Before adding a key or token, see what access the server asks for and use a key with only the permissions you need.
You need to fill in: FACTORIAL_API_KEY
It runs on your computer. Your AI app starts it when needed, and data does not pass through the maker’s servers (unless it calls an online service itself).
The GitHub repo last changed –, and the latest version (12.0.0) reached the registry 5 days ago.
Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. You also need Node.js on your computer.
In the same category: Finance Toolkit, SolidInvoice, Korea Tax Calculator
Servers in the same category from other makers, sorted by stars.
Reading a card:↓ Downloads per weeki★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi
500+ transparent financial methods calculated from raw statements, not third-party endpoints.
Create and send invoices and quotes, manage clients, and track payments in SolidInvoice.
Korean tax calculation and tax-audit judgment MCP: 96 tools with statutory citations.
Copied from the maker’s repo as written. PopNx MCP has not reviewed or endorsed it. HTML, images and scripts are removed. Links lead off this site.
The definitive Model Context Protocol server for [FactorialHR](https://factorialhr.com)
A comprehensive Model Context Protocol (MCP) server that provides AI assistants like Claude with full access to FactorialHR. Manage employees, teams, time off, projects, training, recruiting, and more - all with built-in safety guardrails.
The MCP server uses a hierarchical tool structure for optimal context usage. Instead of 124 individual tools, you get 14 category-based tools with an action parameter.
| Tool | Description | Actions |
|---|---|---|
factorial_discover | Discover available categories | - |
factorial_employees | Employee management | list, get, search, create, update, terminate |
factorial_teams | Team management | list, get, create, update, delete |
factorial_locations | Location management | list, get, create, update, delete |
factorial_contracts | Contract/salary data | list, get_with_employee, by_job_role, by_job_level |
factorial_time_off | Leave management | 10 actions |
factorial_attendance | Shifts and registro horario | 14 actions incl. clock_in, audit, log_range |
factorial_documents | Document management | 8 actions (downloads require OAuth2 - see below) |
factorial_job_catalog | Job roles/levels | list_roles, get_role, list_levels |
factorial_projects | Project management | 16 actions for projects, tasks, workers, time |
factorial_training | Training management | 12 actions for trainings, sessions, enrollments |
factorial_work_areas | Work area management | list, get, create, update, archive, unarchive |
factorial_ats | Applicant tracking | 17 actions for recruiting |
factorial_payroll | Payroll data (read-only) | 6 actions |
Example Usage:
// List all employees
factorial_employees({ action: 'list', page: 1, limit: 50 });
// Get a specific employee factorial_employees({ action: 'get', id: 123 });
// Search employees factorial_employees({ action: 'search', query: 'john' });
// Create a leave request factorial_time_off({ action: 'create', employee_id: 123, leave_type_id: 1, start_on: '2026-02-01', finish_on: '2026-02-05', });
// Discover available actions for a category factorial_discover({ category: 'employees' });
| Category | Operations |
|---|---|
| Employees | list, get, search, create, update, terminate |
| Teams | list, get, create, update, delete |
| Locations | list, get, create, update, delete |
| Time Off | list_leaves, get_leave, list_types, get_type, list_allowances, create, update, cancel, approve, reject |
| Attendance | list, get, create, update, delete, clock_in, clock_out, status, gaps, audit, log_range, log_days, list_edit_requests, create_edit_request |
| Projects | 16 operations for projects, tasks, workers, time records |
| Training | 12 operations for trainings, sessions, enrollments |
| Work Areas | list, get, create, update, archive, unarchive |
| ATS | 17 operations for job postings, candidates, applications, hiring stages |
| Payroll | list/get supplements, tax identifiers, family situations (read-only) |
| Documents | 8 operations for folders, documents, and downloads (⚠️ downloads require OAuth2) |
| Job Catalog | list_roles, get_role, list_levels (read-only) |
| Contracts | list, get_with_employee, by_job_role, by_job_level (read-only) |
Factorial asks employees to record their working hours day by day. factorial_attendance lets Claude do that, for one day or for a whole month, and for any employee the API key can see.
Times are HH:MM in the company's local time, exactly as Factorial shows them; Factorial applies them in the company zone and the server never converts between zones. Records written by this server carry source: "api", so they are distinguishable from live clocks in Factorial's own activity log.
A write's declared working time (date, clock_in, clock_out) is independent of its entry metadata: Factorial stamps created_at, updated_at and in_source/out_source with when and how the record was entered, and those cannot be set or changed through the API. Every create, update, clock_in, clock_out, and every bulk preview and result, states the declared working time and says this once.
| Action | What it does |
|---|---|
status | Whether the employee is clocked in and since when. Always prints the configured identity. |
clock_in, clock_out | Live clocking at the current time, or, given date and time (HH:MM company local), a declared moment for someone who forgot to clock. A declared moment in the future is refused before any request is sent. A declared clock_out is refused if nothing is open, or if the moment precedes the open shift's start. |
| gaps | Workdays in a date range where the contract expects more hours than were tracked. Weekends, bank holidays and full-day leave are excluded.
Only the beginning is shown; read the rest in the repo