[Cotlet](https://cotlet.dev/index.md) · [Integrations](https://cotlet.dev/integrations.md) · [How it works](https://cotlet.dev/how-it-works.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) # Ordrestyring API and MCP server: Let your AI agent run your Ordrestyring paperwork. > Ordrestyring has a GraphQL API and no official MCP server (checked 31 Oct 2026). The API key is not self-serve: you ask Ordrestyring support for it. Cotlet runs 12 Ordrestyring tools hosted, over MCP for agents and REST for scripts. Orders, hours, materials and planning for your Ordrestyring account. Use it in ChatGPT, Claude or any AI agent over MCP, or in n8n, Make and scripts over REST. [MCP setup](https://cotlet.dev/integrations/ordrestyring-api-mcp-server.md#connect) [REST API guide](https://cotlet.dev/integrations/ordrestyring-api-mcp-server.md#rest-api) - Free 7-day trial, no card - Unofficial, not affiliated with Ordrestyring - Page: https://cotlet.dev/integrations/ordrestyring-api-mcp-server ## What can you automate in Ordrestyring? - Create an order from a call - Log hours from a message - Book materials after a job - Plan next week's crew - Approve hours before payroll - Prepare invoice drafts ## Does Ordrestyring have an MCP server or an API? - The public docs show one query, cases, and two example mutations. The full list of operations sits in GraphiQL behind the key. - Limits: 1,000 requests a minute on weekdays 05:30 to 23:59, 4,500 at night and on weekends, and a hard cap of 60 a minute on every route. - Zapier, Make and n8n have no Ordrestyring app that we found. The listed integrations cover accounting and payroll, not orders, hours or planning. | What you need | GraphQL API | GitHub MCP server | Cotlet | |---|---|---|---| | Start without asking support | No, key from support | No, needs the same key | Yes, your own login | | Works from an AI agent | No MCP server | Yes, you run it | Yes, hosted | | Read orders, hours and materials | If you write queries | Yes | Yes | | Log hours, plan crews, draft invoices | If you write mutations | Off by default, you opt in | Yes, risky ones ask first | | Allowed by Ordrestyring's terms | Yes, official | Yes, official API | Uses the web app | Checked 31 Oct 2026. Sources: [Ordrestyring GraphQL API docs](https://graphql.ordrestyring.dk/docs), [Ordrestyring subscription terms](https://ordrestyring.dk/betingelser-og-vilkar/abonnementsvilkar/), [Ordrestyring pricing](https://ordrestyring.dk/priser/) ## How does Cotlet connect to Ordrestyring? 1. **Sign in to Ordrestyring.** Use your own account in its Cotlet Cloud Browser. 2. **Choose MCP or REST.** Connect your agent or create a Cotlet API key. 3. **Run your workflow.** Ask your agent or send an HTTP request. We never keep your Ordrestyring password, and nothing that lands in a fitter's app or locks hours happens until you approve it. ## Connect Ordrestyring to your agent or workflow Use MCP with your AI agent, or HTTP requests in n8n, Make, Zapier and scripts. Follow the MCP setup below or jump to the REST guide. 1. **Enable Ordrestyring for agents.** Sign up, log in to Ordrestyring in its Cloud Browser, then press Enable for agents. 2. **Add the Cotlet address.** Add https://cotlet.dev/mcp/v1 as an MCP server or connector in your agent. 3. **Approve the connection.** Chat apps ask you to sign in to Cotlet. Editors, n8n and scripts use an API key from the console. One shared address, `https://cotlet.dev/mcp/v1`, also carries Ordrestyring next to your other apps. If you enable Ordrestyring after connecting, refresh the connector so the new tools show up. Claude: ``` Settings > Connectors > Add custom connector URL: https://cotlet.dev/mcp/v1/connect Claude Code: claude mcp add --transport http cotlet-ordrestyring \ https://cotlet.dev/mcp/v1 \ --header "Authorization: Bearer $COTLET_API_KEY" ``` ChatGPT: ``` Settings > Apps & Connectors > Create MCP server URL: https://cotlet.dev/mcp/v1/connect Authentication: OAuth ``` Cursor: ``` // ~/.cursor/mcp.json { "mcpServers": { "cotlet-ordrestyring": { "url": "https://cotlet.dev/mcp/v1", "headers": { "Authorization": "Bearer ${env:COTLET_API_KEY}" } } } } ``` Codex: ``` # ~/.codex/config.toml [mcp_servers.cotlet-ordrestyring] url = "https://cotlet.dev/mcp/v1" bearer_token_env_var = "COTLET_API_KEY" ``` n8n: ``` MCP Client Tool (inside an AI Agent) Transport: HTTP Streamable URL: https://cotlet.dev/mcp/v1 Auth: Bearer, Tool: ordrestyring_read ``` Make, Zapier: ``` Make: MCP Client > Call a tool Zapier: MCP Client by Zapier > Run Tool Server URL: https://cotlet.dev/mcp/v1 Token: Tool: ordrestyring_write ``` ## How to use the Ordrestyring REST API ### Create your Cotlet API key Create a Cotlet API key with access to Ordrestyring and its read operations. Store it as `COTLET_API_KEY` in your environment or automation platform's credential store. Connect Ordrestyring in Cotlet and enable it for agents. Account access: Your own Ordrestyring user (planning, customers and hour approval need the matching rights or an Admin; a basis user reaches only the orders assigned to them). ### Make your first Ordrestyring API request REST: ``` curl "https://cotlet.dev/api/v1/ordrestyring/orders?status=in_progress" \ -H "Authorization: Bearer $COTLET_API_KEY" ``` ### Read orders and apply the operation limits A successful REST call puts the tool output in `result`. This illustrative response excerpt omits call IDs, messages and credit details. Illustrative response excerpt: ``` { "status": "success", "app": "ordrestyring", "tool": "list_orders", "result": { "orders": [ { "order_id": "10482", "customer": "Nørregaard Ejendomme", "title": "Badeværelse Nørrebro", "status": "in_progress", "responsible": "Jonas H." }, { "order_id": "10469", "customer": "Fjordvej Boligforening", "title": "Tagrende udskiftning", "status": "in_progress", "responsible": "Jonas H." } ], "next_cursor": null } } ``` Returns the orders from the Orders menu with customer, status and responsible employee. The default statuses are open, in progress, closed, posted and cancelled, and your firm may have renamed them. A basis user sees only the orders assigned to them and the statuses their group may see. Replace `in_progress` with the status you need, or leave it out for every order you may see. Keep the same filters when continuing a list. Compare changed record values as well as order numbers when refreshing your destination. ### Ordrestyring workflows for agents and automations | Tool | Connect through | Example workflow | |---|---|---| | n8n | HTTP Request | Read the hours sent for approval each Friday. Use `list_time_entries` in your configured payroll report. | | Make | HTTP > Make a request | Read the economy totals of an order into a sheet. Use `get_order` in your configured business report. | | Python or Node.js | REST API | Flag material lines where cost and sales price are equal. Use `list_material_lines` in your configured business report. | Send `Authorization: Bearer ` in request headers. You configure the schedule, destination and record comparisons. Cotlet reads Ordrestyring; your workflow steps write to your chosen destination. These HTTP workflows do not require a native Cotlet connector or a prebuilt template. Python and Node.js can use the same HTTP requests without an AI agent. Keep access keys in credentials, outside shared workflow exports. The [API and MCP reference](https://cotlet.dev/integrations/ordrestyring-api-mcp-server.md#tools) lists operations and inputs. The [REST API guide](https://cotlet.dev/docs/api.md) explains authentication, errors and approvals. ## Ordrestyring API endpoints and MCP tools ### Orders and customers An order needs a customer, so create_order takes a customer ID from the customer list. Basis users see only the orders assigned to them. - **List orders** (`list_orders`, read): Orders with customer, status and responsible employee, newest first. - **Get order** (`get_order`, read): One order with its customer, status and the economy totals. - **List customers** (`list_customers`, read): Customers from the customer list, searchable by name. - **Create order** (`create_order`, write): Create an order for an existing customer. ### Hours and materials Hours already approved cannot be edited by anyone. Approval needs the Time approval add-on and an Admin. - **List time entries** (`list_time_entries`, read): Hours registered on an order or by an employee for a week or period. - **Log hours** (`log_time`, write): Register hours on an order for the signed-in employee. - **Approve or reject hours** (`approve_hours`, write, asks first): Approve or reject hours that employees sent for approval. - **List material lines** (`list_material_lines`, read): Materials booked on an order, with cost and sales price. - **Add material line** (`add_material_line`, write): Book a material on an order. ### Planning and invoice drafts Planned time shows in the fitter's app at once. Invoice drafts are never sent from here. - **List planned tasks** (`list_planned_tasks`, read): The day overview: who is planned on which order, day by day. - **Plan an employee** (`plan_task`, write, asks first): Plan an employee on an order for a start and end time. - **Create invoice draft** (`create_invoice_draft`, write): Start an invoice draft from the hours and materials of an order. Inputs, REST path and example response of every tool: https://cotlet.dev/integrations/ordrestyring-api-mcp-server#tools ## Who can see my Ordrestyring session, and how do I revoke it? - **What we store.** Your logged-in Ordrestyring profile, encrypted with AES-256-GCM, in Finland. Not the password. - **What your agent gets.** The 12 Ordrestyring tools. Never the cookie. - **What the session sees.** What your user sees: orders, customers, hours, materials, planning. - **What no tool touches.** Sending invoices, subscription, payroll, passwords and deleting. - **If Ordrestyring logs you out.** Your agent gets a link. You sign in again, we never type your password. - **How to cut access.** Disable for agents, reset the browser, or change your Ordrestyring password. Our site scores A+ on Qualys SSL Labs, securityheaders.com and Mozilla Observatory ([live results](https://cotlet.dev/security.md)). There is no SOC 2 report or third-party pentest yet. ## Is it against Ordrestyring's terms? Account safety > Aceve reserves the right to put technical measures in place and enforce them, including access control, limits on simultaneous logins and IP validation, to protect the application from misuse and unauthorised use. Aceve may suspend access without notice on suspicion of unauthorised or improper use. > > [Ordrestyring subscription terms, section 2.6 (translated from Danish)](https://ordrestyring.dk/betingelser-og-vilkar/abonnementsvilkar/) Section 2.4 makes each user licence personal, one person per account, and section 2.3 makes you answerable for what is done through your login. The terms never mention bots, scraping or AI agents. We found no public case of an Ordrestyring account closed for automation (checked 31 Oct 2026). Connect your own user, not a login shared with a colleague. How we keep your account looking like you: - Your own user, logged in by you - One Cloud Browser with its own IP and cookies - Planning and hour approval wait for your OK - No tool deletes an order, customer or invoice - If Ordrestyring objects, we pause the Ordrestyring tools for everyone within 24 h > Ordrestyring may suspend access without notice on suspicion of misuse. Start with reads and a few writes, then widen. ## What happens when Ordrestyring changes? - **12 h** between tests of the Ordrestyring reads - **$0** for a call to an Ordrestyring tool paused for repair When Ordrestyring moves a button or renames a field, the fix happens on our side and your prompts keep working. [status.cotlet.dev](https://status.cotlet.dev) watches the site, console and API every 3 minutes. ## Approvals, undo and mistakes 1. **Reads the order.** Checks the order, its status and the hours already booked. 2. **Prepares the change.** Planned time, or the hours to approve, listed by name. 3. **Waits for your OK.** The call shows up in your Cotlet console first. 4. **Reports the result.** Order, employee, times, and what could not be saved. | Action | Undo | |---|---| | Create an order | Cancel the order in Ordrestyring | | Log hours or book a material | Edit or delete the line on the order | | Plan an employee | Delete the planned time in the Day overview; the fitter has already seen it | | Approve hours | No, approved hours cannot be edited by anyone | | Create an invoice draft | Delete or edit the draft; nothing was sent | 2 of 12 tools ask first: plan_task and approve_hours. One puts a job in a fitter's app, the other locks hours for payroll. Drafts, hours, materials and new orders reach nobody, so they run at once. Switch the wait off per tool for a scheduled run. > Logged hours stay editable until they are sent for approval and approved. Check payroll hours before you approve them. MCP call: ``` { "name": "log_time", "arguments": { "date": "2026-10-30", "time_type": "Svendetime", "order_id": "10482", "from": "07:00", "to": "15:00", "description": "Fliser i bad" } } ``` REST: ``` curl -X POST https://cotlet.dev/api/v1/ordrestyring/times \ -H "Authorization: Bearer $COTLET_API_KEY" \ -H "Content-Type: application/json" \ -d '{"date":"2026-10-30","time_type":"Svendetime","order_id":"10482","from":"07:00","to":"15:00","description":"Fliser i bad"}' ``` Tool output: ``` { "entry_id": "h_88140", "date": "2026-10-30", "time_type": "Svendetime", "order_id": "10482", "from": "07:00", "to": "15:00", "hours": 8, "approval": "not_sent" } ``` Scripts and cron jobs reach the same tools over REST at `/api/v1/ordrestyring`, with the same key and price. Time approval fails on an account without the add-on, and a failed call costs nothing. The tools table lists the REST path of each tool. ## How much does the Ordrestyring MCP server cost? **About $22 a month** for a firm with 8 fitters, 3,740 credits. Your Ordrestyring licences are billed by Ordrestyring as before. | Job | Calls | Credits | |---|---|---| | Create an order for a new job | 2 × 20 | 400 | | Log hours and book materials after a job | 3 × 40 | 1,200 | | Plan next week's crew | 5 × 4 | 200 | | Approve hours before payroll | 2 × 4 | 80 | | Draft invoices for finished orders | 3 × 12 | 360 | | Cloud Browser, 30 days | | 1,500 | | Total | | 3,740 | - Free 7-day trial, no card - 10 credits per successful call, MCP or REST - 50 credits a day for the Cloud Browser - Uses a licence you already pay for The month is our example: 20 new orders, 40 jobs with hours and materials, 4 weekly plans and 12 invoice drafts. Ordrestyring lists 339 DKK per user a month for 1 to 10 users with a 12-month commitment (31 Oct 2026). Dollars at the $29 pack rate. ## Ordrestyring MCP server on GitHub or hosted: which to use | Option | What it does | Where it stops | |---|---|---| | [borgels/mcp-server-ordrestyring](https://github.com/borgels/mcp-server-ordrestyring) | TypeScript MCP server on the GraphQL API with tools for orders, customers, time, materials, planning and invoice drafts. Read-only by default. 0 stars, created 13 May 2026, last commit 31 Oct 2026. | Independent project. Needs an API token from Ordrestyring support and you run it. Writes need an opt-in and a prepared operation hash. | | [LasseRafn/php-ordrestyring](https://github.com/LasseRafn/php-ordrestyring) | PHP wrapper for the old REST v2 API. | Last commit 19 Apr 2023, the REST API is marked legacy. | | Ordrestyring's listed integrations | Accounting and payroll systems such as e-conomic, Dinero, Uniconta and Zenegy. | Fixed flows for invoices and hours, nothing for an agent. | | Your own GraphQL script | Anything the key allows. | Key from support, a developer to write and keep it, a hard cap of 60 requests a minute on every route. | If you already hold an API token and run Node.js, the GitHub server is a reasonable free start. Cotlet suits firms with no token and no developer: you sign in with your own user, we host and fix the tools, and n8n, Make and scripts reach the same ones over REST. ## Who runs Cotlet Take Group sp. z o.o. runs Cotlet. It is a software company registered in Poland, EU (VAT PL6342984273), working since 2019, founded by Bart Krawczyk (Co-founder, CTO) and Jake Slugocki (Co-founder, SEO, sales and marketing). Write to contact@cotlet.dev with questions about the Ordrestyring tools. ## Ordrestyring API and MCP: questions ### How do I get access? Create a free account at https://cotlet.dev, open Ordrestyring under Integrations in the console and log in to Ordrestyring in its Cloud Browser. The trial starts with your first app, no card asked. ### How do I connect Ordrestyring to ChatGPT or Claude? Sign up at cotlet.dev, log in to Ordrestyring once in its Cloud Browser and add Cotlet to ChatGPT or Claude, following the steps in your console. No API key is needed. ChatGPT and Claude then work in your Ordrestyring account through Cotlet, in their phone apps too. ### What can ChatGPT do in Ordrestyring? With Cotlet, ChatGPT, Claude and other AI agents handle jobs like these in Ordrestyring: log the day\; book materials after a job; create an order from a customer call. You ask in plain words, and anything that reaches other people waits for your OK first. ### How do I get an Ordrestyring API key? You ask Ordrestyring support, by chat in the system or by email, and they send the token (checked 31 Oct 2026). Cotlet needs no key: it works in your own login. ### Which Ordrestyring user does my agent need? Your own user. A basis user can log hours and book materials on orders assigned to them. Planning, hour approval and the customer list need the matching rights or an Admin, and approval also needs the Time approval add-on. ### Can the agent send an invoice? No. create_invoice_draft fetches hours and materials into an invoice draft and stops there. You or the owner review, approve and send it in Ordrestyring, which is also when the order moves to posted. ### Does Ordrestyring have a free trial? Yes, 14 days on its own site (checked 31 Oct 2026). After it the standard licence is 339 DKK per user a month for 1 to 10 users with a 12-month commitment. Cotlet adds no Ordrestyring fee. ### Is the MCP server different from the REST API? Only the door is different. Both expose the same 12 tools, inputs and answers, with one API key and one price. Agents use MCP; scripts and HTTP steps use REST. ### Is Cotlet affiliated with Ordrestyring? No. Cotlet is independent and not affiliated with Ordrestyring ApS or Aceve. ### Can I use the Ordrestyring API without an AI agent? Yes. Call Cotlet's REST API from a script or an HTTP step in n8n, Make or Zapier with your Cotlet key. MCP is the alternative for AI agents; you do not need to connect an agent to use REST. --- Give your AI agents your signed-in browser. **Product:** [Integrations](https://cotlet.dev/integrations.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.