Overview
Dashboardly AI Pilot is an invitation-only connection for approved synthetic testing. It helps you compare offer assumptions and prepare a review from text you supply. It is separate from Dashboardly Profit and is not a public Claude directory listing. Access remains limited to the shops approved for your connection.
Before you connect
Use the Claude account approved for your Pilot test and a Dashboardly account with access to the approved synthetic shop. This guide does not expand your access. A connector configured under another Claude account does not prove that your current account has it. Claude account limits and organization settings can affect availability.
Use fictional or already-redacted material. Leave out buyer names, email addresses, phone numbers, postal addresses, tracking details, passwords, access credentials and payment-card information. The Pilot checks some obvious contact patterns, but it is not a complete personal-information remover. Continue using synthetic material while the wider Pilot privacy and release review is unfinished.
Connect in Claude
Open Customize > Connectors in Claude. For an individual account, choose + Add > Add custom connector. In a Team or Enterprise organization, ask an authorized organization owner to make the connector available first. Check the current Claude help link below if the menu labels differ.
Name the connection Dashboardly AI Pilot and enter https://mcp.dashboardly.io/mcp/dashboardly as the server address. Keep the full /mcp/dashboardly path. Choose account sign-in and automatic client registration where offered. Do not paste a Dashboardly password or access credential into a chat.
Use the Dashboardly sign-in window opened by that connector, checking the site address before signing in. It may open in your system browser even when you started in Claude desktop. Review consent and select only the approved synthetic shop with Reporting & reconciliation access. Do not enable customer contact, address or tracking access to troubleshoot a problem.
Return to Claude and check that the connection completed. Enable it for the conversation from the + menu under Connectors if needed. Ask the Pilot for Connection context and Available shops, then check that the returned shop selection matches your authorization. A saved connector name or an unfinished sign-in page does not establish a working connection.
The four Pilot tools
Connection context describes the workflows available to the current connection. Available shops lists the shops authorized for it. Follow a returned next cursor when you need the complete list; one page may be incomplete.
Evaluate offer economics compares manual prices, discounts and cost assumptions. Prepare product-page evidence organizes supplied video-transcript and product-page text for a draft review. These tools are read-only: they do not change budgets, product costs, inventory, orders or live page content, and they do not buy anything or move money.
Compare an offer
Tell Claude the currency, quantity, unit price, seller discount and costs for each scenario. State whether an amount applies per unit or to the whole scenario when asked. Keep a confirmed zero distinct from an unknown cost. Ask Claude to preserve the returned assumptions, missing inputs and warnings.
Example: “Use Dashboardly AI Pilot to compare a fictional one-unit USD offer with a unit price of 100, a total seller discount of 10 and product cost of 30. Ask me for the other required costs instead of assuming they are zero. Preserve unavailable results and explain which inputs are missing.”
A partial result is expected when a required cost is unknown. Missing profit and margin results stay unavailable rather than becoming zero. Money and margins can use different precision, so read the tool’s returned amounts instead of reconstructing a rounded total from the assistant’s explanation. These are modeled scenarios, not the profit your shop actually earned.
The Pilot currently accepts manual scenarios. It does not fill an offer from a connected product, report actual weekly profit or rank products and creators by realized margin. Use Dashboardly’s reporting views or the separate Profit connection for supported financial reporting.
Prepare a product-page review
Supply a spoken video transcript and product-page copy for a full comparison. You can add captions, selected review excerpts, funnel notes or product facts, clearly labeling each source. Use material you have the right to share. For a test, use fictional or already-redacted excerpts.
Ask Claude to compare the promise, product details and next step, preserve conflicting facts and list missing evidence before drafting recommendations. A caption is not a spoken transcript. Missing page text does not prove that the live page lacks a claim. Supplied reviews do not establish representative sentiment or verified testimonials.
The tool prepares supplied text. It does not visit URLs, watch videos, upload media, verify connected product facts, measure visitors or purchases, or prove a conversion increase. Claude’s suggestions are drafts to review before use.
Fix duplicate evidence identifiers
Each evidence item in a request needs its own evidenceId. If two items reuse an identifier, the Pilot refuses the request and can identify the safe field evidence[1].evidenceId with a uniqueness correction. Assign a different evidenceId to the second item and update any references to that item in the same request. Refer only to identifiers included in that request.
The field reference identifies where to correct the input; it should not repeat your supplied excerpt or identifier value. After correcting the identifier, retry the corrected request. If you receive only a general error, keep the safe request reference and ask support which input needs correction. Do not send the full private prompt to troubleshoot it.
Troubleshoot the connection
Pilot missing: check the account and organization shown in Claude desktop, then its Connectors list and the conversation’s enabled tools. Do not sign out of another working account or create duplicate connectors as a first step. If the intended account still has no Pilot entry, contact Dashboardly support.
Sign-in unfinished or expired: return to the window started by the same connector. If it expired, begin a fresh Connect attempt from that connector with the same approved shop and reporting access. A new authorization is a permission decision, not an ordinary read-only health check.
Access unavailable: check your current Dashboardly account and approved shop access. Removed permissions can stop a request. Do not broaden access, change credentials or reconnect another assistant to bypass the restriction. A healthy Dashboardly service does not establish that your Claude session is connected.
Claude usage limit: wait for the reset Claude shows or contact Claude support if it remains unexpectedly. A healthy Dashboardly server does not remove a Claude account limit. Do not move the test into an unrelated account to evade the approved scope.
Contact details detected: remove them yourself before retrying. Input or result too large: reduce the excerpts or number of scenarios. If a tool panel is truncated, say which part was visible rather than treating it as a complete archived result. Unknown cost: provide it when known; do not substitute zero just to obtain a complete result.
Privacy and access control
Use only the material needed for the test. Claude receives the tool inputs and results used in your conversation, and its account and data controls also apply. Read Dashboardly’s Privacy Policy and Data Deletion Policy. This guide does not promise a fixed log-retention period, immediate backup erasure or that all request content is excluded from every operational system.
Manage Dashboardly connections in Settings > API Keys > Connected Apps. Revoking a Dashboardly connection is different from removing a connector’s local entry in Claude. Revocation stops authorized access; it is not a request to erase every retained record. Preserve a working grant during an ordinary read-only check.
Get help
Contact hello@dashboardly.io with the connector name, the stage that failed, a safe error code or field reference, the request reference and time if shown. Do not send passwords, access credentials, buyer information, raw evidence excerpts or a full private conversation.
Related guidance
Claude custom connector setup: https://support.claude.com/en/articles/11175166-get-started-with-custom-connectors-using-remote-mcp
Dashboardly Profit and API-key connections: https://help.dashboardly.io/features/connecting-ai-assistants-to-dashboardly
Dashboardly Privacy Policy: https://www.dashboardly.io/privacy-policy