> ## Documentation Index
> Fetch the complete documentation index at: https://docs.gatetrix.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# Set up a connector with an agent

> Delegate connection setup in Gatetrix Access while keeping resource scope, credential entry, sign-in, and tool review under your control.

An agent can prepare a connection from a service's API documentation and the
capabilities exposed by your installed Access version. You supply the intended
outcome and scope, enter credentials in Access, and make required review decisions.

<Info>
  **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](/access/connection-types) and [Supported protocols](/access/protocols).
</Info>

## Before you start

* [Connect the agent to Access](/access/quickstart).
* 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

<Steps>
  <Step title="Select the profile">
    In **Connectors**, select the agent profile that should own the connection.
    Find **Set up a connection with your agent**.
  </Step>

  <Step title="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.
  </Step>

  <Step title="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.
  </Step>

  <Step title="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.
  </Step>

  <Step title="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.
  </Step>
</Steps>

## Prompt for your agent

Use this alongside the setup prompt copied from Access. Replace the bracketed
parts with your intended scope.

```text theme={null}
Set up [service] in Gatetrix Access for [purpose].
Allow only [operations] on [specific projects, folders, accounts, or resources].
Start with read access. Do not add write or delete access unless I request it.

Discover the available Gatetrix tools. Read
configuration_connection_capabilities and configuration_mode_status first.
Use the installed schemas and templates and the service's official API docs.
If the requested restriction cannot be enforced, explain that before proceeding.

Prepare the connection within the selected profile's Configuration Mode.
Ask me to enter credentials, complete sign-in, and review tools in Access.
Do not ask me to paste secrets into this conversation.

Run a bounded verification after setup and report the resulting scope,
anything still waiting on me, and any check that could not be completed.
If an action requires approval, use the saved approval result afterward.
Do not repeat a write whose outcome is uncertain.
```

## 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.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.