Skip to content

MCP Use Cases

These examples show common work an AI client can do in CxReports through the MCP server. Each one gives the goal and the prompts to send in order. Replace the workspace, database, table and report names with your own.

Prompts that ask the client to check an exported PDF work only if the client can download files. Otherwise, open the export link and check it yourself.

Reports

Create a report from a description

Describe the document, the data behind it, and the template and theme to use. Ask to see the data before the client lays out the page:

In the Sales workspace, create a Customer Statement report with our Statement template and the Sales database. It has a Customer parameter and lists the customer's open invoices with their dates, due dates and amounts, and the total due. Run the query and show me sample rows before you build the page.

Export it to PDF for customers 1001 and 1002, and check that the total matches the sum of the invoices on each.

Rebuild a document from a PDF or image

If your client accepts files, attach a PDF, scan or screenshot of a document you already send, and ask for a report that looks the same. Name the database, so the client binds the fields to your data instead of copying the values from the file:

Rebuild the attached invoice as an Invoice report in the Sales workspace, with an Invoice parameter, using the Invoices and InvoiceItems tables in the Sales database. Keep the layout, fonts and colors as close as you can. Before you build, tell me which fields in the document you matched to which columns, and anything you could not find.

Export invoice 1001 so I can compare it with the original.

Move reports from other reporting software

Give the client what you have from the old system: the report definition, if the old tool saves it as text (for example an RDL or XML file), the SQL queries behind it and a PDF of its output. A client running on your computer, such as Claude Code, can read these from a folder. Rebuild one report at a time, and check the figures against the old output:

The files in the legacy/monthly-sales folder are the definition, the queries and a sample PDF of our Monthly Sales report. Rebuild it in the Sales workspace with the same parameters, grouping and subtotals, using the Sales database. List anything you could not carry over.

Export it for the period of the sample PDF and check that every subtotal and the grand total match it.

Change many reports at once

The client can find and change content across all reports in a workspace, for example after a database change or a rebranding. It reads each report in turn, so in a large workspace name the reports to check:

The CustomerName column in the Customers table was renamed to Name. Find every data source in the Sales workspace that uses it, show me the list, and update them once I confirm.

Switch every report in the Sales workspace that uses the Classic theme to the Corporate theme.

Generate and deliver a document for each record

A report job generates a document for every record in a list, such as one statement per customer, and delivers it. Email delivery needs SMTP set up for the workspace. Test the job with one run, with the documents held for review, before you schedule it:

Create a report job in the Sales workspace that generates the Customer Statement for every customer in the Customers table with open invoices, and emails it to the address in the Email column. Hold the documents for review before they are sent.

Run the job once now, and tell me how many statements were generated and for which customers.

Check a few of the documents in the job's run in CxReports, and select Deliver to send the held ones (see Hold-for-review). Then let the job run on its own:

Run the job automatically on the first day of every month at 07:00, and tell me when it runs next.

While Hold deliveries for review is on, every scheduled run waits for you to deliver it. Ask the client to turn it off once you trust the results.

Translate a report

The client moves the fixed text of a report into a dictionary and adds the translations:

Translate all the fixed text on the Customer Statement report into German and French, then export it for customer 1001 in German.

Portals

Build a dashboard page

Describe what the page should show and where the data comes from. The client adds the widgets and the data source to a draft of the portal:

Add a Revenue page to the Sales portal with the revenue, order count and average order value as key figures, revenue by month as a column chart, and the top 10 customers in a table, from the Orders table in the Sales database.

Add a period filter at the top and connect it to every widget on the page.

Check the page in the designer, and publish the portal once the draft is ready, in the designer or by asking the client. See Versions and Publishing.

Brand a portal

The client can create a portal theme from your brand colors and set it on the portal's design, which also holds the page layouts around every page:

Create a portal theme in the Sales workspace with #0B3D91 as the primary color and #F2A900 for charts, and use it in the design of the Sales portal. Put the company logo from the workspace files at the top of the design's page layout.

The theme and logo go into a draft of the design, so the portal keeps its look until the design is published. Check the design in the designer, then publish the design and the portal, in the designer or by asking the client. See Versions and Publishing.

Tips

These practices make the results more accurate and easier to check:

  • Give the client your rules once. Put what the client needs in every session, such as what your tables hold, how revenue is calculated and which date an order counts on, in the client's own instructions or skills.
  • Check the data before the layout. Ask the client to run each data source and show sample rows before it puts the data on a page.
  • Keep figures tied to the data. Ask the client to take totals, counts and labels such as "Overdue" from the data sources, not to type the values it saw while building onto the page. Then they stay right for every parameter value.
  • Export with several parameter values. Some errors show only in an export, for example a parameter value compared with a number column. Name the values in the prompt.
  • Build in steps. A full report takes dozens of tool calls, and a single very large change is refused. Ask for one page or section at a time.
  • Let the client read its exports. With the token set for the client, it can download the PDF and check the figures and layout itself.
  • Ask how a figure was calculated before you rely on it.