Pre-built sources
MCP Toolbox ships native support for PostgreSQL, MySQL, MariaDB, SQL Server, Oracle, MongoDB, Redis, Elasticsearch, Snowflake, BigQuery, AlloyDB, Spanner, Firestore, Neo4j, ClickHouse, Couchbase, CockroachDB, and Trino.
Connect to Systems You Already Run
Endeavor is designed to leverage existing enterprise systems. If a system has an API or an MCP server, Endeavor can work with it. That covers essentially every ERP, CRM, CMS, accounting, HR, and service-desk platform in the mid-market stack.
Three Ways to Connect
Any REST API
The HTTP source connects Toolbox to arbitrary HTTP endpoints, so any web API becomes 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 to it directly over OAuth. No custom connector to build or maintain.
How the Integration Layer Works
AI is only as good as its context data. Endeavor reaches your systems through the Model Context Protocol (MCP), using MCP Toolbox as our preferred connector — the open-source MCP server maintained by Google.
MCP Toolbox sits between the agent and your data sources and handles the parts that are tedious and easy to get wrong: connection pooling, integrated IAM authentication, and end-to-end observability through OpenTelemetry.
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 token, logged at the interaction level, and swappable without touching agent logic.
The same pattern is how Endeavor reaches any other system. Nothing about it is specific to HubSpot.
Systems Endeavor is Built to Reach
ERP
Oracle Fusion, SAP, NetSuite and similar systems of record, reached through their published APIs.
CRM
Salesforce, HubSpot, and other pipeline and customer-data platforms.
ITSM & Service Desk
Ticketing and incident platforms, so agents can act on operational work rather than just describe it.
HR & Finance
HRIS, payroll, and accounting systems where data is sensitive and access must be provably scoped.
Data and cloud
Postgres, MongoDB, Elasticsearch, object storage, and data warehouses; queried directly rather than copied.
Governed Integration
- Agents see only the data the initiating user is authorised to access, not a god-mode service account.
- Every source read is logged, so you can prove which records produced a given output.
- Structured, parameterised tools prevent unauthorised lateral movement between systems.
- Connections are declared as configuration, so adding a system does not mean rewriting an agent.
- Credentials live in your secret manager and never leave your environment.
Not seeing your platform? That is not a blocker. The question is only whether the system exposes an API or an MCP service - almost all of them do.