> ## Documentation Index > Fetch the complete documentation index at: https://docs.corvic.ai/llms.txt > Use this file to discover all available pages before exploring further. # Connector Vault > One place for every external service, database, and MCP server your agents use, with credentials agents never see. The **Connector Vault** is where your organization connects everything Corvic reaches: SaaS APIs, personal accounts such as Gmail or Microsoft 365, MCP servers, cloud storage buckets, and databases. You connect a service once. Agents, workflows, apps, and playbooks then use it by name. Corvic's proxy adds the credential to each request, so the secret never appears in agent code, logs, or chat history. Find it under [**Settings → Connector Vault**](https://app.corvic.ai/settings/vault). (It was called the *API Secret Vault* before.) ![Connector Vault with the Connected tab open, filtered by All, MCP, OAuth, API, and Storage/Databases, showing connector cards with their status, kind, and visibility](https://mintcdn.com/corvicinc/bul-C054LMt6FJW9/images/connector-vault.png?fit=max\&auto=format\&n=bul-C054LMt6FJW9\&q=85\&s=2d920bb1f45b6f52e812501252a0b9e9) ## How it works **1. Connect a service** Pick a service from the catalog, sign in with OAuth, point Corvic at an MCP server, or add a bucket or database. Anything reachable over HTTPS can also be added as a custom connector. **2. Corvic stores the credential** The key, token, or password is stored encrypted in the vault. Only the connector's name, host, and settings are shown afterwards, never the secret. **3. Your agents use it by name** When code in a run calls the connector's host, Corvic's proxy injects the credential into the right header or query parameter. MCP tools, buckets, and databases work the same way: the credential stays in the vault. ## Find your way around the vault | Control | What it does | | - | - | | **Connected** / **Available to connect** | Switch between the connectors your organization already has and the catalog of services you can add. Each tab shows a count. | | **All · MCP · OAuth · API · Storage/Databases** | Filter either tab by kind of connector. | | **Search** | Find a connector by name across both tabs, for example *Stripe*, *FHIR*, or *Slack*. | | **Sort by** | Order connectors by **Newest** or **Name (A–Z)**. | | **Add Custom Connector** | Add something that isn't in the catalog: an **API key**, **OAuth** app, **MCP server**, or **Storage/Databases** connector. | Each connected card shows the connector's status. OAuth and MCP connectors also show whether they are connected, need you to finish signing in, or *need reconnect* after a sign-in expired. ## Kinds of connectors > [card] [API keys](https://docs.corvic.ai/connector-vault/api-keys.md) > > Bearer tokens, API keys, basic authentication, or query-parameter keys for any HTTPS API. > [card] [OAuth](https://docs.corvic.ai/connector-vault/oauth.md) > > Sign in to a service; Corvic keeps the access token fresh. > [card] [MCP servers](https://docs.corvic.ai/connector-vault/mcp-servers.md) > > Remote MCP servers whose tools your agents can call. > [card] [Cloud storage](https://docs.corvic.ai/connector-vault/cloud-storage.md) > > Amazon S3, S3-compatible stores, Google Cloud Storage, and Azure Storage. > [card] [Databases](https://docs.corvic.ai/connector-vault/databases.md) > > PostgreSQL, Redshift, MySQL, SQL Server, Trino, Snowflake, BigQuery, Databricks, and Oracle. > [card] [Change data capture](https://docs.corvic.ai/connector-vault/postgres-cdc.md) > > Keep a live copy of Postgres and Oracle tables in Corvic. ## Connector catalog The catalog has one-click presets for dozens of services, grouped by category. A preset fills in the host and the authentication header, so connecting is just "pick a service and paste your token." Presets carry only the **shape** of the request, never a real secret. > [card] [Personal accounts](https://docs.corvic.ai/connector-vault/catalog/personal-accounts.md) > > Gmail, Google Drive, Microsoft 365, Slack, GitHub, and more > [card] [Sales & CRM](https://docs.corvic.ai/connector-vault/catalog/sales-crm.md) > > Salesforce, HubSpot, Pipedrive, Crunchbase, Apollo.io > [card] [Finance](https://docs.corvic.ai/connector-vault/catalog/finance.md) > > Stripe, QuickBooks, Polygon.io, Finnhub, SerpApi > [card] [Healthcare](https://docs.corvic.ai/connector-vault/catalog/healthcare.md) > > PubMed, Epic on FHIR, Oracle Health, Health Gorilla, Medplum > [card] [Databases & Data](https://docs.corvic.ai/connector-vault/catalog/databases-data.md) > > Databases, warehouses, buckets, HuggingFace, Kaggle > [card] [Communication](https://docs.corvic.ai/connector-vault/catalog/communication.md) > > Slack, Twilio, SendGrid > [card] [Productivity](https://docs.corvic.ai/connector-vault/catalog/productivity.md) > > Notion, Airtable, Linear, Jira, Google Sheets > [card] [Developer](https://docs.corvic.ai/connector-vault/catalog/developer.md) > > GitHub, GitLab, OpenAI, Anthropic, Apify, Firecrawl > [card] [Marketing](https://docs.corvic.ai/connector-vault/catalog/marketing.md) > > Mailchimp, Klaviyo, Google Analytics, DataForSEO The catalog grows with most releases. The [use cases](https://docs.corvic.ai/use-cases/overview.md) list the connectors each one needs. ## Reaching private networks Connectors normally reach services over the public internet. If a service only accepts known IP addresses, use [Dedicated IP](https://docs.corvic.ai/virtual-network/dedicated-ip.md). If a database lives in your own cloud network, reach it over [Corvic Private Networking](https://docs.corvic.ai/virtual-network/private-networking.md). ## Related Documentation > [card] [Using connectors](https://docs.corvic.ai/connector-vault/using-connectors.md) > > Give agents, workflows, apps, and playbooks access to a connector. > [card] [Access and security](https://docs.corvic.ai/connector-vault/access-and-security.md) > > Visibility, testing, policies, and what a connector can reach. This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.