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

# TaxDome API and MCP server

> TaxDome has no public API that firms can use today (checked 14 Oct 2026). Its Zapier integration only creates, updates and finds contacts, and TaxDome MCP, which would let Claude or ChatGPT work in a firm account, is announced but not open yet and is offered to Professional and Business plan firms first.

Practice management platform for accounting firms: client accounts, jobs in pipelines, client requests for documents, invoices, secure chats and a client portal in one place.

## What is the TaxDome API?

Cotlet's TaxDome API exposes 14 endpoints for your own TaxDome account: list accounts, get account, list pipelines, list jobs, get job, list tasks, list invoices, list client requests, create account, create job, archive job, create and send invoice, send client request and message client. The list_accounts endpoint returns client accounts, individuals and companies, with their contacts. Each endpoint takes simple JSON inputs like account_id, cursor or assignee and works both as an operation of the taxdome_read or taxdome_write MCP tool for agents and as a REST call for scripts.

- **Category:** [Invoicing & freelance CRM](https://cotlet.dev/integrations/category/invoicing-freelance-crm.md)
- **Endpoints:** 14 (8 read, 6 write)
- **Updated:** 2026-10-19

TaxDome has no public API that firms can use today (checked 14 Oct 2026). Cotlet is a hosted MCP server and REST API for TaxDome with 14 endpoints (8 read, 6 write): you sign in once in your own cloud browser, your AI agent does the work.

## Does TaxDome have an official API?

TaxDome has no public API that firms can use today (checked 14 Oct 2026). Its Zapier integration only creates, updates and finds contacts, and TaxDome MCP, which would let Claude or ChatGPT work in a firm account, is announced but not open yet and is offered to Professional and Business plan firms first.

| Task | TaxDome official | Cotlet |
|---|---|---|
| List and read client accounts | Partly: Zapier can find a contact; there is no account list | Yes |
| Create a client account | Partly: Zapier can create a contact | Yes |
| List and read jobs | No | Yes |
| Create and archive jobs | No | Yes |
| Send a client request for documents | No | Yes |
| Create and send an invoice | No | Yes |
| Message a client in a chat | No | Yes |
| List tasks of a job | No | Yes |

Sources: [TaxDome: MCP](https://go.taxdome.com/mcp-waitlist), [TaxDome Help: Zapier integration](https://help.taxdome.com/article/102-integration-with-zapier), [TaxDome Help: Zapier integration (Basic) actions](https://help.taxdome.com/article/1694-zapier-integration-basic-actions), [TaxDome Help: Creating a bill (invoice)](https://help.taxdome.com/article/24-creating-a-bill)

## For AI agents

```text
TaxDome has no public API that firms can use today (checked 14 Oct 2026). Its Zapier integration only creates, updates and finds contacts, and TaxDome MCP, which would let Claude or ChatGPT work in a firm account, is announced but not open yet and is offered to Professional and Business plan firms first.
Cotlet provides a hosted MCP server and REST API for TaxDome: 14 tools (8 read, 6 write).
Access       Sign up at https://cotlet.dev/app/signup?app=taxdome, then request the app and create API keys in the Cotlet console.

MCP server   https://cotlet.dev/mcp/v1
MCP tools    taxdome_read, taxdome_write, reads and writes apart; call one with {"operation": "<operation>", "arguments": {...}}
REST base    https://cotlet.dev/api/v1/taxdome, each operation at its own route, e.g. POST /api/v1/taxdome/accounts/{account_id}/invoices
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_accounts, get_account, list_pipelines, list_jobs, get_job, list_tasks, list_invoices, list_requests, create_account, create_job, archive_job, send_invoice, request_documents, send_message
Confirm      create_account, send_invoice, request_documents, send_message (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/taxdome-api-mcp-server.md

How access works:
1. The user signs up at https://cotlet.dev/app/signup?app=taxdome, requests TaxDome in the Cotlet console and creates an API key there.
2. The user signs in to TaxDome once in their Cotlet Cloud Browser (their own Chrome in the cloud, opened from the console) and enables TaxDome 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 TaxDome server that someone else maintains, including non-developers.

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 TaxDome 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 TaxDome 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 TaxDome 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 TaxDome's terms; Cotlet is not affiliated with TaxDome.
```

## What can an AI agent do in TaxDome?

Cotlet is best for accounting firms and bookkeepers who repeat the same requests, invoices and jobs for many clients and want an AI agent to do it without running or fixing a server.

- **[Request documents from every client on a checklist](https://cotlet.dev/integrations/taxdome-api-mcp-server/request-client-documents.md)** (runs: weekly): "For each company account in the Tax Prep 2026 pipeline that has no open request, send a client request titled "2026 tax documents" asking for last year's return, bank statements and payroll reports, due Friday." → `list_jobs`, `list_requests`, `request_documents`
- **[Send recurring client invoices from one prompt](https://cotlet.dev/integrations/taxdome-api-mcp-server/send-client-invoices.md)** (runs: weekly): "Create and send the monthly bookkeeping invoice for each company account tagged "monthly": one line "Bookkeeping, October 2026" at the amount in my sheet, due in 14 days." → `list_accounts`, `list_invoices`, `send_invoice`
- **[Create jobs for every client from a template](https://cotlet.dev/integrations/taxdome-api-mcp-server/create-jobs-for-clients.md)** (runs: weekly): "For each company account tagged "annual", create a job in the Annual Filing pipeline at stage "Intake", assigned to Maria Silva, priority Medium, due 15 March, unless the account already has an open one." → `list_accounts`, `list_jobs`, `create_job`
- **Chase overdue jobs and message the client** (runs: weekly): "List overdue jobs in Annual Filing. For each one waiting on the client, send a short chat message asking for what is missing. Show me the rest." → `list_jobs`, `get_job`, `send_message`
- **Add new clients from a signed engagement list**: "Create a company account for each row in this list with the main contact name and email, skip any that already exist, and do not invite them to the portal." → `list_accounts`, `create_account`

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

Yes. Cotlet does not replace your automation platform: it gives it a TaxDome 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 request documents from every client on a checklist, 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/taxdome/jobs. | 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/taxdome/jobs with your API key. | cron or GitHub Actions. |

## Tools

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

### list_accounts

Client accounts, individuals and companies, with their contacts. Access: read. REST: `GET /api/v1/taxdome/accounts`. MCP: `taxdome_read → list_accounts`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `query` | string | no | Search by account name or contact email. |
| `type` | string | no | 'individual' or 'company'. |
| `limit` | integer | no | 1 to 100. Default: 25. |
| `cursor` | string | no | Next page cursor from the previous call. |

Lists client accounts, each an Individual or a Company, with the contacts linked to it. Search by name or email and page with the cursor. Visibility follows the rights of the login you connected: a team member sees the accounts they are assigned to or may view.

Example response:

```json
{
  "accounts": [
    {
      "account_id": "acc_4f21",
      "name": "Harbor Dental LLC",
      "type": "company",
      "contacts": [
        {
          "name": "Dana Reyes",
          "email": "dana@harbordental.example"
        }
      ]
    },
    {
      "account_id": "acc_7c09",
      "name": "Nguyen Family",
      "type": "individual",
      "contacts": [
        {
          "name": "Linh Nguyen",
          "email": "linh@nguyen.example"
        }
      ]
    }
  ],
  "next_cursor": null
}
```

### get_account

One account with its contacts, open jobs and open requests. Access: read. REST: `GET /api/v1/taxdome/accounts/{account_id}`. MCP: `taxdome_read → get_account`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `account_id` | string | yes | Account ID from list_accounts. |

Returns one account with its contacts, the jobs that are in progress and the client requests still open. Use it before writing to a client so your agent sees what they were already asked.

Example response:

```json
{
  "account_id": "acc_4f21",
  "name": "Harbor Dental LLC",
  "type": "company",
  "contacts": [
    {
      "name": "Dana Reyes",
      "email": "dana@harbordental.example",
      "portal_login": true
    }
  ],
  "open_jobs": [
    {
      "job_id": "job_3081",
      "name": "Annual Filing 2026",
      "stage": "Collect docs"
    }
  ],
  "open_requests": [
    {
      "request_id": "req_912",
      "title": "2026 tax documents"
    }
  ]
}
```

### list_pipelines

Pipelines with their stages and job templates. Access: read. REST: `GET /api/v1/taxdome/pipelines`. MCP: `taxdome_read → list_pipelines`.

No parameters.

Lists the firm's pipelines with their stages in order and the job templates available. Call it once to learn the stage names that list_jobs and create_job accept.

Example response:

```json
{
  "pipelines": [
    {
      "pipeline_id": "pl_annual",
      "name": "Annual Filing",
      "stages": [
        "Intake",
        "Collect docs",
        "Preparation",
        "Review",
        "Filed"
      ],
      "templates": [
        "Individual 1040",
        "Business return"
      ]
    }
  ]
}
```

### list_jobs

Jobs in progress or archived, with stage, assignee, priority and due date. Access: read. REST: `GET /api/v1/taxdome/jobs`. MCP: `taxdome_read → list_jobs`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `pipeline_id` | string | no | Only jobs in this pipeline. |
| `stage` | string | no | Only jobs at this stage. |
| `assignee` | string | no | Team member name. |
| `account_id` | string | no | Only jobs of this account. |
| `priority` | string | no | 'Low', 'Medium', 'High' or 'Urgent'. |
| `overdue` | boolean | no | true: only jobs past their due date. |
| `archived` | boolean | no | true: the Archived tab. Default: false. |
| `limit` | integer | no | 1 to 100. Default: 25. |
| `cursor` | string | no | Next page cursor from the previous call. |

Lists jobs the way Workflow > Jobs shows them: In progress by default, or archived. Filter by pipeline, stage, assignee, account or priority. With overdue set, only jobs whose due date has passed come back, oldest due date first.

Example response:

```json
{
  "jobs": [
    {
      "job_id": "job_3081",
      "name": "Annual Filing 2026",
      "account": "Harbor Dental LLC",
      "pipeline": "Annual Filing",
      "stage": "Collect docs",
      "assignee": "Maria Silva",
      "priority": "High",
      "due_date": "2026-10-09",
      "overdue": true
    }
  ],
  "next_cursor": null
}
```

### get_job

One job with its tasks, stage, assignee and dates. Access: read. REST: `GET /api/v1/taxdome/jobs/{job_id}`. MCP: `taxdome_read → get_job`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `job_id` | string | yes | Job ID from list_jobs. |

Returns one job with its tasks and which are done, the stage, the assignee, the priority and the dates. Tasks are the steps of the job, so this shows what is blocking it.

Example response:

```json
{
  "job_id": "job_3081",
  "name": "Annual Filing 2026",
  "account_id": "acc_4f21",
  "stage": "Collect docs",
  "assignee": "Maria Silva",
  "priority": "High",
  "due_date": "2026-10-09",
  "tasks": [
    {
      "title": "Receive bank statements",
      "done": false
    },
    {
      "title": "Receive payroll reports",
      "done": true
    }
  ]
}
```

### list_tasks

Tasks across jobs, with the job, assignee and due date. Access: read. REST: `GET /api/v1/taxdome/tasks`. MCP: `taxdome_read → list_tasks`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `job_id` | string | no | Only tasks of this job. |
| `assignee` | string | no | Team member name. |
| `due_before` | date | no | Only open tasks due before this date, ISO. |
| `cursor` | string | no | Next page cursor from the previous call. |

Lists the tasks that make up jobs. Filter by job, assignee or a due date; due_before returns open tasks due before that date, soonest first. Use it to find what a team member still owes.

Example response:

```json
{
  "tasks": [
    {
      "task_id": "tsk_551",
      "title": "Receive bank statements",
      "job_id": "job_3081",
      "assignee": "Maria Silva",
      "due_date": "2026-10-09",
      "done": false
    }
  ],
  "next_cursor": null
}
```

### list_invoices

Invoices of an account with amount, status and dates. Access: read. REST: `GET /api/v1/taxdome/accounts/{account_id}/invoices`. MCP: `taxdome_read → list_invoices`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `account_id` | string | yes | Account ID from list_accounts. |
| `cursor` | string | no | Next page cursor from the previous call. |

Lists the invoices of one account, newest first, with total, status as TaxDome shows it and issue date. Use it to avoid billing a client twice for one period.

Example response:

```json
{
  "invoices": [
    {
      "invoice_id": "inv_2207",
      "description": "Bookkeeping, September 2026",
      "total": 1200,
      "status": "paid",
      "issued": "2026-09-30"
    }
  ],
  "next_cursor": null
}
```

### list_requests

Client requests of an account, open and answered. Access: read. REST: `GET /api/v1/taxdome/accounts/{account_id}/requests`. MCP: `taxdome_read → list_requests`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `account_id` | string | yes | Account ID from list_accounts. |

Lists the client requests sent to one account, newest first, with title, due date and whether the client has answered. Check it before sending a new request to avoid a duplicate email.

Example response:

```json
{
  "requests": [
    {
      "request_id": "req_912",
      "title": "2026 tax documents",
      "due_date": "2026-10-16",
      "answered": false
    }
  ]
}
```

### create_account

Create a client account of type Individual or Company with its first contact. Access: write, asks the user first. REST: `POST /api/v1/taxdome/accounts`. MCP: `taxdome_write → create_account`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `type` | string | yes | 'individual' or 'company'. |
| `company_name` | string | no | Required for a company. |
| `first_name` | string | yes | First name of the contact. |
| `last_name` | string | yes | Last name of the contact. |
| `email` | string | yes | Email of the contact. |

Creates an account, then its first contact from the name and email. Creating an account does not give the client portal access, and this tool does not invite anyone. Needs the firm owner, an admin or the Manage accounts access right. By default you confirm each call; you can switch that off for this tool.

Example response:

```json
{
  "account_id": "acc_9d14",
  "name": "Cedar Studio LLC",
  "type": "company",
  "contacts": [
    {
      "name": "Priya Shah",
      "email": "priya@cedarstudio.example",
      "portal_login": false
    }
  ]
}
```

### create_job

Create a job for an account in a pipeline, with stage, assignee, priority and due date. Access: write. REST: `POST /api/v1/taxdome/accounts/{account_id}/jobs`. MCP: `taxdome_write → create_job`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `account_id` | string | yes | Account ID from list_accounts. |
| `pipeline_id` | string | yes | Pipeline ID from list_pipelines. |
| `stage` | string | no | Stage name. Default: the first stage. |
| `template` | string | no | Job template name from list_pipelines. |
| `assignee` | string | no | Team member name. |
| `priority` | string | no | 'Low', 'Medium', 'High' or 'Urgent'. |
| `due_date` | date | no | Due date, ISO. |

Creates a job for one account in a pipeline, optionally from a template so its tasks come with it. It reaches no client, so it does not ask for confirmation; archive_job undoes it in one call.

Example response:

```json
{
  "job_id": "job_3190",
  "name": "Annual Filing 2026",
  "account_id": "acc_4f21",
  "pipeline": "Annual Filing",
  "stage": "Intake",
  "assignee": "Maria Silva",
  "priority": "Medium",
  "due_date": "2027-03-15"
}
```

### archive_job

Move a job to the Archived tab. Access: write. REST: `POST /api/v1/taxdome/jobs/{job_id}/archive`. MCP: `taxdome_write → archive_job`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `job_id` | string | yes | Job ID from list_jobs. |

Moves one job from In progress to Archived. It reaches no client, and the job stays in the Archived tab with all its data, so it does not ask for confirmation.

Example response:

```json
{
  "job_id": "job_3190",
  "archived": true
}
```

### send_invoice

Create an invoice for an account from line items and send it to the client. Access: write, asks the user first. REST: `POST /api/v1/taxdome/accounts/{account_id}/invoices`. MCP: `taxdome_write → send_invoice`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `account_id` | string | yes | Account ID from list_accounts. |
| `items` | array | yes | Lines as { description, amount }. |
| `template` | string | no | Invoice template name to start from. |
| `due_date` | date | no | Due date, ISO. |

Creates an invoice from line items and sends it, as the Create button does in TaxDome, so there is no draft step. Returns the invoice ID and the total, which is the sum of the lines. Needs the firm owner or the Manage invoices access right. By default you confirm each call; you can switch that off for this tool.

Example response:

```json
{
  "invoice_id": "inv_2291",
  "account_id": "acc_4f21",
  "items": [
    {
      "description": "Bookkeeping, October 2026",
      "amount": 1200
    }
  ],
  "total": 1200,
  "due_date": "2026-10-28",
  "status": "sent"
}
```

### request_documents

Send a client request for documents or information to an account. Access: write, asks the user first. REST: `POST /api/v1/taxdome/accounts/{account_id}/documents/request`. MCP: `taxdome_write → request_documents`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `account_id` | string | yes | Account ID from list_accounts. |
| `title` | string | yes | Title the client sees. |
| `items` | array | yes | Names of the documents or questions, one field each. |
| `due_date` | date | no | Due date, ISO. |
| `reminder_days` | integer | no | Days between reminders. Default: 3. |

Sends a client request with the items you list as fields; the client gets an email and a mobile push notification. Reminders repeat every reminder_days, which is 3 in TaxDome by default. By default you confirm each call; you can switch that off for this tool.

Example response:

```json
{
  "request_id": "req_940",
  "account_id": "acc_4f21",
  "title": "2026 tax documents",
  "items": 3,
  "due_date": "2026-10-16",
  "reminder_days": 3,
  "status": "sent"
}
```

### send_message

Send a message to a client in a chat, now or at a set time. Access: write, asks the user first. REST: `POST /api/v1/taxdome/accounts/{account_id}/messages`. MCP: `taxdome_write → send_message`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `account_id` | string | yes | Account ID from list_accounts. |
| `body` | string | yes | Message text. |
| `send_at` | datetime | no | Schedule for later instead of sending now. |

Sends a message in the account's chat on its Communication tab; the message can be scheduled with send_at. Needs a login allowed to open chats for the account. By default you confirm each call; you can switch that off for this tool.

Example response:

```json
{
  "message_id": "msg_6120",
  "account_id": "acc_4f21",
  "status": "sent",
  "sent_at": "2026-10-14T09:00:00+02:00"
}
```

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

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

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

2. **Sign in to TaxDome in your Cloud Browser** Open your Cloud Browser in the console: your own Chrome in the cloud. Sign in to TaxDome 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 TaxDome 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.

```
For each company account in the Tax Prep 2026 pipeline that has no open request, send a client request titled "2026 tax documents" asking for last year's return, bank statements and payroll reports, due Friday.
```

### Call TaxDome 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/taxdome 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/taxdome/accounts/acc_4f21/invoices \
  -H "Authorization: Bearer $COTLET_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"items":[{"description":"Bookkeeping, October 2026","amount":1200}],"due_date":"2026-10-28"}'
```

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

```
{
  "invoice_id": "inv_2291",
  "account_id": "acc_4f21",
  "items": [
    {
      "description": "Bookkeeping, October 2026",
      "amount": 1200
    }
  ],
  "total": 1200,
  "due_date": "2026-10-28",
  "status": "sent"
}
```

## Why use Cotlet for TaxDome?

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

## Is it safe to connect TaxDome to Cotlet?

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

No, Cotlet is independent of TaxDome. TaxDome has no public API. Cotlet works through your own TaxDome account, the way you use TaxDome 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 TaxDome in your console: your agents lose access at once and you stay signed in. Signing out of TaxDome in the browser works too, and Reset browser deletes the whole profile.

## Is there a TaxDome MCP server on GitHub?

The realistic option today is doing the work by hand in TaxDome, or Zapier for contacts. TaxDome has no public API to build on, and its own MCP is not open to every firm yet. Cotlet signs in to your TaxDome account for you and exposes jobs, requests, invoices and chats as one MCP server and one REST API.

|  | By hand in TaxDome | Cotlet |
|---|---|---|
| Setup | Nothing to install; every job, request and invoice is a form you fill in | Sign up, sign in to TaxDome once, add one MCP server or API key |
| Repeat work | You create the same job, request or invoice for each client, one at a time | Your agent loops over the client list from one prompt or a schedule |
| When TaxDome changes | You learn the new screens | Our team tests it daily and fixes it for you; failed calls are free |
| Your TaxDome session | Your own browser login | 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 | You sign in again | Your agent gets a link to sign in again; we never save your password or bypass MFA |
| Where it runs | In your browser, while you work | Hosted: Claude Code, Codex, Cursor, n8n and scripts, also on a schedule |
| Price | Free, paid for with staff 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 TaxDome 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 TaxDome API cost?

Free 7-day trial with 2,000 credits, no card needed. After that, the TaxDome 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 TaxDome 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 TaxDome 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 TaxDome only after you enable it. When TaxDome 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 TaxDome, sign out of TaxDome 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.
- **TaxDome's terms:** You use your own TaxDome account and stay responsible for following TaxDome's terms. Cotlet is independent and not affiliated with TaxDome. [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 TaxDome in the console and press Request access. Then you create your API key and connect TaxDome there.

**Do I need to be technical?**

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

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

TaxDome offers no OAuth or API for this, so there is no scoped token to hold. 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 TaxDome MCP or a Professional plan?**

No. Cotlet works with your own TaxDome firm login and does not use TaxDome MCP, which is announced for Professional and Business plans first and is not open to every firm yet. What the agent may do follows your access rights, such as Manage invoices or Manage accounts.

**Can the agent send invoices without my approval?**

Only if you switch confirmation off for send_invoice. By default each invoice, request and message waits for your OK, because creating an invoice in TaxDome also sends it to the client.

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

No. Every call to create_account, send_invoice, request_documents or send_message 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_job, archive_job runs without asking, because it sends nothing to anyone and one call undoes it.

**Can I use the TaxDome 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/taxdome 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.