Prebuilt sources
Native support for PostgreSQL, MySQL, MariaDB, SQL Server, Oracle, MongoDB, Redis, Elasticsearch, Snowflake, BigQuery, AlloyDB, Spanner, Firestore, Neo4j, ClickHouse, Couchbase, CockroachDB, and Trino.
Endeavor application integrations
Endeavor integrates with any business application that exposes an API or an MCP server. This page covers how that works technically: the connector layer, the three routes into a system, and the controls applied to every call.
Why integration decides whether an agent is useful
An agent is only as good as the context it can reach. The automations worth building are precisely the ones that cross application boundaries: reconciling an ERP against banking data, joining an order record to a CRM conversation, checking a supplier against external risk signal.
An assistant embedded inside a single platform structurally cannot do that work, however capable its model. This is the difference between an AI feature and an AI operations layer.
The connector layer
Endeavor reaches applications through the Model Context Protocol (MCP), using MCP Toolbox — the open-source MCP server maintained by Google — as the preferred connector.
MCP Toolbox sits between the agent and your systems and handles what is tedious and easy to get wrong: connection pooling, integrated IAM authentication, and end-to-end observability through OpenTelemetry. Tools are declared in YAML as structured, parameterised operations rather than open-ended access, so an agent can only do what you explicitly defined.
MCP exposes three kinds of capability: tools (executable functions), prompts (reusable templates), and resources (read-only information). A server can be a hosted service, a container you run, or a local process.
Three routes into any application
Any REST API
The HTTP source connects to arbitrary HTTP endpoints, turning any documented web API into an available tool — with SSRF and DNS-rebinding protection on by default and custom headers for authentication.
Any OAuth MCP service
Where a vendor already publishes an MCP server, Endeavor connects directly over OAuth. Nothing custom to build, nothing to maintain as the vendor's API evolves.
Application coverage by category
| Category | Examples | Route |
|---|---|---|
| ERP | Oracle Fusion, SAP, NetSuite | Published REST API via HTTP source |
| CRM | Salesforce, HubSpot | MCP server or REST API |
| ITSM and service desk | Ticketing and incident platforms | REST API |
| HR and payroll | HRIS and payroll systems | REST API, scoped per user |
| Finance and accounting | Ledger and AP/AR systems | REST API, scoped per user |
| Relational databases | Postgres, MySQL, Oracle, SQL Server | Native MCP Toolbox source |
| Document and NoSQL | MongoDB, Couchbase, Firestore | Native MCP Toolbox source |
| Warehouses and analytics | Snowflake, BigQuery, Trino, ClickHouse | Native MCP Toolbox source |
| Search and graph | Elasticsearch, Neo4j | Native MCP Toolbox source |
A worked example: HubSpot
Rotational runs this pattern in production. Endeavor connects to HubSpot through MCP Toolbox, giving our own lead-generation agents governed read and write access to CRM records — scoped by credential, logged at the interaction level, and swappable without touching agent logic.
Nothing about the pattern is specific to HubSpot. It is the same route used for any other application.
Controls applied to every integration
| Control | How it works |
|---|---|
| Least privilege | An agent inherits the clearance of the user who invoked it |
| Declared operations | Tools are parameterised operations in configuration, not open access |
| Source attribution | The system log records which records produced each output |
| Input and output guardrails | Checks run before a prompt is sent and on the generated result |
| Credential isolation | Secrets stay in your secret manager and never leave your environment |
| Configuration not code | Adding an application does not require rewriting an agent |
What this means in practice
- Agents see only the data the initiating user is authorised to access.
- Every source read is logged, so you can prove which records produced an output.
- Structured tools prevent unauthorised lateral movement between applications.
- Swapping the underlying model does not touch the integration at all.
- Data is queried in place, so no system of record has to be duplicated.
- Adding an application is a config change, not a project.
Not seeing your application? That is not a blocker. The only requirement is that it exposes an API or an MCP service — and at this point, almost all of them do.
Frequently asked questions
What applications can Endeavor integrate with?
Any application that exposes an API or an MCP server. That covers effectively every ERP, CRM, CMS, accounting, HR, and service-desk platform in the mid-market stack, plus databases, warehouses, and object storage.
What is MCP Toolbox?
MCP Toolbox is the open-source Model Context Protocol server maintained by Google that Rotational uses as its preferred connector. It handles connection pooling, integrated IAM authentication, and end-to-end OpenTelemetry observability, and exposes tools as structured, parameterised operations declared in YAML.
What if our application has no prebuilt connector?
The HTTP source connects MCP Toolbox to arbitrary HTTP endpoints, so any documented REST API becomes an available tool. There is nothing bespoke to build or maintain, and no waiting on a vendor roadmap.
Does integrating an application mean copying our data?
No. Data is queried in place. Endeavor does not require you to migrate a system of record into another platform to make it usable by an agent.
How is an agent's access to each application controlled?
Agents inherit the clearance of the person who invoked them rather than running on a shared service account. Tools are declared as specific parameterised operations, so an agent can only perform actions you defined, and every read is logged with its source.
How long does it take to add a new application?
Adding a system is a configuration change rather than an agent rewrite. The connector is declared once and any task can then be granted the tools it needs.