Summary
RO App (formerly RemOnline) repair-shop and service CRM, Public API v2: orders with statuses and comments, clients, inquiries (leads), products and warehouses, invoices, finance accounts with their transactions, tasks and employees. API key.
Guided setup
Connect RO App to Microsoft Copilot in 2 minutes
Start a free trial on AnythingMCP Cloud, connect RO App in the guided setup, then add your MCP URL to Microsoft Copilot. No code and no server to run.
No credit card · 7-day trial · Self-host alternative available
Try asking
Example prompts for RO App
Click any prompt to copy it. Paste into Claude, ChatGPT, Cursor, Gemini, Copilot or OpenClaw to run it against this connector.
Claude is AI and can make mistakes. Please double-check responses.
💡 No install? Use cloud.anythingmcp.com directly. Sign in, click Connectors → RO App, paste your credentials, mint an MCP API key and you're done. No Docker, no
git clone, no local server.
RO App + Microsoft Copilot
RO App (formerly RemOnline) repair-shop and service CRM, Public API v2: orders with statuses and comments, clients, inquiries (leads), products and warehouses, invoices, finance accounts with their transactions, tasks and employees. API key.
Prerequisites
See the full setup instructions baked into the connector (visible in the in-app store when you select the connector). The required environment variables for this connector are:
RO_APP_API_KEY
Step 1 — Get credentials
Setting up takes about 2 minutes.
- In RO App open Settings, API (https://web.roapp.io/settings/api).
- Copy the API key into
RO_APP_API_KEY. It is tied to your user profile and can be regenerated on the same page.
The key is sent as Authorization: Bearer. There is no token exchange in API v2. A wrong key answers 403 with the message Invalid token.
Where to start: ro_app_get_company checks the key. ro_app_list_orders lists repair orders; filter by status ids from ro_app_list_order_statuses. ro_app_get_order and ro_app_list_order_items show one order with its parts and services.
Orders: ro_app_list_orders, ro_app_get_order, ro_app_list_order_items, ro_app_create_order, ro_app_update_order, ro_app_update_order_status, ro_app_add_order_comment, with the reference lists ro_app_list_order_statuses and ro_app_list_order_types. A new order needs a location (ro_app_list_locations), an order type and a client.
Clients: a client is a person or an organization. People: ro_app_list_people, ro_app_get_person, ro_app_create_person. Organizations: ro_app_list_organizations, ro_app_get_organization, ro_app_create_organization.
Leads: RO App calls them inquiries. ro_app_list_inquiries, ro_app_get_inquiry, ro_app_create_inquiry, ro_app_update_inquiry_status, with ro_app_list_inquiry_statuses and ro_app_list_inquiry_types.
Inventory: ro_app_list_products and ro_app_get_product read the product catalogue, ro_app_list_warehouses the warehouses. API v2 documents no call for the stock quantity per warehouse, so stock levels are not available here.
Invoices and payments (read only): ro_app_list_invoices, ro_app_get_invoice, ro_app_list_invoice_items; ro_app_list_finance_accounts and ro_app_list_account_transactions show cash boxes, bank accounts and the payments booked on them. The connector creates no payments, transfers or refunds.
Tasks and staff: ro_app_list_tasks, ro_app_get_task, ro_app_create_task; ro_app_list_employees gives the employee ids used for managers and assignees.
Paging and filters: lists return up to 50 rows per page with count (the total); ask for the next page with page. Most filters take lists of ids. Date filters take one or two ISO 8601 date-times: one is the start, two are a range.
Limits: 3 requests per second; more answers 429. Nothing is deleted by this connector.
Step 2 — Install the adapter
curl -fsSL https://raw.githubusercontent.com/HelpCode-ai/anythingmcp/main/docker-compose.quickstart.yml -o docker-compose.yml
printf 'JWT_SECRET=%s\nENCRYPTION_KEY=%s\n' "$(openssl rand -hex 32)" "$(openssl rand -hex 32)" > .env
docker compose up -d
Step 3 — Add the connector in Microsoft Copilot
Your server URL: in AnythingMCP, open MCP Servers → the server this connector is on, and copy its URL (
https://cloud.anythingmcp.com/mcp/…). Use it wherever this guide showsYOUR_SERVER_ID.
Microsoft Copilot uses MCP servers through agents built in Copilot Studio: you add AnythingMCP to an agent as a tool, then publish the agent to Microsoft 365 Copilot and Teams. Copilot Studio connects from Microsoft's cloud over Streamable HTTP, which AnythingMCP supports.
- In Copilot Studio, open your agent (or create one), go to Tools and choose Add a tool → New tool → Model Context Protocol.
- Enter a Server name (for example
AnythingMCP), a Server description that says what the connector does, and the Server URLhttps://cloud.anythingmcp.com/mcp/YOUR_SERVER_ID. Copilot Studio uses the description to decide when to call the server. - Under authentication, choose API key, set Type to Header and the header name to
X-API-Key, then select Create. - In Add tool, choose Create a new connection, paste an MCP API key from AnythingMCP (MCP Servers → your server → API keys) and select Add to agent.
- Try it in the agent's Test pane: ask for something that needs the
RO Apptools. - Select Publish, then Channels → Microsoft 365 and Microsoft Teams, keep Make agent available in Microsoft Copilot selected and choose Add channel. See agent in Teams installs it for you; in Microsoft 365 Copilot, type @ and pick the agent.
Prefer per-user sign-in? Choose OAuth 2.0 → Dynamic discovery instead of an API key: each user then signs in to AnythingMCP the first time the agent calls it.
Self-hosting? Use your instance's public HTTPS address instead of https://cloud.anythingmcp.com. Copilot Studio connects from Microsoft's cloud, so localhost does not work.
Available tools
| Tool | What it does |
|---|---|
ro_app_get_company | Read the information RO App holds about the company account behind the API key. Use it to check that the key works. Read-only |
ro_app_list_locations | List the locations (branches, workshops) of the company: id, name, address and whether archived. The id is the branch_id of orders… |
ro_app_list_employees | List the employees of the company: id, name, email, phone, position and group. The id is what managers, assignees and task authors refer… |
ro_app_list_orders | List repair and service orders: id, document number, status, type, location, client, asset, manager and assignee, problem description… |
ro_app_get_order | Read one order with all its details: status, type, client and payer, asset, manager and assignee, problem description, notes, conclusion… |
ro_app_list_order_items | List the products and services on an order: each item with its name, quantity, price, cost, discount, tax and warranty. Read-only |
ro_app_create_order | Create a repair or service order for a client at a location. Fetch the ids first: ro_app_list_locations (branch_id)… |
ro_app_update_order | Update an order: client, asset, manager, assignee, schedule, due date, problem description, notes or custom fields. Only the fields given… |
ro_app_update_order_status | Move an order to another status, with an optional comment. Depending on the status rules of the account this can notify the client or close… |
ro_app_add_order_comment | Add a comment to the event feed of an order. A private comment is visible to employees only |
ro_app_list_order_statuses | List every status an order can have: id, name, colour and group (new, in progress, ready, closed and others). Read-only |
ro_app_list_order_types | List the order types of the account (for example repair, sale, maintenance) with their ids. An order needs one. Read-only |
ro_app_list_people | List clients that are people: id, first and last name, email, phones, address, tags, manager, discount and whether a supplier. Returns the… |
ro_app_get_person | Read one person: names, birthday, email, phones, addresses, tags, manager, discount code, tax number and custom fields. Read-only |
ro_app_create_person | Create a client that is a person, with a first name and optionally last name, email, phones, address and tags. Returns the person with its… |
ro_app_list_organizations | List clients that are organizations (companies): id, name, email, phones, address, tags, manager and whether a supplier. Returns the rows… |
ro_app_get_organization | Read one organization: name, email, phones, addresses, tags, manager, tax and registration numbers and custom fields. Read-only |
ro_app_create_organization | Create a client that is an organization (company), with a name and optionally email, phones, address, tax numbers and tags. Returns the… |
ro_app_list_inquiries | List inquiries (leads): id, document number, status, type, location, contact name and phone, client, manager, comment, due date and created… |
ro_app_get_inquiry | Read one inquiry (lead): status, type, contact name, phone and email, client, manager, comment, notes, address, due date and custom fields.… |
ro_app_create_inquiry | Create an inquiry (lead) of a given type, with the contact name and phone or an existing client, a comment and an optional due date.… |
ro_app_update_inquiry_status | Move an inquiry (lead) to another status, with an optional comment, for example to mark it as won or lost |
ro_app_list_inquiry_statuses | List every status an inquiry (lead) can have, with id, name and group. Read-only, no parameters |
ro_app_list_inquiry_types | List the inquiry (lead) types of the account with their ids. An inquiry needs one. Read-only, no parameters |
ro_app_list_products | List the products (parts and goods) of the catalogue: id, title, SKU, internal code, barcodes, manufacturer part number, category, unit of… |
ro_app_get_product | Read one product of the catalogue: title, SKU, code, barcodes, category, unit of measure, warranty, prices and custom fields. Read-only |
ro_app_list_warehouses | List the warehouses: id, name, type and the location they belong to. Read-only |
ro_app_list_invoices | List invoices: id, document number, status, client and payer, legal entity, payment method, totals, issue date and due date, and the order… |
ro_app_get_invoice | Read one invoice: number, status, client and payer, legal entity, payment method, totals with tax and discount, issue and due dates and… |
ro_app_list_invoice_items | List the products and services on an invoice: each item with name, quantity, price, discount and tax. Read-only |
ro_app_list_finance_accounts | List the finance accounts (cash boxes and bank accounts) of the company with their ids, titles and payment method types. Read-only; this… |
ro_app_list_account_transactions | List the payments booked on one finance account: direction (income or expense), amount, cash flow category, description, the employee who… |
ro_app_list_tasks | List tasks: id, title, description, priority, status, due date, author, assignees and the object they are linked to. Returns the rows of… |
ro_app_get_task | Read one task: title, description, priority, status, due date, author, assignees, the linked object and its comments. Read-only |
ro_app_create_task | Create a task with a title and a due date, optionally with a description, priority, assignees and a link to an order, inquiry, invoice… |
Example prompts
- "Which repair orders are still waiting for parts, and which technician has them?"
- "Show order 10482 with its parts, services and comments."
- "Create a lead for Anna Petrova, iPhone 14 screen replacement, from the website."
- "Move order 10482 to Ready for pickup and add the comment: customer called, will come Friday."
- "Which invoices from last month are still unpaid?"
FAQ
Where does the API key come from? In RO App open Settings, API and copy the API key into RO_APP_API_KEY. It belongs to your user profile and can be regenerated on the same page. RO App was formerly called RemOnline.
What does it cover? Repair orders with statuses, items and comments, clients as people and organizations, inquiries (leads), products and warehouses, invoices, finance accounts with their transactions, tasks and employees. Invoices and payments are read-only, and the connector creates no payments, transfers or refunds. Stock levels per warehouse are not available, because API v2 documents no call for them.
Does anything install switched off? No. Every tool is on, and nothing is deleted by this connector; writes create or update orders, clients, leads and tasks, so the AI shows you each one and waits for a yes.
Which Copilot is this for? Microsoft 365 Copilot at work, through agents built in Copilot Studio. The Microsoft Copilot app for personal accounts has no option to add your own MCP server.
What do I need? A work account with access to Copilot Studio (a license or a trial) to build the agent. People who use it in Microsoft 365 Copilot or Teams need access to the agent: share it with them, or ask an admin to publish it to the organization. If your organization applies data policies to Power Platform connectors, they cover MCP servers too.
The agent doesn't call the tools. Check that the header name is exactly X-API-Key and that the key belongs to the same MCP server as the URL, and make the server description specific: Copilot Studio uses it to decide when to call the server. Publish the agent again after each change; in an open chat, type "start over" to get the new version.
Next steps
Was this guide helpful?