Integrations

Plexara composes three open-source systems through provider abstractions, enabling multi-source data federation, cross-platform catalog coverage, and universal object storage access through a single MCP endpoint.

Query Engine

Trino Federation

A single query can join a PostgreSQL table with an Elasticsearch index, an Iceberg lakehouse, and a Cassandra cluster. Trino does not require data to be moved, copied, or transformed. It queries data where it lives.

Multi-connection support lets you configure separate Trino clusters and route tool calls to specific connections via the connection parameter. Read-only enforcement, query timeouts, and configurable row limits keep production systems safe.

40+ supported connectors including

PostgreSQLMySQLMariaDBSQL ServerOracleElasticsearchOpenSearchCassandraMongoDBRedisIcebergDelta LakeHiveHudiGoogle SheetsKafkaKinesisPinotDruidClickHouseBigQueryRedshiftSnowflake

The New Connection form in the Connections admin screen, with the kind set to trino, an identifier field, a split markdown description editor with an empty preview, and a Configuration card holding the connection details and a default catalog and schema, with Cancel and Create buttons — Adding a Trino connection: pick the kind, name it, describe what it is for, and point it at the cluster.

The edit form for an existing Trino connection named acme-warehouse, with the kind and identifier locked, a description reading production data warehouse with retail, inventory, and analytics schemas shown in source and preview, and the Configuration card below with a Save button — Editing keeps the kind and identifier fixed, since persona patterns and tool routes refer to them, and lets everything else change.

Metadata Catalog

DataHub Integration

Full catalog operations across datasets, dashboards, charts, data flows, data jobs, containers, data products, domains, glossary terms, and glossary nodes.

Search

Advanced filters by column names, tags, glossary terms, platform, domain, and owner.

Metadata

Entity details, schema with column descriptions, structured properties, data contracts.

Lineage

Dataset and column-level lineage traversal. Upstream and downstream graph exploration.

Glossary

Business term definitions, glossary node hierarchy, term-to-entity mappings.

Write Ops

Create, update, and delete entities. Manage descriptions, tags, glossary terms, incidents.

Data Products

Business-oriented groupings of related datasets for specific use cases and audiences.

The Connections admin screen with connections grouped by kind in a left column, DataHub, MCP, S3, and Trino, and a DataHub catalog connection selected on the right showing its description, kind, creator, last updated time, and Edit and delete buttons — Every connection your deployment has, grouped by kind, with the DataHub catalog connection open. Each one lists how many tools it exposes.

Object Storage

S3 Integration

Bucket browsing, object listing with prefix filtering, content retrieval, metadata inspection, and presigned URLs for temporary access. Prefix ACLs restrict access to specific S3 paths. Read-only mode blocks write operations.

Size limits protect against oversized transfers: 10MB for GET operations, 100MB for PUT. All storage operations are subject to the same persona-based access controls and audit logging as query and catalog operations.

List Buckets

Browse available storage buckets

List Objects

Explore objects with prefix filtering

Get Object

Retrieve content up to 10MB

Get Metadata

Inspect object metadata and properties

Presigned URLs

Generate temporary download and upload links

Put / Copy / Delete

Write operations with configurable controls

External APIs

Connect external REST APIs

Federation is not limited to your data. The API gateway connects Plexara to any external REST or HTTP API, from Salesforce and Stripe to your own internal services, and lets the assistant search and call their operations directly.

Each API is described once and shared across connections, Plexara handles the sign-in, and access is limited by role, so those calls are governed and logged on the same endpoint as Trino, DataHub, and S3.

Explore the API Gateway

OAuth 2.1

API key

Bearer token

Basic auth

mTLS certificates

Static headers

Compatibility

Any MCP Client

Plexara works with any MCP-compatible client. Agents reach it over the standard remote MCP transport, with nothing to install and no local process to run. Multiple Trino clusters, DataHub instances, and S3 endpoints sit behind that one endpoint, selected per call through the connection parameter.

Claude Desktop

Anthropic's desktop application with native MCP support

Cursor

AI-powered code editor with MCP tool integration

Custom Agents

Build with the MCP SDK in Python, TypeScript, Go, or any supported language

API Gateway

The same governed connection, pointed at Salesforce, Stripe, and your own internal services.

Continue