Connect Collate to ECA
Give ECA governed access to Collate’s 19 tools through Runlayer, with identity, policy, scanning, and audit on every call.
Set up
Add Collate to ECA in four steps
Admins approve the server once. Everyone in ECA then gets it through the same governed connection.
- 1
Add Collate to Runlayer
Collate isn’t in the Runlayer catalog yet, so an admin adds it by its MCP server URL.
Adding a connector manually - 2
Connect ECA to Runlayer
Users add the Runlayer Plugin to ECA by following Runlayer’s setup guide. ECA reaches Collate’s 19 tools through the Runlayer Plugin’s search and execute tools instead of listing each one.
ECA setup guide - 3
Sign in to Collate
Sign in the way Collate requires. Runlayer holds the credentials so they stay out of the client’s configuration.
- 4
Use Collate from ECA
Collate’s approved tools appear in ECA. Every call is checked against policy and recorded.
Tools
19 Collate tools in ECA
Runlayer policy decides which of these ECA users can call.
Create article
Creates a Knowledge Center Article page in Collate.
Create classification
Creates a new Classification in OpenMetadata.
Create data product
Creates a new Data Product in OpenMetadata.
Create domain
Creates a new Domain in OpenMetadata.
Create glossary
Creates a new Glossary.
Create glossary term
Creates a new Glossary Term.
Create lineage
Can be used to create lineage between two assets.
Create metric
Creates a new Metric entity in OpenMetadata.
Control
What Runlayer can see and stop in ECA
Some controls apply to every client at the gateway. Others depend on what ECA exposes to Runlayer.
Gateway policy (available)
Every Collate call from ECA passes through Runlayer, where your policies can allow, alert, mask, or block it.
Audit trail (available)
Each call is recorded with the user, ECA as the client, the tool, and the policy and scanner decisions.
Native enforcement adapter (not available)
Runlayer has no device-side adapter for ECA yet, so control happens at the gateway.
Frequently asked questions
Connect more