Choose between the interface, import, API and MCP
Choose the connection according to the action you want to perform. Editing in Boldo, importing a file, running a synchronization and connecting an AI client have different controls.
Match the tool to the task
| Your goal | Use | What controls the result |
|---|---|---|
| Correct a few assets or review a suggestion | Boldo's interface | Your permissions, selected context and the action's save or confirmation step. |
| Load a spreadsheet or reconcile a file with existing assets | File import | Matching keys, mapped columns and the preview you validate. |
| Regularly read Boldo from another system | API reads | An API key, pagination, filters and the synchronization you implement. |
| Create or update data from another system | API writes | The key's effective permissions and the exact request you send. |
| Let an external AI client read, suggest or change data | MCP | Your MCP level, business permissions, organization settings and OAuth consent. |
| Use your own model service in Boldo's assistant | Self-hosted AI endpoint | Organization AI settings, service compatibility and model capabilities. |
The API exchanges structured data with your program. Your program schedules the synchronization and handles failures. Boldo does not provide a universal synchronization schedule on the API key screen.
MCP gives a compatible external client read tools and, when authorized, tools to submit suggestions or write directly. Suggestions await review in Boldo. Direct writes do not create an AI proposal card in Boldo’s chat. Configuring a model endpoint instead changes the provider used inside Boldo; it does not connect an external client's tools.
Prepare the connection
- Identify the target organization and whether you need real data or a scenario.
- Decide whether you only need to read or also need to write.
- Check the plan and the permissions required by the chosen connection.
- Start with a limited read, using a known asset or type.
- Check the returned organization, identifiers and visible fields before expanding the integration.
- For writes, test a small, identifiable set and read back the saved result.
An API key belongs to one organization. MCP uses the organization selected during OAuth consent. Being signed into Boldo in a browser does not automatically give either connection access.
Plan updates and access
Use stable asset identifiers or unique-key properties when matching records across systems. Names alone are not reliable identifiers. Decide which system owns each field to avoid two integrations repeatedly overwriting each other's changes.
API writes take effect when the request succeeds; there is no additional Boldo confirmation dialog. An import instead has its own preview and validation procedure. A network timeout does not establish whether an API write was saved: read the current state before repeating it.
For regular integration access, document who owns the connection and how to rotate or revoke its credentials. API keys and MCP consent use different mechanisms; a v1 API key is not a substitute for MCP OAuth.
If data is absent, check permissions and context before treating it as deleted. For a reliable external copy, account for archives, relationships and quality metadata as explained in reading and synchronization.