Connections tailored to your task. Access does not depend on a large catalog
of predefined API integrations. An agent can read the service’s documentation
and prepare the operations and data scope you need. You review the result,
supply credentials, and verify that the requested restriction is enforceable.
See Connection types and Supported protocols.
Before you start
- Connect the agent to Access.
- Choose the service and the exact data or resources it should access.
- Decide which operations it needs: for example, read selected projects or create drafts in one mailbox.
- Have access to the service’s account settings if an API key or OAuth registration is required. Provider registration can require steps outside Gatetrix.
Set up the connection
1
Select the profile
In Connectors, select the agent profile that should own the connection.
Find Set up a connection with your agent.
2
Enable Configuration Mode
Choose the setup duration and permissions in Configuration Mode, then
enable it for this profile. Start with the time-limited option.
Copy prompt copies instructions; it does not enable or extend access.
3
Give the agent the task
Copy Access’s setup prompt to the connected agent and add the service,
operations, and resource scope you want. The agent should discover installed
capabilities and use the provider’s official documentation.
4
Complete the owner steps
Enter API keys, passwords, or client secrets in Access when prompted. Complete
provider sign-in yourself. For an upstream MCP server, discover and review its
tools, then explicitly enable the operations the profile should use.
5
Verify the result and close setup access
Ask for one bounded read within the agreed scope. Check the configuration and
grants, and verify that excluded resources remain unavailable using a safe
check appropriate to the connector. Turn off Configuration Mode when finished.
Ordinary permitted operations can continue after setup access closes.
Prompt for your agent
Use this alongside the setup prompt copied from Access. Replace the bracketed parts with your intended scope.Technical notes for agents
configuration_connection_capabilities describes the installed connection
builders, authentication options, schemas, and templates. These are preferable
to a copied configuration that may be outdated. Depending on the installed
version, builders include HTTP services, upstream MCP servers, and PostgreSQL.
Setup permission and runtime permission are separate. A successful configuration
write does not prove that credentials, sign-in, discovery, or tool review are
complete. Report the remaining state explicitly.
If a tool is absent, refresh discovery and check the app version and profile
permissions. Do not substitute a broader connection or bypass owner review.