Skip to main content
Use Access when a dashboard needs data from a business service or local application. Both d0 and Access should be running on the same Mac for this setup.
1

Create a dedicated profile in Access

Create an agent profile for d0. Grant only the connections and operations your dashboards require. A dedicated profile makes the scope and audit activity easier to identify.
2

Enable local MCP HTTP

In Access, enable MCP HTTP on this Mac and create an MCP credential for the dedicated profile. Copy the endpoint shown by Access.
3

Connect d0

Open Gatetrix Connection in d0 and enter the local Access MCP URL and credential. This connection uses a loopback endpoint on the same Mac. The host holds the credential; the dashboard does not need it in its files.
4

Declare the dashboard's permissions

Ask your builder agent to declare the required tools in the manifest. When using connector_operation_call, also declare the exact connector and operation IDs. Friendly labels help you review the request; the IDs identify the actual operations.
5

Review and verify

Refresh d0, review the updated version, and trust it if its scope matches your intent. Run one bounded read and inspect the result. If Access requests approval, decide in Access and retrieve the saved result.

​
Both sets of permissions matter

A dashboard needs the capability declared in its trusted manifest and the corresponding permission in Access. Trusting a dashboard cannot expand an Access profile’s grants. The bundled Reminders Insights sample is another starting point. It uses read-only Apple Reminders tools through Access; approve the intended reminder lists and grant the tools the sample needs. If a call is denied, check the current trust state, manifest IDs, Access profile grants, and approval requirements. Avoid broadening all permissions to diagnose a single missing operation.