Connectors

Documentation Index

Fetch the complete documentation index at: https://docs.major.build/llms.txt

Use this file to discover all available pages before exploring further.

Connectors are the databases, APIs, and storage services your apps connect to. Major manages credentials securely so you never need to handle secrets in your code.

​

How connectors work

• Secure Flow: Your app connects to the Major API, which proxies requests to your actual connectors.
• Authentication: Powered by a MAJOR_JWT_TOKEN issued to your session. This token contains your user scopes, ensuring the client can only access what you’re permitted to access.
• Generated Clients: Major generates resource clients for you. You’ll find one per resource in src/clients/.

​

Setting up a connector

1. Navigate to Organization Settings > Connectors
2. Click Add Connector and select the type
3. Configure the connection details and credentials
4. Attach the connector to your app via the web editor or major resource manage

​

Per-environment configuration

When editing a connector, you can configure each environment independently. This lets you use different credentials or endpoints for staging and production. You can also enable shared configuration for a resource, which uses a single configuration from the default environment across all environments instead of per-environment configs. When enabled, non-default environment tabs are locked with an explanatory tooltip.

​

Resource context

You can upload context files — database schemas, OpenAPI specs, API documentation, and more — to any connector. The AI assistant uses this context when writing queries and API calls against that resource, so it understands your data model without you having to explain it every time. If your app needs a connector that hasn’t been set up yet, the AI will show a setup card in the chat — click it to configure the resource inline without leaving the editor.

​

Identity-based authentication

For S3 and DynamoDB resources, you can use Assume Role Identities instead of access keys. Create an identity in the web UI, review the generated trust policy for your IAM role, and select identity-based authentication when configuring your resource. This approach is more secure and avoids managing long-lived credentials.

​

Available connectors

Don’t see the connector you need? Click Request it in the Add Connector dialog to submit a request.