Fatture in Cloud MCP Server and API by Cotlet

by cotlet Your server? Claim it

answering

Fatture in Cloud MCP Server and API by Cotlet is answering right now. Last checked 1 min ago. It exposes 31 tools.

Fatture in Cloud MCP server: create invoice, send to SDI, add client, record expense.

Uptime history 15 hours of history

15 hours agonow

100.0%

Uptime 24h

108 of 108 checks

Tools

read from the server

246 ms

Response time

average over 24h

OAuth sign-in

Access

streamable-http

Nothing serious here today

Today is the operative word: we check Fatture in Cloud MCP Server and API by Cotlet every 15 minutes and re-read its code on every release. Watch it and you find out the day that stops being true.

Connect this server

Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 1 min ago.

Claude Code Claude Desktop Codex Cursor VS Code

run in your terminal

claude mcp add fatture-in-cloud --transport http https://cotlet.dev/mcp/v1/fatture-in-cloud/connect

Settings → Connectors → Add custom connector, then paste this address

https://cotlet.dev/mcp/v1/fatture-in-cloud/connect

~/.codex/config.toml

[mcp_servers.fatture-in-cloud]
url = "https://cotlet.dev/mcp/v1/fatture-in-cloud/connect"

.cursor/mcp.json

{
  "mcpServers": {
    "fatture-in-cloud": {
      "url": "https://cotlet.dev/mcp/v1/fatture-in-cloud/connect"
    }
  }
}

.vscode/mcp.json

{
  "servers": {
    "fatture-in-cloud": {
      "type": "http",
      "url": "https://cotlet.dev/mcp/v1/fatture-in-cloud/connect"
    }
  }
}

This endpoint answered with an authorization challenge. The server is running, and it signs you in through your browser: there is no API key to paste.

This server publishes 1 more address. The block above uses the one we reach during checks; the full list is under Endpoints below, and the author may intend a particular one for your client.

Available tools 31

Read directly from the server with tools/list, grouped by what they act on. If a tool disappears, we record the date.

cotlet

cotlet_app_guide

How to work in an app by clicking in the user's Cloud Browser with Cotlet's browser tools: which browser to use for this workspace and the sign-in link, the method step by step, the app's screens, menus and actions, notes, and the app's dedicated tools when Cotlet has them. Call it before the first browser step in an app. Works for any web app; one outside Cotlet's catalog gets the general method. Free, no browser session. For Fatture in Cloud it covers these actions: Create invoice, Send to SDI, Add client, Record expense, List unpaid invoices.

cotlet_apps

The apps of the user's workspace and whether each works now: the app account in the user's Cloud Browser (connected, signed out, signed in but not connected), and the one step the user has to take, with the console link. Free. Needs the user's Cotlet API key or sign-in.

cotlet_balance

The user's current credit balance. Free. Needs the user's Cotlet API key or sign-in.

cotlet_browser_click

Clicks element `element`, or point `x`, `y` of the screenshot; `double` double-clicks, `button: right` right-clicks. Answers the page after it: the elements and text in view, with the same numbers. Says when nothing changed. A link that would open a new tab opens in this one. Buttons that pay or buy, and sign-in and account pages, are refused.

cotlet_browser_close

Ends the browser session when the task is done: the browser keeps its cookies and sleeps, and the per-minute charge stops. Answers the session's minutes and credits.

cotlet_browser_download

Gets the file that clicking `element` (a download link or button) or opening `url` starts: answers its name, type, size and a link valid 15 minutes; CSV, JSON and other text files also as text.

cotlet_browser_drag

Drags from one element or point to another: a card between columns, a piece on a board, a slider's handle. Answers the page after it: the elements and text in view, with the same numbers.

cotlet_browser_evaluate

Runs a JavaScript function body on the page and answers what it returns, as JSON. Use it to extract data the page holds (a table, a list, attributes); act with the other tools. It cannot send requests, click, submit, or read cookies or storage; a filled field's value reads [hidden by Cotlet]. Example: return [...document.querySelectorAll('h2')].map(h => h.innerText)

cotlet_browser_fill_form

Fills several fields in one step: text fields take text, drop-downs an option's label, checkboxes, radios and switches true or false. Stops at the first field that fails and names those filled. Does not send the form: click its button after. Answers the page after it: the elements and text in view, with the same numbers.

cotlet_browser_find

Finds `text` on the whole current page, frames included: the elements whose label holds it, with their numbers, and each line of text that holds it. Use it instead of reading or scrolling a long page for one thing.

cotlet_browser_hover

Rests the pointer on an element or a point, to open a hover menu, a tooltip or a preview. Answers the page after it: the elements and text in view, with the same numbers.

cotlet_browser_navigate

Opens `url` in the current tab, or goes `history` back or forward. Answers the page after it: the elements and text in view, with the same numbers.

cotlet_browser_open

Starts the user's Cloud Browser (a real Chrome on Cotlet, where the user is signed in to their sites) and opens `url`. Call it first. The URL goes to the site's open tab, else to a new tab, so the user's own tabs stay. Answers the page after it: the elements and text in view, with the same numbers. In Fatture in Cloud it serves these actions: Create invoice, Send to SDI, Add client, Record expense, List unpaid invoices.

cotlet_browser_press

Presses a key on the focused element: Enter to send, Tab to the next field, Escape to close a pop-up, arrows in a list or slider, or one character (a site's shortcut). Answers the page after it: the elements and text in view, with the same numbers.

cotlet_browser_read

The whole current page: its text (up to 20,000 characters) and a numbered list of its links, buttons, fields and other controls, open dialogs first. Use it on a new page or when a step's answer is not enough; `element` reads only inside one element (a dialog, a form, a list). Never returns field values, cookies or storage.

cotlet_browser_screenshot

A JPEG of the visible part of the page. Use it for boards, canvases, maps, charts and layout that the text does not show, then click or drag by `x`, `y` of the image.

cotlet_browser_scroll

Scrolls with the mouse wheel: `down` or `up` by `screens`, to `top` or `bottom`, until `element` is in view, or inside a panel or list (`inside`). Content that loads on scroll appears. Answers the page after it: the elements and text in view, with the same numbers.

cotlet_browser_select

Chooses `option` (its label as listed, or its value) in drop-down `element`. For a home-made drop-down, click it, then click the option. Answers the page after it: the elements and text in view, with the same numbers.

cotlet_browser_tabs

The tabs of the user's web browser, where they keep their signed-in sites open. `list` (default) answers each tab's id, URL and title and which is shown; `switch` with `tab` shows that tab, and every later step acts on it; `new` with `url` opens a tab (at most 8); `close` with `tab` closes it. Work in the tab of the site the task is about and close only the tabs you opened.

cotlet_browser_type

Types `text` into field `element`, replacing what it held; `submit` presses Enter after it. For several fields use fill_form. Without `element` the text goes where the focus is, as a person types after clicking: for spreadsheet cells and editors that read does not number (Google Sheets, Docs), click the place first; there a tab in `text` presses Tab and a line break Enter, so one call fills a table. Answers the page after it: the elements and text in view, with the same numbers. Password, card and one-time code fields are refused: the user types them.

cotlet_browser_upload

Puts files into file field or upload button `element`: each file is {"url": "https://..."} or {"file_id": "..."} of a file uploaded to Cotlet; up to 10 files, 20 MB each. Answers the page after it: the elements and text in view, with the same numbers.

cotlet_browser_wait

Waits until `text` shows on the page (at most `seconds`, default 5, up to 20), or just `seconds`: for results that load slowly. Says whether the text appeared. Answers the page after it: the elements and text in view, with the same numbers.

cotlet_get_call

Status of an earlier Cotlet call, by its call_id: pending (waits for the owner's approval in the Cotlet console), approved, running, success, rejected, expired, blocked or failed. For a call that answered with status pending or running.

cotlet_report_issue

Sends a report to the Cotlet team: a tool that failed or returned wrong data, an error you could not get past, or a step the browser could not do, with the page, the step and what you saw. A missing dedicated tool is not a problem to report: do the task in the browser. A feature the user asks for goes as feature_request. A report promises nothing: tell the user it was sent, never that something will be built or fixed, or when. The report carries the error text and call_id when there is one, never passwords or tokens. Needs the user's Cotlet API key or sign-in.

cotlet_upload_file

Returns a one-time upload_url and a file_id for a local file (an image for a post, an attachment). The file is sent to upload_url with an HTTP PUT; an argument that takes a file accepts {"file_id": "..."}. Up to 25 MB, the URL works once. Free. Needs the user's Cotlet API key or sign-in.

cotlet_whoami

The Cotlet account this connection acts as: email, workspace, access status, the API key or OAuth client in use with its scope, the apps the workspace may call and its credit balance. Free. Needs the user's Cotlet API key or sign-in.

fatture

fatture_in_cloud_add_client

Add client in the user's own Fatture in Cloud account from ChatGPT, Claude or any AI agent. Returns how to do it in Fatture in Cloud step by step (screens, buttons, fields) and opens nothing by itself; then do it with the cotlet_browser_* tools in the user's Fatture in Cloud Cloud Browser. Fatture in Cloud's official API: Yes, Fatture in Cloud has a documented REST API (v2) for issued invoices, clients, received documents, e-invoices to SDI and attachments (checked 14 Oct 2026), but it has no official MCP server.

fatture_in_cloud_create_invoice

Create invoice in the user's own Fatture in Cloud account from ChatGPT, Claude or any AI agent. Returns how to do it in Fatture in Cloud step by step (screens, buttons, fields) and opens nothing by itself; then do it with the cotlet_browser_* tools in the user's Fatture in Cloud Cloud Browser. Fatture in Cloud's official API: Yes, Fatture in Cloud has a documented REST API (v2) for issued invoices, clients, received documents, e-invoices to SDI and attachments (checked 14 Oct 2026), but it has no official MCP server.

fatture_in_cloud_list_unpaid_invoices

List unpaid invoices in the user's own Fatture in Cloud account from ChatGPT, Claude or any AI agent. Returns how to do it in Fatture in Cloud step by step (screens, buttons, fields) and opens nothing by itself; then do it with the cotlet_browser_* tools in the user's Fatture in Cloud Cloud Browser. Fatture in Cloud's official API: Yes, Fatture in Cloud has a documented REST API (v2) for issued invoices, clients, received documents, e-invoices to SDI and attachments (checked 14 Oct 2026), but it has no official MCP server.

fatture_in_cloud_record_expense

Record expense in the user's own Fatture in Cloud account from ChatGPT, Claude or any AI agent. Returns how to do it in Fatture in Cloud step by step (screens, buttons, fields) and opens nothing by itself; then do it with the cotlet_browser_* tools in the user's Fatture in Cloud Cloud Browser. Fatture in Cloud's official API: Yes, Fatture in Cloud has a documented REST API (v2) for issued invoices, clients, received documents, e-invoices to SDI and attachments (checked 14 Oct 2026), but it has no official MCP server.

fatture_in_cloud_send_to_sdi

Send to SDI in the user's own Fatture in Cloud account from ChatGPT, Claude or any AI agent. Returns how to do it in Fatture in Cloud step by step (screens, buttons, fields) and opens nothing by itself; then do it with the cotlet_browser_* tools in the user's Fatture in Cloud Cloud Browser. Fatture in Cloud's official API: Yes, Fatture in Cloud has a documented REST API (v2) for issued invoices, clients, received documents, e-invoices to SDI and attachments (checked 14 Oct 2026), but it has no official MCP server.

Endpoints

URL	Transport	State	Latency	Checked
https://cotlet.dev/mcp/v1/fatture-in-cloud/connect	streamable-http	sign-in	221 ms	1 min ago
https://cotlet.dev/mcp/v1/fatture-in-cloud	streamable-http	answering	124 ms	1 min ago

Alternatives to Fatture in Cloud MCP Server and API by Cotlet

same job, measured the same way

Invoice Ninja MCP Server and API by Cotlet

by cotlet

Invoice Ninja MCP server: create invoice, send invoice, create quote, record payment.

answering

Joist MCP Server and API by Cotlet

by cotlet

Joist MCP server: create estimate, convert estimate to invoice, list invoices, add client.

answering

Holded MCP Server and API by Cotlet

by cotlet

Holded MCP server: create invoice, send invoice, create expense, add contact, list unpaid invoices.

answering

17hats MCP Server and API by Cotlet

by cotlet

17hats MCP server: add contact, create project, send quote, send invoice, record payment.

31 tools answering

MYOB MCP Server and API by Cotlet

by cotlet

MYOB MCP server: create invoice, send invoice, record payment, create bill, list overdue invoices.

answering

Thryv MCP Server and API by Cotlet

by cotlet

Thryv MCP server: list appointments, book appointment, create invoice, add client, send message.

answering

Bloom MCP Server and API by Cotlet

by cotlet

Bloom MCP server: create lead, create project, send invoice, send contract, record payment.

31 tools answering

Jobber MCP Server and API by Cotlet

by cotlet

Jobber MCP server: create quote, convert quote to job, create invoice, send invoice.

answering

Fatture in Cloud MCP Server and API by Cotlet — questions

Answers built from our own checks of this server.

What can Fatture in Cloud MCP Server and API by Cotlet do?

It exposes 31 tools, read directly from the server on our last check. Among them: cotlet_app_guide, cotlet_apps, cotlet_balance, cotlet_browser_click, cotlet_browser_close, cotlet_browser_download and 25 more. The full list with descriptions is on this page — we take it from the server itself via tools/list, not from a README. How MCP servers expose tools in the first place →

What is Fatture in Cloud MCP Server and API by Cotlet mostly used for?

Its tools cluster around cotlet and fatture. That is what this server is built to work with — the grouping comes from the actual tool names, not from a category we assigned.

Is Fatture in Cloud MCP Server and API by Cotlet working right now?

We send a real MCP handshake every 15 minutes. Over the last 24 hours 108 of 108 checks got a reply (100.0%), average response time 246 ms. The bar chart above shows every period we have measured.

How do I connect Fatture in Cloud MCP Server and API by Cotlet?

Copy the ready config from this page. We generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each in the form that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address. You sign in through your browser once and the client keeps the session: no key to copy, and it refuses anonymous clients.

How do you sign in to Fatture in Cloud MCP Server and API by Cotlet?

No API key is involved. Fatture in Cloud MCP Server and API by Cotlet answers our knock with an OAuth challenge, so you authorise it once in your browser and the client keeps the session. That is also why we see no tool list: it will not describe itself to an anonymous client, and that is the server working as intended, not a fault.

How fast is Fatture in Cloud MCP Server and API by Cotlet?

It answers our handshake in 246 ms on average, which is faster than 55% of all working MCP servers we measure. The comparison comes from our own checks across the whole registry, every 15 minutes.