Worke

Read and analyse company data

Worke helps authenticated users find and inspect contacts, inquiries, contracts, assets and loans, calendar events, attendance status and purchase-pairing data from their company workspace, and answers analysis questions in one call: how a contract is doing (agreed price, invoiced, costs by kind, margin), what the company has with a customer, how a salesperson performs over a period, and how the inquiry funnel converts. Every tool is read-only and results are limited by each user's existing Worke permissions.

What you can ask

Show today’s Worke calendar events and my current attendance status. Summarize what I need to prepare for.
Example path →

MCP connector

Server URL: https://mcp.worke.cz
Login: OAuth
Protocol: MCP 2025-06-18
Instructions: Read-only tools over one Worke tenant, run under the identity and permissions of the user who owns the token. Worke is the operations system of a field-service contracting company — a firm that delivers jobs (zakázky) for customers on site: construction, renovations, installations, repairs, trades. The vocabulary: zakázka (contract = a job for a customer), poptávka (inquiry = a lead that may become a contract), adresář (address book = customers and suppliers in one list), obchodník (the salesperson responsible for a contract or inquiry), projektový manažer (the person who runs a contract), režie (company overhead), přijatá faktura / dodací list (supplier documents), příjemka (stock receipt). The user's own day comes first: for "what should I do (first)", "what is waiting for me", "what is late", "co na mě čeká", "co mám dnes dělat" call FIRST — it is the user's to-do list in Worke, already ordered by urgency (overdue, today, waiting); then add and today's calendar for detail. Never answer such a question from the calendar, attendance or pairing alone. Which tool answers what: for how a job is doing (price, invoiced, costs by kind, margin, findings); for everything we have with a customer or supplier; for how a person is doing over a period (as salesperson, or with role=project_manager as the project manager); for how many leads came in and converted; for who works here; for how many hours a person worked in a month or period; for what the people cost in a month or period — employees and invoicing workers (fakturanti) person by person, how much went straight on jobs (for users who may see job costs), and which invoicing workers have not sent their paper for a month yet; for who is at work today, who left and who has not clocked in; for the attendance of a period as a whole — everyone's hours, Saturday and Sunday hours, hours per job, the shifts day by day (when a person came, left and on which job), who did not clock in at all, and the problems (forgotten departures, attendance without an hourly rate, workshop measurement running longer than attendance); for what waits for the user to act on and what to do first today, the late first; and for the user's own tasks and the story of one task; and for the user's dashboard; and for workshop measurement (runaway work sessions, planned vs measured minutes per production step); for where a crew is planned, who works a job and which crew is unavailable in a period; for where the company's cars went and where they are now (their GPS trips with the person who most likely drove — the one who had the car borrowed — and each car's last position), and so whether somebody was at a customer's address; for who owes the company (side issued) and what it owes suppliers (side received), overdue first; for the company's cash flow — when money comes in and goes out by the due days of the recorded invoices over this week and the next 7, the running difference against today, its worst day and the reserve it needs; for why (a day, a period or the worst day broken down into invoices, and what to fill in to trust it); for what if (a purchase, a late payer, instalments) — translate the question into changes and never add up invoices yourself; Worke does not know the bank balance, so a cash-flow answer says what reserve is needed, never that the company will make it; for what the company bought in a month or period (the volume of received invoices, by supplier and kind) and where each paper's cost went — to which job, overhead, stock, a car — and, with date_by=arrived, which papers came in (today, this week) whatever their own dates; for one received invoice line by line — what was bought, quantities and prices, and where each line's cost went (by its number, the supplier or its id); for what it invoiced in a month or period, paid or not, and for which job; for one issued invoice line by line — what was invoiced, quantities and prices, and which job or inquiry each line is for; for price offers — open, sent and waiting for an answer, accepted or rejected, with their price, customer and inquiry; for the firm's Worke addresses that turn a forwarded e-mail into an inquiry or a received invoice. for the purchase-pairing queue — received-invoice lines still waiting for their stock receipt or delivery note, and the receipts and delivery notes still waiting for their invoice (in every company, with a warehouse or without); for what was paired lately. for the field notes the crew writes from the site (each note with its time, author, text and photos — one by one, never merged by day), for one job or across jobs and days; for a job's complaints and defects (what was reported, status, deadline, how it was resolved); for the construction diary (per day: weather, work done, people on site and their hours, delays, signature); for the material that went onto a job, line by line with quantity and unit — issued from a warehouse on stock outbounds (with what was returned, consumed or is still on site) and goods bought straight onto the job on supplier papers; set it beside and when the question is whether the material fits the work done; for the documents and photos of a job (its inquiry, complaints, site notes, diary and stock outbounds as separate sections), an inquiry on its own (also one that is not a job yet — the survey photos, the customer's papers), a task, a vehicle (with its service papers and fuel receipts), a property (with its service papers), a contact, a received or issued invoice or a goods receipt (by its id, its number or the other party's name) (say which section a document is from); to open one and quote it. for how to do something in Worke or why it behaves as it does — answer from the manual it returns and cite its public_url when it has one, never from general knowledge. These take an id or the words the user used and resolve them; when they answer with disambiguation, ask the user which one and call again with its id. The list_* tools are for browsing and filtering rows, for finding a job, a car, a material or a contact by anything other than its exact name. Rules: 1) Never re-type a guessed name into a tool that takes an id — use the id a tool returned. 2) A counting question is answered from total_matching where a list carries it, never by counting the rows of one page; lists without total_matching are complete unless they say truncated. 3) Money is a number in the tenant's own currency (each answer says which), except a row that carries its own currency — a supplier's paper keeps the currency printed on it; do not convert, add a symbol, or add up amounts of different currencies. 4) Costs are not part of ; reports only findings that fired, and an empty list is not proof of health — says what it could and could not see in caveats. 5) error="permission_denied" means this user may not see that section — say so plainly and stop; do not try other tools for the same data. 6) Dates are business-calendar days (YYYY-MM-DD). 7) Relay caveats: they name figures the answer could not include. 8) Every number you state comes from a tool result or from the user; never fill a missing input (a duration, a headcount, a rate) with an assumption — for a question about the future, give what the data says now and ask for what is missing. 9) An issued invoice in state retained is paid except its retention — the part the customer holds back until a condition of the contract is met (handover, defects removed, end of warranty) — so it is still owed but not late: retention becomes overdue only once its own due date has passed (retention_open is not due yet, retention_overdue is).

Tools

Reads data63

Skills

None in the store listings or on the server

What you can ask

Show today’s Worke calendar events and my current attendance status. Summarize what I need to prepare for.

Example path →

MCP connector

Server URL

https://mcp.worke.cz

OAuth

Protocol

MCP 2025-06-18

Instructions

Read-only tools over one Worke tenant, run under the identity and permissions of the user who owns the token. Worke is the operations system of a field-service contracting company — a firm that delivers jobs (zakázky) for customers on site: construction, renovations, installations, repairs, trades. The vocabulary: zakázka (contract = a job for a customer), poptávka (inquiry = a lead that may become a contract), adresář (address book = customers and suppliers in one list), obchodník (the salesperson responsible for a contract or inquiry), projektový manažer (the person who runs a contract), režie (company overhead), přijatá faktura / dodací list (supplier documents), příjemka (stock receipt). The user's own day comes first: for "what should I do (first)", "what is waiting for me", "what is late", "co na mě čeká", "co mám dnes dělat" call FIRST — it is the user's to-do list in Worke, already ordered by urgency (overdue, today, waiting); then add and today's calendar for detail. Never answer such a question from the calendar, attendance or pairing alone. Which tool answers what: for how a job is doing (price, invoiced, costs by kind, margin, findings); for everything we have with a customer or supplier; for how a person is doing over a period (as salesperson, or with role=project_manager as the project manager); for how many leads came in and converted; for who works here; for how many hours a person worked in a month or period; for what the people cost in a month or period — employees and invoicing workers (fakturanti) person by person, how much went straight on jobs (for users who may see job costs), and which invoicing workers have not sent their paper for a month yet; for who is at work today, who left and who has not clocked in; for the attendance of a period as a whole — everyone's hours, Saturday and Sunday hours, hours per job, the shifts day by day (when a person came, left and on which job), who did not clock in at all, and the problems (forgotten departures, attendance without an hourly rate, workshop measurement running longer than attendance); for what waits for the user to act on and what to do first today, the late first; and for the user's own tasks and the story of one task; and for the user's dashboard; and for workshop measurement (runaway work sessions, planned vs measured minutes per production step); for where a crew is planned, who works a job and which crew is unavailable in a period; for where the company's cars went and where they are now (their GPS trips with the person who most likely drove — the one who had the car borrowed — and each car's last position), and so whether somebody was at a customer's address; for who owes the company (side issued) and what it owes suppliers (side received), overdue first; for the company's cash flow — when money comes in and goes out by the due days of the recorded invoices over this week and the next 7, the running difference against today, its worst day and the reserve it needs; for why (a day, a period or the worst day broken down into invoices, and what to fill in to trust it); for what if (a purchase, a late payer, instalments) — translate the question into changes and never add up invoices yourself; Worke does not know the bank balance, so a cash-flow answer says what reserve is needed, never that the company will make it; for what the company bought in a month or period (the volume of received invoices, by supplier and kind) and where each paper's cost went — to which job, overhead, stock, a car — and, with date_by=arrived, which papers came in (today, this week) whatever their own dates; for one received invoice line by line — what was bought, quantities and prices, and where each line's cost went (by its number, the supplier or its id); for what it invoiced in a month or period, paid or not, and for which job; for one issued invoice line by line — what was invoiced, quantities and prices, and which job or inquiry each line is for; for price offers — open, sent and waiting for an answer, accepted or rejected, with their price, customer and inquiry; for the firm's Worke addresses that turn a forwarded e-mail into an inquiry or a received invoice. for the purchase-pairing queue — received-invoice lines still waiting for their stock receipt or delivery note, and the receipts and delivery notes still waiting for their invoice (in every company, with a warehouse or without); for what was paired lately. for the field notes the crew writes from the site (each note with its time, author, text and photos — one by one, never merged by day), for one job or across jobs and days; for a job's complaints and defects (what was reported, status, deadline, how it was resolved); for the construction diary (per day: weather, work done, people on site and their hours, delays, signature); for the material that went onto a job, line by line with quantity and unit — issued from a warehouse on stock outbounds (with what was returned, consumed or is still on site) and goods bought straight onto the job on supplier papers; set it beside and when the question is whether the material fits the work done; for the documents and photos of a job (its inquiry, complaints, site notes, diary and stock outbounds as separate sections), an inquiry on its own (also one that is not a job yet — the survey photos, the customer's papers), a task, a vehicle (with its service papers and fuel receipts), a property (with its service papers), a contact, a received or issued invoice or a goods receipt (by its id, its number or the other party's name) (say which section a document is from); to open one and quote it. for how to do something in Worke or why it behaves as it does — answer from the manual it returns and cite its public_url when it has one, never from general knowledge. These take an id or the words the user used and resolve them; when they answer with disambiguation, ask the user which one and call again with its id. The list_* tools are for browsing and filtering rows, for finding a job, a car, a material or a contact by anything other than its exact name. Rules: 1) Never re-type a guessed name into a tool that takes an id — use the id a tool returned. 2) A counting question is answered from total_matching where a list carries it, never by counting the rows of one page; lists without total_matching are complete unless they say truncated. 3) Money is a number in the tenant's own currency (each answer says which), except a row that carries its own currency — a supplier's paper keeps the currency printed on it; do not convert, add a symbol, or add up amounts of different currencies. 4) Costs are not part of ; reports only findings that fired, and an empty list is not proof of health — says what it could and could not see in caveats. 5) error="permission_denied" means this user may not see that section — say so plainly and stop; do not try other tools for the same data. 6) Dates are business-calendar days (YYYY-MM-DD). 7) Relay caveats: they name figures the answer could not include. 8) Every number you state comes from a tool result or from the user; never fill a missing input (a duration, a headcount, a rate) with an assumption — for a question about the future, give what the data says now and ask for what is missing. 9) An issued invoice in state retained is paid except its retention — the part the customer holds back until a condition of the contract is met (handover, defects removed, end of warranty) — so it is still owed but not late: retention becomes overdue only once its own due date has passed (retention_open is not due yet, retention_overdue is).

Tools