Connect an AI assistant with the correct MCP
Research, synthetic trial and authenticated merchant MCPs have different permissions. Installation is not business activation.
Instructions reviewed
Current workspace availability, quotes and permissions apply. The review date is not a live provider status. Reading help makes no checks or payments.
Before you start
- Choose research, synthetic trial or merchant work, and a compatible AI client.
Follow these steps
For research, use the public developer kit; it cannot read merchant records. Use quickstart_mcp.py for account-free synthetic trials.
You should see： Results are labelled research or synthetic.
For merchant work, install the documented client and dependencies. Choose merchant_mcp.py for sandbox or production_mcp.py for eligible live products, using a private environment key.
You should see： Tools appear; start with capability reads, without automatic funding or unapproved costs.
Cross-check the merchant and result ID in the console. Live writes retain all enrollment, funding, quote and consent gates.
You should see： MCP and web refer to the same merchant records; tool availability is not provider availability.
Completion check
You know which MCP, account and potentially paid actions you are using.
If you get stuck
- No tools: check stdio support, Python absolute path and dependencies. Public research MCP is not remote merchant OAuth.
Next steps and related guides
Unclear step? Report its location
Include the guide, step, visible message and expected outcome. Redact screenshots. Do not include codes, keys, identity documents, full accounts or customer records.
open@gridzen.ai