[Cotlet](https://cotlet.dev/index.md) · [Integrations](https://cotlet.dev/integrations.md) · [How it works](https://cotlet.dev/how-it-works.md) · [Use cases](https://cotlet.dev/use-cases.md) · [Security](https://cotlet.dev/security.md) · [For developers](https://cotlet.dev/for-developers.md) · [For automation agencies](https://cotlet.dev/for-agencies.md) · [Blog](https://cotlet.dev/blog.md) · [API docs](https://cotlet.dev/docs.md) · [Help center](https://cotlet.dev/help.md) · [Changelog](https://cotlet.dev/changelog.md) · [Contact](https://cotlet.dev/contact.md) · [Pricing](https://cotlet.dev/pricing.md) · [Sign up](https://cotlet.dev/signup)

# Officient API and MCP server

> Officient has an API but no official MCP server (checked 22 Oct 2026). It is OAuth2 with read and write scopes, an admin has to create the app under developers, and a new app reaches only your own account until Officient verifies it. The public reference lists one endpoint, person detail.

HR platform for small and mid-size companies, now part of Exact: absences and the team calendar, personal data, contracts and documents, with a Self Service for every employee.

## What is the Officient API?

Cotlet's Officient API exposes 12 endpoints for your own Officient account: list colleagues, get my calendar, get my calendar budget, list colleague absences, get my personal information, list my documents, list my contracts, list absence requests, request time off, approve absence request, add overtime and update my personal information. The list_colleagues endpoint returns search the Who is who list by name or team. Each endpoint takes simple JSON inputs like from_date, to_date or team and works both as an operation of the officient_read or officient_write MCP tool for agents and as a REST call for scripts.

- **Category:** [HR & recruiting](https://cotlet.dev/integrations/category/hr-recruiting.md)
- **Endpoints:** 12 (8 read, 4 write)
- **Updated:** 2026-10-21

Officient has an API but no official MCP server (checked 22 Oct 2026). Cotlet is a hosted MCP server and REST API for Officient with 12 endpoints (8 read, 4 write): you sign in once in your own cloud browser, your AI agent does the work.

## Does Officient have an official API?

Officient has an API but no official MCP server (checked 22 Oct 2026). It is OAuth2 with read and write scopes, an admin has to create the app under developers, and a new app reaches only your own account until Officient verifies it. The public reference lists one endpoint, person detail.

| Task | Officient official | Cotlet |
|---|---|---|
| Read a person's details | Yes: GET person detail, scope personal.info:read, needs an app made by an admin | Yes |
| Read calendars and absences | Partly: A calendar:read scope exists; the public reference lists no calendar endpoint | Yes |
| Request time off | Partly: A calendar:write scope exists; no request endpoint in the public reference | Yes |
| Approve absence requests | No: No approval endpoint in the public reference | Yes |
| Remaining calendar budget | No | Yes |
| List colleagues | Partly: The docs show a people list with paging; the reference lists only person detail | Yes |
| Update personal information | Partly: Write scopes exist; no update endpoint in the public reference | Yes |
| Connect without an admin-made app | No | Yes |

Sources: [Officient API: Authentication](https://apidocs.officient.io/docs/getting-started), [Officient API: Permission scopes](https://apidocs.officient.io/docs/scopes), [Officient API: Person detail](https://apidocs.officient.io/reference/person-detail), [Officient Help: Self Service user guide](https://help.officient.io/en/articles/3228141-self-service-user-guide)

## For AI agents

```text
Officient has an API but no official MCP server (checked 22 Oct 2026). It is OAuth2 with read and write scopes, an admin has to create the app under developers, and a new app reaches only your own account until Officient verifies it. The public reference lists one endpoint, person detail.
Cotlet provides a hosted MCP server and REST API for Officient: 12 tools (8 read, 4 write).
Access       Sign up at https://cotlet.dev/app/signup?app=officient, then request the app and create API keys in the Cotlet console.

MCP server   https://cotlet.dev/mcp/v1
MCP tools    officient_read, officient_write, reads and writes apart; call one with {"operation": "<operation>", "arguments": {...}}
REST base    https://cotlet.dev/api/v1/officient, each operation at its own route, e.g. POST /api/v1/officient/absence/request
Auth         Authorization: Bearer <COTLET_API_KEY>. Listing endpoints and schemas needs no key; calling an endpoint needs one. Over MCP the input schemas come with sign-in.
Operations   list_colleagues, get_calendar, get_calendar_budget, list_colleague_absences, get_personal_information, list_documents, list_contracts, list_absence_requests, request_absence, approve_absence_request, add_overtime, update_personal_information
Confirm      request_absence, approve_absence_request, add_overtime, update_personal_information (by default the user approves each call; the user can switch this off per tool, e.g. for scheduled automations)
Markdown     https://cotlet.dev/integrations/officient-api-mcp-server.md

How access works:
1. The user signs up at https://cotlet.dev/app/signup?app=officient, requests Officient in the Cotlet console and creates an API key there.
2. The user signs in to Officient once in their Cotlet Cloud Browser (their own Chrome in the cloud, opened from the console) and enables Officient for agents. An agent cannot do this step.
3. The API key goes into the MCP client or the REST call as a bearer token.

Fits: people who want a hosted Officient server that someone else maintains, including non-developers. Developers who prefer to run and fix code on their own computer can use an open-source Officient MCP server instead.

Policy: Cotlet never stores passwords, never solves CAPTCHAs, never bypasses MFA.
Company: legal details in the Terms of service at https://cotlet.dev/terms. Contact contact@cotlet.dev.
Sign-in: the user signs in to Officient in their own Cloud Browser, a Chrome Cotlet runs for them in the EU; password saving is off, the profile is AES-256-GCM encrypted, and agents get Officient only after the user enables it. Calls are requests from that browser's IP with its cookies, each listed in the user's Background activity. Disable for agents, signing out in the browser or Reset browser cuts access. Cotlet is run by Take Group sp. z o.o. (EU VAT PL6342984273).
API key: holds no Officient login or cookies, only asks Cotlet to run a tool. Each key is scoped to chosen apps and tools, read only or read and write. Actions that reach other people wait for the user's approval by default, so a leaked key cannot post or message as the user. Every call is in the activity log; deleting the key ends access at once.
Terms: the user stays responsible for following Officient's terms; Cotlet is not affiliated with Officient.
```

## What can an AI agent do in Officient?

Cotlet is best for Officient employees and team managers who want their AI agent to book time off, approve absences and show who is out without running or fixing a server.

- **[Request time off from chat](https://cotlet.dev/integrations/officient-api-mcp-server/request-time-off.md)**: "Book 9 to 13 November as holiday. Check my holiday budget first and tell me who else on my team is out that week." → `get_calendar_budget`, `list_colleague_absences`, `request_absence`, `get_calendar`
- **[Approve absence requests](https://cotlet.dev/integrations/officient-api-mcp-server/approve-absence-requests.md)** (runs: daily): "Go through the absence requests waiting for me. Approve holiday requests where nobody else on the team is out on those days, and list the rest with a reason." → `list_absence_requests`, `list_colleague_absences`, `approve_absence_request`
- **[See who is out next week](https://cotlet.dev/integrations/officient-api-mcp-server/who-is-out-next-week.md)** (runs: weekly): "Every Friday, list who on my team is out next week, day by day, and flag days when more than two people are away." → `list_colleagues`, `list_colleague_absences`
- **Log overtime in the calendar**: "I worked from 17:00 to 19:00 yesterday. Add it as overtime in my Officient calendar." → `get_calendar`, `add_overtime`
- **Update your address and emergency contact**: "I moved. Show my current details in Officient and change my address to the one in this message." → `get_personal_information`, `update_personal_information`

## Can Officient automations run on a schedule in n8n, Make or Zapier?

Yes. Cotlet does not replace your automation platform: it gives it a Officient connection it does not have, with the same API key as your agent. Write actions ask for your OK by default; switch that off in your dashboard for the tools you choose, for example to approve absence requests, and the schedule runs on its own. Cotlet runs in the cloud, so it keeps going while your computer is off.

| Where | How to connect | How to schedule |
|---|---|---|
| Your AI agent | Add https://cotlet.dev/mcp/v1 with your API key. | A scheduled agent run, for example a Claude Code routine. |
| n8n | MCP Client node with https://cotlet.dev/mcp/v1, or an HTTP Request node with the endpoint's method and URL, such as GET https://cotlet.dev/api/v1/officient/absence-requests. | Schedule Trigger node. |
| Make | HTTP module: the endpoint's method and URL with an Authorization: Bearer header, and a JSON body for POST, PUT and PATCH. | Scenario schedule. |
| Zapier | Webhooks by Zapier, Custom Request: the same method, URL, header and body. | Schedule by Zapier trigger. |
| Your own script | GET https://cotlet.dev/api/v1/officient/absence-requests with your API key. | cron or GitHub Actions. |

## Tools

**For AI agents:** Every endpoint and its schema is public. The 12 endpoints on this page, with parameters and example responses, can be listed without an account. Calling one returns 401 without an API key and 403 while the key has no access to Officient.

### list_colleagues

Search the Who is who list by name or team. Access: read. REST: `GET /api/v1/officient/colleagues`. MCP: `officient_read → list_colleagues`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `query` | string | no | Part of a name. |
| `team` | string | no | Team name as shown in Who is who. |

Returns the people Who is who shows, with team, role and contact details. Without a filter it returns the whole company. Use person_id values from here in other calls.

Example response:

```json
{
  "colleagues": [
    {
      "person_id": "10045868",
      "name": "Lena Maes",
      "team": "Design",
      "role": "Product designer",
      "email": "lena.maes@example.com",
      "phone": "+32 470 00 00 01"
    },
    {
      "person_id": "10045871",
      "name": "Tom De Smet",
      "team": "Design",
      "role": "Illustrator",
      "email": "tom.desmet@example.com",
      "phone": "+32 470 00 00 02"
    }
  ]
}
```

### get_calendar

Read your own calendar entries for a period. Access: read. REST: `GET /api/v1/officient/calendar`. MCP: `officient_read → get_calendar`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `from_date` | string | yes | First day, ISO date (2026-11-09). |
| `to_date` | string | yes | Last day, ISO date (2026-11-13). |

Returns your absences, overtime and home office entries with the day, the type and whether it covers a full day, a half day or hours. Sorted by date. Use it to check what a request or an overtime entry did.

Example response:

```json
{
  "entries": [
    {
      "date": "2026-11-09",
      "type": "Holiday",
      "day_part": "full_day"
    },
    {
      "date": "2026-11-10",
      "type": "Holiday",
      "day_part": "full_day"
    }
  ],
  "total": 2
}
```

### get_calendar_budget

Read what is left of your absence budget, per type. Access: read. REST: `GET /api/v1/officient/calendar-budget`. MCP: `officient_read → get_calendar_budget`.

No parameters.

Returns the figures shown under My calendar budget in the Calendar, one line per absence type your company uses. Call it before request_absence to see whether the type has enough left.

Example response:

```json
{
  "budgets": [
    {
      "type": "Holiday",
      "remaining": 14.5
    },
    {
      "type": "Overtime",
      "remaining": 6
    }
  ]
}
```

### list_colleague_absences

Read who is out in a period, as Show colleagues displays it. Access: read. REST: `GET /api/v1/officient/colleague-absences`. MCP: `officient_read → list_colleague_absences`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `from_date` | string | yes | First day, ISO date (2026-11-09). |
| `to_date` | string | yes | Last day, ISO date (2026-11-13). |
| `team` | string | no | Only people of this team. |

Returns the colleagues' calendar entries between the two dates: person, type, dates and day part. Home office entries come back too, with their own type. Sorted by first day.

Example response:

```json
{
  "absences": [
    {
      "person": "Lena Maes",
      "type": "Holiday",
      "from_date": "2026-11-09",
      "to_date": "2026-11-13",
      "day_part": "full_day"
    },
    {
      "person": "Tom De Smet",
      "type": "Holiday",
      "from_date": "2026-11-11",
      "to_date": "2026-11-11",
      "day_part": "half_day"
    },
    {
      "person": "Aya Claes",
      "type": "Home office",
      "from_date": "2026-11-11",
      "to_date": "2026-11-11",
      "day_part": "full_day"
    }
  ],
  "total": 3
}
```

### get_personal_information

Read your own record from Personal information. Access: read. REST: `GET /api/v1/officient/personal-information`. MCP: `officient_read → get_personal_information`.

No parameters.

Returns the contact details, address and emergency contact that your employer holds for you. It is your own record only; other people's data is not reachable.

Example response:

```json
{
  "name": "Sofie Peeters",
  "email": "sofie@example.com",
  "phone": "+32 470 00 00 03",
  "address": {
    "line_1": "Meir 12",
    "zipcode": "2000",
    "city": "Antwerp"
  },
  "emergency_contact": {
    "name": "Jan Peeters",
    "relation": "Brother",
    "phone": "+32 470 00 00 04"
  }
}
```

### list_documents

List the folders and documents in your Documents section. Access: read. REST: `GET /api/v1/officient/documents`. MCP: `officient_read → list_documents`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `folder` | string | no | Folder name; leave out for the top level. |

Returns the folders and files your employer shared with you, plus the required documents you still have to submit. Contents are not downloaded, only listed.

Example response:

```json
{
  "folders": [
    "Payslips",
    "Identity card"
  ],
  "documents": [
    {
      "name": "House rules",
      "folder": ""
    }
  ],
  "required": [
    "Identity card"
  ]
}
```

### list_contracts

List your contracts, agreements and regulations, signed or waiting. Access: read. REST: `GET /api/v1/officient/contracts`. MCP: `officient_read → list_contracts`.

No parameters.

Returns each document in Contracts with its title and whether it is signed. Signing stays with you in the Self Service; this tool never signs.

Example response:

```json
{
  "contracts": [
    {
      "title": "Employment agreement",
      "signed": true
    },
    {
      "title": "Work regulations",
      "signed": false
    }
  ],
  "waiting_for_signature": 1
}
```

### list_absence_requests

List absence requests waiting for your approval as a manager. Access: read. REST: `GET /api/v1/officient/absence-requests`. MCP: `officient_read → list_absence_requests`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `cursor` | string | no | Next page cursor from the previous call. |

Returns the requests waiting for you with the person, type, dates and day part. Only a manager or HR account sees requests; any other account gets an empty list. Oldest first.

Example response:

```json
{
  "requests": [
    {
      "request_id": "req_2207",
      "person": "Kathleen Janssens",
      "type": "Holiday",
      "from_date": "2026-11-16",
      "to_date": "2026-11-17",
      "day_part": "full_day"
    },
    {
      "request_id": "req_2208",
      "person": "Pieter Wouters",
      "type": "Holiday",
      "from_date": "2026-11-09",
      "to_date": "2026-11-13",
      "day_part": "full_day"
    }
  ],
  "total": 2
}
```

### request_absence

Send an absence request to your manager or HR. Access: write, asks the user first. REST: `POST /api/v1/officient/absence/request`. MCP: `officient_write → request_absence`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `type` | string | yes | Absence type as your company names it, as listed by get_calendar_budget. |
| `from_date` | string | yes | First day, ISO date (2026-11-09). |
| `to_date` | string | no | Last day; leave out for a single day. |
| `day_part` | string | yes | full_day, half_day or hours. |
| `from_time` | string | no | Start time, HH:MM, only with hours. |
| `until_time` | string | no | End time, HH:MM, only with hours. |

Creates the request the way Add 1 day and Send request do in the Calendar, and returns its id and status. The request reaches your manager or HR. By default you confirm each call; you can switch that off for this tool.

Example response:

```json
{
  "request_id": "req_2210",
  "status": "sent",
  "type": "Holiday",
  "from_date": "2026-11-09",
  "to_date": "2026-11-13",
  "day_part": "full_day"
}
```

### approve_absence_request

Approve a request waiting for you. Access: write, asks the user first. REST: `POST /api/v1/officient/requests/{request_id}/absence-request/approve`. MCP: `officient_write → approve_absence_request`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `request_id` | string | yes | Request id from list_absence_requests. |

Approves one request. Officient enters the absence in the calendar straight away and the employee sees it. Needs a manager or HR account. By default you confirm each call; you can switch that off for this tool.

Example response:

```json
{
  "request_id": "req_2207",
  "status": "approved",
  "person": "Kathleen Janssens",
  "type": "Holiday",
  "from_date": "2026-11-16",
  "to_date": "2026-11-17",
  "in_calendar": true
}
```

### add_overtime

Add overtime hours to your calendar. Access: write, asks the user first. REST: `POST /api/v1/officient/overtimes`. MCP: `officient_write → add_overtime`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `date` | string | yes | Day of the overtime, ISO date. |
| `from_time` | string | yes | Start of the overtime, HH:MM. |
| `until_time` | string | yes | End of the overtime, HH:MM. |

Adds one overtime entry for the day, like Add 1 day with the overtime type in the Calendar. Officient allows overtime once per day, so add the total as one entry. By default you confirm each call; you can switch that off for this tool.

Example response:

```json
{
  "date": "2026-10-21",
  "type": "Overtime",
  "from_time": "17:00",
  "until_time": "19:00",
  "status": "added"
}
```

### update_personal_information

Change your address, phone or emergency contact. Access: write, asks the user first. REST: `PATCH /api/v1/officient/personal-information`. MCP: `officient_write → update_personal_information`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `address_line_1` | string | no | Street and number. |
| `zipcode` | string | no | Postal code. |
| `city` | string | no | City. |
| `phone` | string | no | Phone number. |
| `emergency_contact_name` | string | no | Name of the person to inform. |
| `emergency_contact_phone` | string | no | Phone of the person to inform. |

Changes only the fields you send, the way the pencil in Personal information does. Your employer uses this data to process payroll, so the change reaches HR. By default you confirm each call; you can switch that off for this tool.

Example response:

```json
{
  "updated": [
    "address_line_1",
    "zipcode",
    "city"
  ],
  "address": {
    "line_1": "Korte Nieuwstraat 5",
    "zipcode": "2000",
    "city": "Antwerp"
  }
}
```

## How do I connect Officient to Claude Code, Codex or Cursor?

Connecting Officient takes three steps: sign up, sign in to Officient once in your Cloud Browser and enable it for agents, then add one MCP server or call the REST API with the same key.

### Connect Officient to your agent.

1. **Create an account** Sign up and add Officient in the console. Your API key is there too.

2. **Sign in to Officient in your Cloud Browser** Open your Cloud Browser in the console: your own Chrome in the cloud. Sign in to Officient there yourself, the way you always do, then press Enable for agents, read only or read and write. We never save your password, and your agent keeps working even when your computer is off.

3. **Add Cotlet to your agent** Paste the snippet for your client. The same server and key serve every app you connect, so you do this once.

   Claude Code:

```
claude mcp add --transport http cotlet \
  https://cotlet.dev/mcp/v1 \
  --header "Authorization: Bearer $COTLET_API_KEY"
```

   Cursor:

```
{
  "mcpServers": {
    "cotlet": {
      "url": "https://cotlet.dev/mcp/v1",
      "headers": {
        "Authorization": "Bearer ${COTLET_API_KEY}"
      }
    }
  }
}
```

   Codex:

```
# ~/.codex/config.toml
[mcp_servers.cotlet]
url = "https://cotlet.dev/mcp/v1"
bearer_token_env_var = "COTLET_API_KEY"
```

4. **Ask your agent** Ask in plain words. Your agent finds the Officient tools on the server and calls them for you; anything that reaches other people waits for your OK unless you switch that off for a tool.

```
Book 9 to 13 November as holiday. Check my holiday budget first and tell me who else on my team is out that week.
```

### Call Officient from your scripts.

1. **Export your API key** Your scripts use the same API key as your agent. Keep it in an environment variable, never in your code.

```
export COTLET_API_KEY="cotlet_..."
```

2. **Call a tool** Every tool is an endpoint under /api/v1/officient with its own method and path, listed with the endpoints above. Path parameters go in the URL; the other parameters go in the query for GET and DELETE and in a JSON body otherwise.

```
curl -X POST https://cotlet.dev/api/v1/officient/absence/request \
  -H "Authorization: Bearer $COTLET_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"type":"Holiday","from_date":"2026-11-09","to_date":"2026-11-13","day_part":"full_day"}'
```

3. **Read the result** You get plain JSON back, ready for your script. A failed call costs nothing.

```
{
  "request_id": "req_2210",
  "status": "sent",
  "type": "Holiday",
  "from_date": "2026-11-09",
  "to_date": "2026-11-13",
  "day_part": "full_day"
}
```

## Why use Cotlet for Officient?

**Built for agents**

- One MCP server for every app you connect.
- The same tools as a REST API for scripts and cron jobs.
- Works with Claude Code, Codex and Cursor.

**Your login stays yours**

- You sign in to Officient yourself, in your own Cloud Browser. We never save your password; the profile is encrypted with AES-256-GCM, the cipher 1Password uses.
- A+ on Qualys SSL Labs, securityheaders.com and Mozilla Observatory.
- The model never sees a login.
- No stored passwords, no CAPTCHA solving, no MFA bypass.

**You stay in control**

- Scope each API key: its apps, its tools, read only or read and write.
- Anything that reaches other people waits for your OK, so a leaked key cannot post or message as you.
- Every background request listed in your Background activity. Disable for agents in one click.

**Kept working for you**

- We test every integration every 6 hours.
- When Officient changes, the tool pauses until we fix it.
- Failed calls cost nothing.

## Is it safe to connect Officient to Cotlet?

Yes. You sign in to Officient yourself, in your own Cloud Browser, and we never save your password. Your agents only get Officient once you enable it, and every background request is listed. The browser profile is stored encrypted with AES-256-GCM, the same cipher 1Password uses for its vaults and Apple for iCloud Keychain. Independent public scanners grade cotlet.dev A+ and find it clean; click a result to rerun it yourself.

- **A+ on Qualys SSL Labs**: Encryption in transit: TLS setup and certificates, on all four server addresses. [Live result](https://www.ssllabs.com/ssltest/analyze.html?d=cotlet.dev)
- **A+ on securityheaders.com**: Browser protections sent with every page, all six headers present. [Live result](https://securityheaders.com/?q=cotlet.dev&followRedirects=on)
- **A+ on Mozilla Observatory**: Mozilla's web security baseline: score 120 of 100, 12 of 12 tests passed. [Live result](https://developer.mozilla.org/en-US/observatory/analyze?host=cotlet.dev)
- **Clean on Sucuri SiteCheck**: No malware, spam or defacement, and not on any of 9 blocklists, Google Safe Browsing included. [Live result](https://sitecheck.sucuri.net/results/cotlet.dev)

[How Cotlet protects your access](https://cotlet.dev/security.md)

### Common concerns

**Who runs Cotlet?**

Cotlet is run by Take Group, a Polish software company working since 2019. Take Group runs about 3,200 websites on its own systems and has its own DevOps team for infrastructure security. We built and used integrations like this inside the company for years before opening them as Cotlet.

**Is this an official Officient integration?**

No, Cotlet is independent of Officient. Officient's own API is too limited for this work. Cotlet works through your own Officient account, the way you use Officient in the browser, so you need no partner approval and no developer setup.

**What about client data and GDPR?**

Cotlet is run from the EU and follows the GDPR. Cloud Browsers run in Finland, a Tier 1 country in the ITU Global Cybersecurity Index 2024. Data passes through a call and is not kept after it.

**Can I start with read only?**

Yes. Enable the app for agents as read only, or make the API key read only, and anything that reaches other people waits for your OK unless you switch that off per tool.

**Is it reliable?**

Every Cotlet service is checked every 3 minutes from Europe, North America, Asia and Australia. The live results and any outage are public at status.cotlet.dev.

**How do I stop?**

Press Disable for agents next to Officient in your console: your agents lose access at once and you stay signed in. Signing out of Officient in the browser works too, and Reset browser deletes the whole profile.

## Is there a Officient MCP server on GitHub?

Yes. Community Officient MCP servers exist on GitHub, usually maintained by one person. They call the official API, so an admin first creates an app and a token in Officient, and you install and fix the server yourself. Cotlet hosts the same kind of server for you, works in your own login and keeps it working.

|  | GitHub MCP server | Cotlet |
|---|---|---|
| Setup | Clone the repo, ask an admin for an app and token under developers, add it to each MCP client | Sign up, sign in to Officient once, add one MCP server or API key |
| When Officient changes | It breaks until you or the maintainer fix it | Our team tests it daily and fixes it for you; failed calls are free |
| Your Officient session | A token in a file on your computer, tied to what the app's scopes allow | In your own Cloud Browser in the EU, profile encrypted, only for the apps you enable, disabled for agents in one click |
| When the session expires | Temporary tokens stop working; someone makes a new one | If Officient logs you out, your agent gets a link to sign in again |
| Upkeep | You update, monitor and debug it yourself | Nothing to host or update |
| Where it runs | Your computer, while it is on | Hosted: Claude Code, Codex, Cursor, n8n and scripts, also on a schedule |
| Price | Free, paid for with your time | Free 7-day trial, then pay-as-you-go credit packs, no subscription |

### Which one fits you

**Pick Cotlet if**

- you are not a developer, or you do not want to maintain a server
- you need it to keep working when Officient changes, without checking it yourself
- your agent or a script should run it on a schedule, also while your computer is off

**Pick an open-source server if**

- you are comfortable installing, updating and fixing it yourself
- you want your sign-in to stay on your own computer
- you only need it now and then, from one MCP client

## How much does the Officient API cost?

Free 7-day trial with 2,000 credits, no card needed. After that, the Officient API is pay as you go with no limit on apps: Credit packs from $29 for 5,000 credits, one-time, no subscription. A successful call uses 20 to 30 credits (25 for most tools, about $0.10 to $0.15), your Cloud Browser uses 50 credits a day while it has an app enabled for agents, however many apps that is, and an agent driving the browser itself uses 5 credits a minute. Credit packs stay valid for 12 months and stack, so unused credits carry over.

| Credits | Price, one time | Calls at 25 credits | Per 1,000 credits |
|---|---|---|---|
| 5,000 | $29 | 200 | $5.80 |
| 15,000 | $79 | 600 | $5.27 |
| 32,000 | $149 | 1,280 | $4.66 |
| 60,000 | $249 | 2,400 | $4.15 |

Only successful calls use credits; failed calls and timeouts cost nothing. At a balance of 0 calls pause, never a surprise charge. Authenticate with the `Authorization: Bearer` header. [See full pricing](https://cotlet.dev/pricing.md)

## How Cotlet holds your access

Cotlet hosts MCP servers and REST APIs for apps with no usable API. Your agent works in your own Officient account.

- **Company details:** Cotlet is run by Take Group sp. z o.o., a company registered in Poland. Its full address and registration numbers are in the Terms of service. [Terms of service](https://cotlet.dev/terms)
- **Your sign-in:** You sign in to Officient yourself, in your own Cloud Browser: a Chrome we run for you in the EU, one per app. We never save your password (password saving is off), the profile is stored encrypted with AES-256-GCM, and your agents get Officient only after you enable it. When Officient signs you out, your agent gives you a link to sign in again. [Security](https://cotlet.dev/security.md)
- **Revoking access:** Press Disable for agents next to Officient, sign out of Officient in your Cloud Browser, or reset the browser. Every background request is listed in your Background activity. Actions that reach other people wait for your OK unless you switch that off per tool.
- **What we never do:** Store passwords, solve CAPTCHAs or bypass MFA.
- **Officient's terms:** You use your own Officient account and stay responsible for following Officient's terms. Cotlet is independent and not affiliated with Officient. [Terms](https://cotlet.dev/terms)
- **Contact:** Questions about the company, security or an app: [contact@cotlet.dev](mailto:contact@cotlet.dev)

## Frequently asked questions

**How do I get access?**

Sign up free, open Officient in the console and press Request access. Then you create your API key and connect Officient there.

**Do I need to be technical?**

No. You sign in to Officient once in your Cloud Browser, a normal Chrome you open from the console, and paste one command into your agent, or one URL into n8n. Your agent can walk you through it. There is no server to install, update or fix.

**Is it safe to connect Officient to Cotlet?**

Yes. You sign in to Officient yourself, in your own Cloud Browser in the EU, and we never save your password. Your agents only get Officient once you enable it, every background request is listed, and the browser profile is stored encrypted with AES-256-GCM, the cipher 1Password uses for its vaults. The AI model never sees a login, posts and messages wait for your OK, and Disable for agents cuts access in one click. Independent scanners grade cotlet.dev A+ on Qualys SSL Labs, securityheaders.com and Mozilla Observatory; live results are on https://cotlet.dev/security.

**Is a hosted server safer than a local one? My Officient sign-in would leave my computer.**

On Cotlet you sign in inside your own Cloud Browser, which only you open, and its profile is stored encrypted with AES-256-GCM in the EU. Agents get only the apps you enable, and every background request is listed. A local server keeps your Officient cookie in a plain file on your computer, readable by any program you run, and stops when your computer is off.

**Why does Cotlet send requests instead of clicking in my browser?**

To be fast, Cotlet doesn't click through Officient's pages. It sends the same requests your browser would, from your browser's IP with its cookies, without opening a window. Officient sees the same browser and IP you signed in with, and every request is listed in your Background activity.

**What if someone gets my Cotlet API key?**

The key holds no Officient login or cookies, it only asks Cotlet to run a tool. It can call only the apps and tools you gave it, and a read-only key changes nothing. Anything that reaches other people, like posts, comments or messages, waits for your OK in the dashboard by default, so a leaked key cannot post or message as you. When you switch approval off for a scheduled job, give that job its own key limited to that one tool. Every call is in your activity log, and deleting the key ends access at once.

**Why a signed-in browser and not OAuth, like other integration platforms?**

Officient offers no OAuth token you can simply grant for these tools: its official API leaves them out or needs a developer app, a plan or an approval first (see the official API section above). That is why Cotlet sets the limits itself: per key, per tool, with your approval before anything reaches other people. Cotlet is run by Take Group sp. z o.o., an EU company (VAT PL6342984273).

**Do I need to be an Officient admin?**

No. Your agent works in your own Self Service login, so it sees what you see. Approvals need a manager or HR role. Officient sign-in works by e-mail link, Google or Office 365, and Cotlet never bypasses a step you set up; you sign in once yourself.

**Should I use the official API instead?**

If you are an admin and need person details, yes: create an app under developers and call person detail. Officient limits the API to 30 calls per 5 seconds, and an app reaches other companies only after Officient verifies it. Cotlet covers the Self Service jobs the public reference does not list.

**What does it not cover?**

Contracts are listed, never signed. Wage and benefits, assets, performance reviews, tasks, courses and the admin settings of the HR platform are out of scope today. Some features are switched off per company, and a tool then returns an empty result.

**Can my agent post or send messages in Officient without asking me?**

No. Every call to request_absence, approve_absence_request, add_overtime or update_personal_information waits for your OK by default. For scheduled automations you can switch confirmation off per tool in your dashboard, for example only for approvals.

**Can I use the Officient API in n8n?**

Yes. Add https://cotlet.dev/mcp/v1 with your API key in n8n's MCP Client node, or call its endpoints under https://cotlet.dev/api/v1/officient from the HTTP Request node.

---

Give your AI agents your signed-in browser.

**Product:** [Integrations](https://cotlet.dev/integrations.md) · [Use cases](https://cotlet.dev/use-cases.md) · [How it works](https://cotlet.dev/how-it-works.md) · [Pricing](https://cotlet.dev/pricing.md) · [Security](https://cotlet.dev/security.md)

**Resources:** [Blog](https://cotlet.dev/blog.md) · [API docs](https://cotlet.dev/docs.md) · [Help center](https://cotlet.dev/help.md) · [Changelog](https://cotlet.dev/changelog.md) · [GitHub](https://github.com/cotletdev/cotlet)

**Solutions:** [For developers](https://cotlet.dev/for-developers.md) · [For automation agencies](https://cotlet.dev/for-agencies.md)

**Company:** [About](https://cotlet.dev/about.md) · [AI info: company facts](https://cotlet.dev/ai-info.md) · [Contact](https://cotlet.dev/contact.md)

**Legal:** [Terms of service](https://cotlet.dev/terms) · [Privacy policy](https://cotlet.dev/privacy) · [Refund policy](https://cotlet.dev/refunds) · [Acceptable use](https://cotlet.dev/acceptable-use) · [Cookie policy](https://cotlet.dev/cookies) · [DPA](https://cotlet.dev/dpa) · [Subprocessors](https://cotlet.dev/subprocessors)

**Elsewhere:** [Status page](https://status.cotlet.dev) · [Cotlet on GitHub](https://github.com/cotletdev) · [Cotlet on X](https://x.com/cotletdev) · [Cotlet on LinkedIn](https://www.linkedin.com/company/cotletdev) · [Cotlet on Product Hunt](https://www.producthunt.com/products/cotlet) · [Cotlet on Crunchbase](https://www.crunchbase.com/organization/cotlet) · [Cotlet on SaaSHub](https://www.saashub.com/cotlet)

Cotlet is an independent service. It is not affiliated with, endorsed by or sponsored by any of the products listed on this site. Product names are trademarks of their respective owners.

## For AI agents: sign your user up

Is your user asking you to sign them up for Cotlet? You can do it for them, no account or key needed.

1. Read the fields and their allowed values: GET https://cotlet.dev/api/v1/access-requests
2. Ask the user for each value: email, apps, what you will do with them. If they leave the password to you, generate a strong one and show it to them.
3. Show the user what you will send, then POST it as JSON to https://cotlet.dev/api/v1/access-requests.

One call creates the account and sends the access request; we email the user when access is granted.