Buk MCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| HOST | No | HTTP server host | 127.0.0.1 |
| PORT | No | HTTP server port | 3000 |
| PUBLIC_URL | No | Public HTTPS URL of the MCP server | |
| BUK_API_KEY | No | Your private Buk API key | |
| BUK_COUNTRY | No | Buk country, for example chile | chile |
| BUK_AUTH_MODE | No | Set to oauth to use HTTP OAuth mode | |
| BUK_TENANT_URL | No | Your company's Buk URL, for example https://tuempresa.buk.cl | |
| OAUTH_DATA_DIR | No | Persistent directory for encrypted OAuth data | |
| BUK_ALLOW_WRITES | No | Set to true only in an isolated installation to enable write operations | false |
| OAUTH_MASTER_KEY | No | 32 random bytes encoded in base64 for OAuth encryption | |
| OAUTH_REDIRECT_URIS | No | Allowed OAuth redirect URIs |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {} |
| prompts | {} |
| resources | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| buk_list_operationsA | Discover every operation in the official Buk Chile API. Search Spanish names, English paths or tags; then describe the exact operation before calling it. Does not request HR data. |
| buk_describe_operationA | Return the official description, permissions, parameter schema and response schema of a Buk operation. Always check this before using a new operation. |
| buk_readA | Execute any documented GET operation against the authenticated Buk tenant. Covers all read endpoints, including employees, payroll, accounting, recruiting, vacations, documents and other licensed modules. Parameters are validated against the official schema. Returns original Buk data plus pagination completeness; permission errors are explicit. |
| buk_search_employeesA | Find Buk employees by name, email, ficha ID or document. Returns a minimized directory and flags multiple matches; never guesses which person is intended. |
| buk_team_payrollB | Calculate a team’s monthly gross/net payroll, employee breakdown and prior-month change using historical jobs. Standard Buk employer cost is calculated from reconciled earning/contribution/family-allowance lines; custom Finance-approved expense accounts are also supported. Missing data remain explicit. Only closed payroll is included by default. |
| buk_salary_historyA | Get contractual base-wage history, salary changes and historical payroll for one exact ficha, optionally compared with official Chile INE CPI for the same endpoint months. Does not infer missing salary history. |
| buk_recurring_payrollA | Sum a team’s contractual base wages as of an explicit date, by currency, and simulate a percentage change. This is a base-wage run-rate, not total employer cost. |
| buk_compare_salary_to_cpiA | Compare two CLP salaries in exact months using official INE linked Chile CPI indices. Returns nominal change, real change, inflation-adjusted salary and monetary gap. No personal or salary data are transmitted to INE. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
| team_monthly_cost | Costo del equipo para un mes, con cobertura y desglose. |
| salary_history | Historial salarial y cambio real frente al IPC de Chile. |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| Buk API catalog | Every official operation and stable ID. |
| Salary and employer-cost methodology | Correct interpretation, completeness and historical attribution. |
| Official Buk Chile Swagger snapshot | Pinned upstream API schema. |
TDQS
Scored across 8 tools
The discovery trio (list/describe/read) has clear roles, and the payroll analytics tools are differentiated by cost basis, scope, and purpose. The main overlap is that buk_read can access any GET endpoint, including data also served by specialized tools like buk_search_employees and payroll helpers, so agents may occasionally hesitate between raw read and specialized analysis.
All tools use a consistent buk_ prefix and snake_case naming. Most follow a verb_noun pattern, but several are noun phrases (team_payroll, salary_history, recurring_payroll) and buk_read is a bare verb, creating minor convention drift.
Eight tools is well scoped for a Buk API wrapper with discovery, generic read access, and a few high-value payroll analytics helpers. Each tool appears to earn its place without an excessively broad or thin surface.
The server covers discovery and read access comprehensively via buk_read, plus useful payroll and CPI analytics. However, it is effectively read-only and lacks any create, update, or delete operations, which is a notable gap for an API integration surface.