Integrations

Your data comes in. Your tools reach back.

Corvic connects to the warehouses, stores and APIs you already run — and exposes an MCP endpoint so Claude, Cursor or your own client can reach the agents and tables on the other side.

Connect the systems your data already lives in

Warehouses and object stores connect once at the organization level, with credentials validated on the way in. Rooms then attach a folder, a table, an upload or a web query — nothing is copied out of place.

Snowflake
Databricks
BigQuery
Redshift
Google Cloud Storage
AWS S3
Azure Blob Storage
PostgreSQL

Everything your agents can call

56 of 56

Snowflake
Databricks
BigQuery
Redshift
Google Cloud Storage
AWS S3
Azure Blob Storage
PostgreSQL
MySQL
MongoDB
Redis
Elasticsearch
Kafka
Salesforce
HubSpot
Pipedrive
Zoho CRM
Crunchbase
Apollo.io
Stripe
QuickBooks
Polygon.io
Finnhub
SerpApi
PubMed
Epic on FHIR
Oracle Health
Health Gorilla
Medplum
Supabase
HuggingFace
Kaggle
Slack
Twilio
SendGrid
Notion
Airtable
Linear
Jira
Google Sheets
GitHub
GitLab
OpenAI
OpenRouter
Anthropic
Scrapfly
Apify
Firecrawl
Mailchimp
Klaviyo
Google Analytics
DataForSEO
Gmail
Google Calendar
Google Drive
Microsoft 365

Not on the list? Register any REST API by its origin and auth header, bring your own OAuth app, or point at a RapidAPI host.

API Secret VaultBeta

The credential half of a connector, kept out of the model's reach. You register a service once; agents call it forever without the token ever entering a prompt.

The agent never receives the secret. Corvic stores the value server-side and hands the agent only the name of the key and the header it belongs in. When code in the sandbox calls that host, the sandbox injects the header on the way out — so a leaked transcript, a logged prompt or a prompt-injection attempt has nothing to leak.

Paste a token, not a pluginPick a service and Corvic prefills its origin and auth header. Anything else: add the origin and headers yourself.
Personal accounts use OAuthGmail, Calendar, Drive, Microsoft 365 and the rest authorize through OAuth instead of a pasted key.
Private, or shared with the orgEach entry is yours alone or visible organization-wide, and an agent only reaches the ones you allow it.

Data and tool access, through one MCP endpoint

Corvic speaks Model Context Protocol in both directions. Your agents call out to MCP servers — and your room is itself an MCP server, so the tools your team already uses can reach in.

Access tokeneyJhbG•••••••••••1JZAExpires in1 day

Room endpoint

https://api.corvic.dev/mcp/

Header — Authorization: Bearer <token>

Tool

Ask the agent a question and get an answer with its room behind it.

Arguments (JSON)

{
  "query_content": "Which accounts are at renewal risk this quarter?",
  "with_citation": true,
  "with_images": false
}

POST tools/call → Agent · query

Response

Run a tool to see the response here.

{
  "mcpServers": {
    "corvic": {
      "url": "https://<your-corvic-host>/mcp/",
      "headers": {
        "Authorization": "Bearer <access-token>"
      }
    }
  }
}

Three steps, no SDK to adoptBeta

1Open a room, mint an access token, and choose what it may read, write or execute.
2Copy the room's MCP endpoint URL from the same dialog.
3Point your client at it over streamable HTTP with the token as a bearer header.

There is a playground in the app for trying calls before you wire anything up, and the same endpoint answers tools/list so a client can discover what it can do.

Your agentsquery puts a question to the agent and answers it with the room behind it.
Your rooms and playbooksList rooms and playbooks, run one, and pull the tables it wrote as parquet.
Your knowledgeTraverse the graph or search semantically across a room's documents and tables.

The reverse direction works too: inside Corvic, an agent can attach external MCP servers as tools, so the same protocol carries your stack in and your results out.

Connect your first source

Point Corvic at a warehouse, a bucket or an API key and ask it something. Free to start, no credit card.

See the agent harness