Data connectors
A data connector gives an agent read access to an external system. You create it once, Studio keeps the credentials in AWS Secrets Manager in your deployment's account, and you attach it to an agent in its Configure dialog; until then nothing reads from it.
The five types
| Type as shown | What the agent gets | Use it when | Page |
|---|---|---|---|
| SQL Database | Read-only queries against PostgreSQL or MySQL with a username and password | The data is in a relational database reachable over TLS | SQL connectors |
| Snowflake | Read access as a Snowflake service user, with a programmatic access token or a key pair | The data is in Snowflake | Snowflake connector |
| REST API | Calls to an HTTP API described by an OpenAPI specification, credentials as headers or query parameters | The system exposes a documented API | REST / OpenAPI connector |
| MCP Server | Tool calls against a Model Context Protocol (MCP) server over streamable HTTP | The system publishes MCP tools | MCP connector |
| AWS | An IAM role in an AWS account you own, assumed with a Studio-generated External ID | Agents need S3 or other AWS services, or a workflow reads files from a bucket | AWS connector |
SQL connectors are read-only at run time; the SQL page gives the loader pattern for processes that must write.
Steps
Open Data Connectors from the dock, click Create Connector, fill Connector Name, Description and Connector Guide (writing the guide), then follow the row for your type above. Once saved, add it to an agent in Configure (Agents: configure and activate).
What you should see
The connector appears in the list (Connector ID, Connector Name with its version, Connector Type, Status, Description, Updated At; 20 rows per page) as "(v1)", Active. Click the row to open it (Connector versions, Test Connection and guides).
| Status | Meaning |
|---|---|
| Active | Agents can use it. Saving sets this status. |
| Needs Attention | Set by Studio on a copy pulled from a Library that cannot connect yet (for example an AWS role that does not trust your account); the detail page shows the reason. |
| Inactive | Disabled. Saving an update makes it Active again. |
Notes
- Limits: name 80 characters; description 1,000; guide counted in bytes, with "Large guides cost more per turn." above 50,000 characters; 12 credential rows (REST API, MCP Server); 256 connectors per user in a standard deployment, where Create Connector is disabled at the cap ("You've reached the limit of 256 data connectors."). A governed deployment lists everyone's connectors, so the server, not the form, refuses at the cap.
- Credentials are entered once, never shown again and never placed in a prompt; each run receives them inside the agent's execution environment. Every save creates a new immutable version; an agent pins a version until you move it.
- Test Connection saves nothing; a cross shows the service's reason. Create Connector (v1) stays disabled while a required field is empty, a counter is over its limit, or the type's gate is unmet (SQL and MCP need the enrich step and Accept & Use This Guide after a passing test).
- "Error loading connectors": reload. A pulled copy's banner reads "This connector needs attention before it can be used. Update its configuration and credentials below."