Enable and authenticate
- Install Access and create an agent profile and credential.
- Open Access Channels → CLI and enable Allow CLI commands.
- Supply the credential through
GATETRIX_MCP_TOKENorGATETRIX_ACCESS_TOKENin the process environment. Use your local secret-management mechanism; do not put a real token in chat, a repository, or command history.
gatetrix-cli; no separate Node installation is
needed. With the app in its standard Applications location, inspect its help:
PATH and the token is
already set in your environment.
Inspect the profile and read a file
root list in place of ROOT_ID. Paths are relative to
that granted root:
Call a saved connector operation
Replace the IDs and input with a permitted operation’s actual contract:approval_required, the operation has not executed.
Decide the request in Access and inspect its saved result through the app or
MCP approval tools. Do not repeat a write to retrieve an approved result.
Delegate connection setup
setup mcp or setup postgresql for those connection types. CLI definition
files use camelCase outer fields such as connectorId and expectedUpdatedAt;
nested HTTP and manifest fields use snake_case. Keep credentials out of the files.
Follow the connector setup process for sign-in, review,
scope verification, and closing setup access. CLI cannot create credentials,
change inbound listeners, or administer profile grants.
Troubleshooting
Check the token, profile grants, and CLI switch when a command is denied. The MCP switches do not control the CLI, and the CLI switch does not control MCP. Usegatetrix-cli audit list to inspect permitted audit events, or Audit Log
in the Mac app for the owner’s view.