[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)

# Resource Guru API and MCP server

> Resource Guru has a public REST API with OAuth 2 that reads and writes bookings, projects, clients, resources and time off, and an official MCP server that only reads (checked 23 Oct 2026). The MCP server shows schedules, availability, utilization, project budgets and time off, and cannot change any of it. To act on the account, you register an app in the Developer Center and build the agent tools yourself.

Scheduling software for teams: bookings for people, placeholders and equipment on one Schedule, with projects, clients, time off, approvals and reports.

## What is the Resource Guru API?

Cotlet's Resource Guru API exposes 13 endpoints for your own Resource Guru account: list resources, list projects, list clients, list bookings, list time off, create booking, create Total Hours booking, update booking, delete booking, approve or decline booking, add time off, create client and create project. The list_resources endpoint returns people, placeholders and other resources in the account. Each endpoint takes simple JSON inputs like start_date, end_date or resource_ids and works both as an operation of the resource_guru_read or resource_guru_write MCP tool for agents and as a REST call for scripts.

- **Category:** [Productivity & teams](https://cotlet.dev/integrations/category/productivity-teams.md)
- **Endpoints:** 13 (5 read, 8 write)
- **Updated:** 2026-10-23

Resource Guru has a public REST API with OAuth 2 that reads and writes bookings, projects, clients, resources and time off, and an official MCP server that only reads (checked 23 Oct 2026). Cotlet is a hosted MCP server and REST API for Resource Guru with 13 endpoints (5 read, 8 write): you sign in once in your own cloud browser, your AI agent does the work.

## Does Resource Guru have an official API?

Resource Guru has a public REST API with OAuth 2 that reads and writes bookings, projects, clients, resources and time off, and an official MCP server that only reads (checked 23 Oct 2026). The MCP server shows schedules, availability, utilization, project budgets and time off, and cannot change any of it. To act on the account, you register an app in the Developer Center and build the agent tools yourself.

| Task | Resource Guru official | Cotlet |
|---|---|---|
| List bookings, resources, projects and clients | Yes: Official MCP server and the public API | Yes |
| Read time off, availability and utilization | Yes: Official MCP server and the public API | Yes |
| Create a booking, including Total Hours bookings | Partly: Public API only, with an OAuth app you build; the official MCP server is read-only | Yes |
| Confirm, move or delete a booking | Partly: Public API only; the official MCP server is read-only | Yes |
| Approve or decline a booking request | Partly: Public API only; the Approval Workflow is part of the Master plan | Yes |
| Add time off | Partly: Public API only; the official MCP server is read-only | Yes |
| Create projects and clients | Partly: Public API only; the official MCP server is read-only | Yes |

Sources: [Resource Guru: MCP server](https://resourceguruapp.com/features/mcp-server), [Resource Guru blog: Introducing our MCP server](https://resourceguruapp.com/blog/product-updates/mcp-server), [Resource Guru API documentation](https://resourceguruapp.com/docs/api), [Resource Guru Developer Center](https://developers.resourceguruapp.com/)

## Quick reference

```text
Resource Guru has a public REST API with OAuth 2 that reads and writes bookings, projects, clients, resources and time off, and an official MCP server that only reads (checked 23 Oct 2026). The MCP server shows schedules, availability, utilization, project budgets and time off, and cannot change any of it. To act on the account, you register an app in the Developer Center and build the agent tools yourself.
Cotlet provides a hosted MCP server and REST API for Resource Guru: 13 tools (5 read, 8 write).
Access       Sign up at https://cotlet.dev/app/signup?app=resource-guru, then request the app and create API keys in the Cotlet console.

MCP server   https://cotlet.dev/mcp/v1
MCP tools    resource_guru_read, resource_guru_write, reads and writes apart; call one with {"operation": "<operation>", "arguments": {...}}
REST base    https://cotlet.dev/api/v1/resource-guru, each operation at its own route, e.g. POST /api/v1/resource-guru/bookings
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_resources, list_projects, list_clients, list_bookings, list_time_off, create_booking, create_total_hours_booking, update_booking, delete_booking, resolve_booking, add_time_off, create_client, create_project
Confirm      create_booking, create_total_hours_booking, update_booking, delete_booking, resolve_booking, add_time_off (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/resource-guru-api-mcp-server.md

How access works:
1. The user signs up at https://cotlet.dev/app/signup?app=resource-guru, requests Resource Guru in the Cotlet console and creates an API key there.
2. The user signs in to Resource Guru once in their Cotlet Cloud Browser (their own Chrome in the cloud, opened from the console) and enables Resource Guru 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 Resource Guru 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 Resource Guru 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 Resource Guru 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 Resource Guru 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 Resource Guru 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 Resource Guru's terms; Cotlet is not affiliated with Resource Guru.
```

## What can an AI agent do in Resource Guru?

Cotlet is best for resource managers and project leads who want their AI agent to book people, confirm tentative bookings and approve requests without running or fixing a server.

- **[Book people onto a project from a request](https://cotlet.dev/integrations/resource-guru-api-mcp-server/book-people-onto-a-project.md)**: "Book Lena Ortiz and Sam Okafor on Website Redesign for Acme from 2 to 6 November, 4 hours a day. Check their bookings first and tell me who is already full." → `list_resources`, `list_projects`, `list_bookings`, `create_booking`
- **[Confirm or clear tentative bookings](https://cotlet.dev/integrations/resource-guru-api-mcp-server/confirm-tentative-bookings.md)** (runs: weekly): "List everyone with tentative bookings next week. Confirm the ones for projects marked won in this list, delete the ones for lost projects and leave the rest for me." → `list_bookings`, `update_booking`, `delete_booking`
- **[Approve or decline booking requests](https://cotlet.dev/integrations/resource-guru-api-mcp-server/approve-booking-requests.md)** (runs: daily): "List bookings waiting for my approval. Approve the ones inside the person's normal hours and decline any over 8 hours a day with the reason "Over daily limit"." → `list_bookings`, `resolve_booking`
- **Clear the waiting list** (runs: weekly): "Find bookings on the waiting list for the next month, move each to the first free day for that person if one exists, and list the rest." → `list_bookings`, `list_resources`, `update_booking`
- **Add time off for the team**: "Add the public holidays from this list for everyone in the London office, and put Dana on vacation from 16 to 20 December." → `list_resources`, `list_time_off`, `add_time_off`
- **Set up a project and client from a signed deal**: "Create the client Acme Ltd and the project Website Redesign for it, with the code ACM-04, then book the kickoff day for the whole delivery team." → `create_client`, `create_project`, `list_resources`, `create_booking`

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

Yes. Cotlet does not replace your automation platform: it gives it a Resource Guru 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 confirm or clear tentative bookings, 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/resource-guru/bookings. | 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/resource-guru/bookings with your API key. | cron or GitHub Actions. |

## Tools

**For AI agents:** Every endpoint and its schema is public. The 13 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 Resource Guru.

### list_resources

People, placeholders and other resources in the account. Access: read. REST: `GET /api/v1/resource-guru/resources`. MCP: `resource_guru_read → list_resources`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `search` | string | no | Part of a name to match. |
| `archived` | boolean | no | True to list archived resources instead of active ones. |

Returns each resource with its ID, name, type, timezone and job title. The IDs feed every booking and time off call. The list shows active resources unless archived is true. Resource Guru returns up to 50 per call by default.

Example response:

```json
{
  "resources": [
    {
      "id": 18211,
      "name": "Lena Ortiz",
      "type": "Person",
      "job_title": "Designer",
      "timezone": "London"
    },
    {
      "id": 18214,
      "name": "Sam Okafor",
      "type": "Person",
      "job_title": "Developer",
      "timezone": "London"
    }
  ]
}
```

### list_projects

Projects with their client, code and dates. Access: read. REST: `GET /api/v1/resource-guru/projects`. MCP: `resource_guru_read → list_projects`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `search` | string | no | Part of a project name or code. |
| `archived` | boolean | no | True to list archived projects instead of active ones. |

Returns each project with its ID, name, project code, client and start and end dates. Active projects come first unless archived is true. Use the ID in create_booking and update_booking.

Example response:

```json
{
  "projects": [
    {
      "id": 703110,
      "name": "Website Redesign",
      "project_code": "ACM-04",
      "client_id": 55120,
      "start_date": "2026-11-02",
      "end_date": "2026-12-18"
    }
  ]
}
```

### list_clients

Clients with their IDs and notes. Access: read. REST: `GET /api/v1/resource-guru/clients`. MCP: `resource_guru_read → list_clients`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `archived` | boolean | no | True to list archived clients instead of active ones. |

Returns each client with its ID, name and notes. Use the ID in create_project and create_booking.

Example response:

```json
{
  "clients": [
    {
      "id": 55120,
      "name": "Acme Ltd",
      "notes": "Retainer client"
    }
  ]
}
```

### list_bookings

Bookings in a date range, filtered by person, approval state or waiting list. Access: read. REST: `GET /api/v1/resource-guru/bookings`. MCP: `resource_guru_read → list_bookings`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `start_date` | string | no | Only bookings starting on or after this date, YYYY-MM-DD. |
| `end_date` | string | no | Only bookings ending on or before this date, YYYY-MM-DD. |
| `resource_ids` | integer[] | no | Only bookings for these resources. |
| `approval_state` | string | no | pending, approved or declined. |
| `waiting` | boolean | no | True to list only bookings on the waiting list. |

Returns each booking with its ID, people, dates, minutes per day, project, tentative flag and approval state. Tentative bookings come back with tentative set to true, so your agent filters them from the list. Always pass start_date and end_date.

Example response:

```json
{
  "bookings": [
    {
      "id": 48213021,
      "resource_ids": [
        18211,
        18214
      ],
      "start_date": "2026-11-02",
      "end_date": "2026-11-06",
      "minutes_per_day": 240,
      "project_id": 703110,
      "tentative": true,
      "approval_state": "approved",
      "waiting": false
    }
  ]
}
```

### list_time_off

Time off entries and their types. Access: read. REST: `GET /api/v1/resource-guru/time-offs`. MCP: `resource_guru_read → list_time_off`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `start_date` | string | no | Only entries starting on or after this date, YYYY-MM-DD. |
| `end_date` | string | no | Only entries ending on or before this date, YYYY-MM-DD. |
| `resource_ids` | integer[] | no | Only entries for these resources. |

Returns each time off entry with its ID, people, dates and type: Vacation/Holiday (personal), Public holiday, Sick leave, Maternity/paternity leave or Compassionate leave. Run it before add_time_off to avoid duplicates.

Example response:

```json
{
  "time_off": [
    {
      "id": 902115,
      "resource_ids": [
        18211
      ],
      "from": "2026-12-24",
      "to": "2026-12-26",
      "type": "Public holiday",
      "details": "Christmas"
    }
  ]
}
```

### create_booking

Book one or more resources on days, for hours per day or at a set time. Access: write, asks the user first. REST: `POST /api/v1/resource-guru/bookings`. MCP: `resource_guru_write → create_booking`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `resource_ids` | integer[] | yes | IDs of the people, placeholders or other resources to book, from list_resources. |
| `start_date` | string | yes | First day, YYYY-MM-DD. |
| `end_date` | string | yes | Last day, YYYY-MM-DD. |
| `minutes_per_day` | integer | yes | Minutes booked on each day, 1 to 1440. |
| `start_time` | integer | no | For a Specific Time booking: minutes after midnight, so 540 is 9:00. |
| `project_id` | integer | no | Project ID from list_projects. |
| `client_id` | integer | no | Client ID from list_clients. |
| `tentative` | boolean | no | True for a pencilled booking that takes no availability. |
| `details` | string | no | Notes on the booking. Markdown works. |
| `clash_resolution` | string | no | What to do when a resource has no free time: add_to_waiting_list, book_with_overtime or increase_availability. |

Returns the new booking with its ID. If a person has too little free time and clash_resolution is not set, nothing is booked and the clash is returned. The booked people see a confirmed booking on their Dashboard, and an account with the Approval Workflow sends it to approvers as pending. By default you confirm each call; you can switch that off for this tool.

Example response:

```json
{
  "id": 48213021,
  "resource_ids": [
    18211,
    18214
  ],
  "start_date": "2026-11-02",
  "end_date": "2026-11-06",
  "minutes_per_day": 240,
  "project_id": 703110,
  "tentative": false,
  "approval_state": "approved",
  "waiting": false
}
```

### create_total_hours_booking

Book a total number of hours across a date range and let Resource Guru place them. Access: write, asks the user first. REST: `POST /api/v1/resource-guru/resources/{resource_id}/total-hours-bookings`. MCP: `resource_guru_write → create_total_hours_booking`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `resource_id` | integer | yes | One person or placeholder, from list_resources. |
| `start_date` | string | yes | First day of the window, YYYY-MM-DD. |
| `end_date` | string | yes | Last day of the window, YYYY-MM-DD. |
| `total_minutes` | integer | yes | Total effort in minutes across the whole window. |
| `effort_flexibility` | string | yes | How freely hours may be spread: fixed, limited or full. |
| `project_id` | integer | no | Project ID from list_projects. |
| `details` | string | no | Notes on the booking. |

Resource Guru fits the hours into free time inside the window. Hours that do not fit go to the waiting list and the response shows the remainder. A Total Hours booking covers one resource and cannot repeat, so use a placeholder for work you will staff later. By default you confirm each call; you can switch that off for this tool.

Example response:

```json
{
  "id": 48213390,
  "resource_ids": [
    18300
  ],
  "start_date": "2026-11-02",
  "end_date": "2026-12-12",
  "total_minutes": 4800,
  "allocated_minutes": 4800,
  "waiting_minutes": 0,
  "project_id": 703110
}
```

### update_booking

Change dates, hours, people, project or the tentative flag of a booking. Access: write, asks the user first. REST: `PATCH /api/v1/resource-guru/bookings/{booking_id}`. MCP: `resource_guru_write → update_booking`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `booking_id` | integer | yes | Booking ID from list_bookings. |
| `start_date` | string | no | New first day, YYYY-MM-DD. |
| `end_date` | string | no | New last day, YYYY-MM-DD. |
| `minutes_per_day` | integer | no | New minutes per day, 1 to 1440. |
| `resource_ids` | integer[] | no | Replace the booked people or resources. |
| `project_id` | integer | no | Move the booking to another project. |
| `tentative` | boolean | no | False confirms a tentative booking, true makes it tentative. |
| `clash_resolution` | string | no | What to do when a resource has no free time: add_to_waiting_list, book_with_overtime or increase_availability. |

Returns the booking after the change. On a multi-resource booking the change applies to every resource on it. Confirming a tentative booking shows it on the booked people's Dashboard, and with the Approval Workflow on it can come back pending. By default you confirm each call; you can switch that off for this tool.

Example response:

```json
{
  "id": 48213021,
  "resource_ids": [
    18211,
    18214
  ],
  "start_date": "2026-11-02",
  "end_date": "2026-11-06",
  "minutes_per_day": 240,
  "project_id": 703110,
  "tentative": false,
  "approval_state": "approved",
  "waiting": false
}
```

### delete_booking

Remove a booking from the Schedule. Access: write, asks the user first. REST: `DELETE /api/v1/resource-guru/bookings/{booking_id}`. MCP: `resource_guru_write → delete_booking`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `booking_id` | integer | yes | Booking ID from list_bookings. |

Removes the whole booking, for every person on it. The booked people lose it from their Dashboard, and it cannot be undone through Cotlet. By default you confirm each call; you can switch that off for this tool.

Example response:

```json
{
  "booking_id": 48213022,
  "deleted": true
}
```

### resolve_booking

Approve or decline a pending booking for the people you approve. Access: write, asks the user first. REST: `POST /api/v1/resource-guru/bookings/{booking_id}/resolve`. MCP: `resource_guru_write → resolve_booking`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `booking_id` | integer | yes | Booking ID from list_bookings. |
| `resolution` | string | yes | approved or declined. |
| `resource_ids` | integer[] | yes | The booked people this decision applies to, from list_bookings. |
| `reason` | string | no | Why you declined. Resource Guru puts it in the email to the booker. |

Needs the Approval Workflow, which is part of the Master plan, and an account that is an approver for these people. Resource Guru emails the booker after the decision. A declined booking stops taking up availability. By default you confirm each call; you can switch that off for this tool.

Example response:

```json
{
  "booking_id": 48213107,
  "resolution": "declined",
  "resource_ids": [
    18214
  ],
  "reason": "Over daily limit"
}
```

### add_time_off

Add vacation, a public holiday, sick leave or other time off for people. Access: write, asks the user first. REST: `POST /api/v1/resource-guru/time-offs`. MCP: `resource_guru_write → add_time_off`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `resource_ids` | integer[] | yes | IDs of the people, placeholders or other resources to book, from list_resources. |
| `from` | string | yes | First day, YYYY-MM-DD. |
| `to` | string | yes | Last day, YYYY-MM-DD. |
| `type` | string | yes | Vacation/Holiday (personal), Public holiday, Sick leave, Maternity/paternity leave or Compassionate leave. |
| `details` | string | no | Notes on the time off. |
| `block_on_clash` | boolean | no | True to fail instead of moving clashing bookings to the waiting list. |

Returns the entry with its ID. Bookings that clash with the time off move to the waiting list unless block_on_clash is true. Time off counts in reports only where it overlaps working hours. By default you confirm each call; you can switch that off for this tool.

Example response:

```json
{
  "id": 902116,
  "resource_ids": [
    18215
  ],
  "from": "2026-12-16",
  "to": "2026-12-20",
  "type": "Vacation/Holiday (personal)",
  "moved_to_waiting_list": 0
}
```

### create_client

Add a client to Projects & Clients. Access: write. REST: `POST /api/v1/resource-guru/clients`. MCP: `resource_guru_write → create_client`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `name` | string | yes | Client name. |
| `notes` | string | no | Details or links about the client. |
| `color` | string | no | Hex color such as c0ffee. |

Returns the new client with its ID. It reaches no one and you can archive or edit it in Resource Guru, so it does not wait for your OK. Needs Manager permission or higher in Resource Guru.

Example response:

```json
{
  "id": 55121,
  "name": "Northwind Studio",
  "notes": "Signed 23 Oct",
  "archived": false
}
```

### create_project

Add a project, with its client, code and dates. Access: write. REST: `POST /api/v1/resource-guru/projects`. MCP: `resource_guru_write → create_project`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `name` | string | yes | Project name. |
| `project_code` | string | no | Short code shown in reports. |
| `client_id` | integer | no | Client ID from list_clients or create_client. |
| `start_date` | string | no | Project start, YYYY-MM-DD. |
| `end_date` | string | no | Project end, YYYY-MM-DD. |
| `default_billable` | boolean | no | True if bookings for this project default to billable. |
| `notes` | string | no | Notes on the project. |

Returns the new project with its ID, ready for create_booking. It reaches no one and you can archive or edit it in Resource Guru, so it does not wait for your OK. Needs Manager permission or higher in Resource Guru.

Example response:

```json
{
  "id": 703111,
  "name": "Brand Guidelines",
  "project_code": "NWS-01",
  "client_id": 55121,
  "start_date": "2026-11-09",
  "end_date": "2026-12-04",
  "archived": false
}
```

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

Connecting Resource Guru takes three steps: sign up, sign in to Resource Guru 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 Resource Guru to your agent.

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

2. **Sign in to Resource Guru in your Cloud Browser** Open your Cloud Browser in the console: your own Chrome in the cloud. Sign in to Resource Guru 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 Resource Guru 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 Lena Ortiz and Sam Okafor on Website Redesign for Acme from 2 to 6 November, 4 hours a day. Check their bookings first and tell me who is already full.
```

### Call Resource Guru 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/resource-guru 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/resource-guru/bookings \
  -H "Authorization: Bearer $COTLET_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"resource_ids":[18211],"start_date":"2026-11-09","end_date":"2026-11-13","minutes_per_day":360,"project_id":703110,"tentative":true,"details":"Pencilled until Acme signs off"}'
```

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

```
{
  "id": 48213450,
  "resource_ids": [
    18211
  ],
  "start_date": "2026-11-09",
  "end_date": "2026-11-13",
  "minutes_per_day": 360,
  "project_id": 703110,
  "tentative": true,
  "approval_state": "approved",
  "waiting": false
}
```

## Why use Cotlet for Resource Guru?

**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 Resource Guru 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 Resource Guru changes, the tool pauses until we fix it.
- Failed calls cost nothing.

## Is it safe to connect Resource Guru to Cotlet?

Yes. You sign in to Resource Guru yourself, in your own Cloud Browser, and we never save your password. Your agents only get Resource Guru 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 Resource Guru integration?**

No, Cotlet is independent of Resource Guru. Resource Guru's own API is too limited for this work. Cotlet works through your own Resource Guru account, the way you use Resource Guru 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 Resource Guru in your console: your agents lose access at once and you stay signed in. Signing out of Resource Guru in the browser works too, and Reset browser deletes the whole profile.

## Is there a Resource Guru MCP server on GitHub?

Yes. Community MCP servers for Resource Guru exist on GitHub, usually maintained by one person. You install one on your own computer, register your own OAuth app, and keep it running yourself; when the API changes, it stops working until you or the maintainer fix it. Cotlet hosts the same kind of server for you, signs in as you, and our team keeps it working.

|  | GitHub MCP server | Cotlet |
|---|---|---|
| Setup | Clone the repo, register an OAuth app in the Developer Center, add the server to each MCP client | Sign up, sign in to Resource Guru once, add one MCP server or API key |
| When Resource Guru 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 Resource Guru session | An OAuth token in a file on your computer, readable by any program you run | 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 | Tools fail until you refresh or reissue the token by hand | Your Cloud Browser keeps you signed in; if Resource Guru 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 Resource Guru 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 Resource Guru API cost?

Free 7-day trial with 2,000 credits, no card needed. After that, the Resource Guru 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 10 credits (about $0.04 to $0.06), 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 10 credits | Per 1,000 credits |
|---|---|---|---|
| 5,000 | $29 | 500 | $5.80 |
| 15,000 | $79 | 1,500 | $5.27 |
| 32,000 | $149 | 3,200 | $4.66 |
| 60,000 | $249 | 6,000 | $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 Resource Guru 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 Resource Guru 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 Resource Guru only after you enable it. When Resource Guru 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 Resource Guru, sign out of Resource Guru 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.
- **Resource Guru's terms:** You use your own Resource Guru account and stay responsible for following Resource Guru's terms. Cotlet is independent and not affiliated with Resource Guru. [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 Resource Guru in the console and press Request access. Then you create your API key and connect Resource Guru there.

**Do I need to be technical?**

No. You sign in to Resource Guru 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 Resource Guru to Cotlet?**

Yes. You sign in to Resource Guru yourself, in your own Cloud Browser in the EU, and we never save your password. Your agents only get Resource Guru 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 Resource Guru 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 Resource Guru 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 Resource Guru's pages. It sends the same requests your browser would, from your browser's IP with its cookies, without opening a window. Resource Guru 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 Resource Guru 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?**

Resource Guru 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 a certain Resource Guru plan?**

Bookings, Total Hours bookings and the official read-only MCP server are on all plans. The Approval Workflow, which resolve_booking needs, is part of the Master plan. Your own permissions count too: creating projects and clients needs Manager or higher.

**Should I turn off Resource Guru's own MCP server?**

No. The official server is read-only, an Admin enables it under Settings > Integrations > MCP Server, and it answers questions about schedules, availability, utilization and budgets. Cotlet adds the writes it cannot do: bookings, confirmations, approvals and time off.

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

No. Every call to create_booking, create_total_hours_booking, update_booking, delete_booking, resolve_booking or add_time_off waits for your OK by default. For scheduled automations you can switch confirmation off per tool in your dashboard, for example only for approvals. create_client and create_project run without asking, because they send nothing to anyone and one call undoes it.

**Can I use the Resource Guru 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/resource-guru 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.dev is built by Bart Krawczyk and Jake Slugocki, the founders of Take Group sp. z o.o., ul. Wincentego Janasa 4, 40-855 Katowice, Poland. KRS 0000871398, NIP 6342984273, VAT EU: PL6342984273. [About us](https://cotlet.dev/about.md)

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.