Plexara
What is an MCP?
201 - Anatomy of a Plexara MCP
201 shows what is actually in the box on a Plexara server: the tool inventory by toolkit, the four content layers, the interactive apps a tool result can carry, and the memory, knowledge, and governance underneath. This lesson is the map.
202 - Your first day with Plexara
A new Plexara user gets connected, sends a first question, and platform_info takes over. Walks through day one and how subsequent turns inherit context.
203 - Discovery: one search, then fetch
One question reaches every system the agent can see. Results come back grouped by source with a coverage summary, and fetch reads any of them in full.
204 - Trino Query: analytics and insights
Plexara reaches customer data through Trino. What Trino is, how it maps to DataHub metadata, why OLAP queries finish fast, and how to export large results.
205 - Assets: dashboards, reports, and data
Plexara's asset system persists dashboards, reports, and exports outside chat. Naming asset tools in a prompt saves tokens and keeps outputs shareable.
206 - Knowledge: from a memory to something the whole team can use
Memory to Insight to Knowledge: the three stages a fact travels, the capability check that promotes it, and the two canonical places it lands.
207 - Governance: personas, access, and audit
Governance in Plexara is enforced when a tool is invoked, not described in a policy. Personas, default-deny, layered safeguards, and a single audit log.
208 - The prompt library: versioned, shared, and measurable
Two buckets, collections and facets, version history with approval provenance, attached materials, and running a prompt by whatever handle you know it by.
209 - Resources: the company files the agent should use, not reinvent
Your templates, brand files, and reference documents, uploaded once and used as-is: which layer a file belongs on, search then fetch, revisions that keep every citation resolving, and making a template mandatory.
210 - Putting it all together: a worked end-to-end example
A capstone that walks a single real-world question through every Plexara subsystem covered in the 200 series, with a tool-by-tool reference at the end.
211 - Governing the catalog without leaving the portal
Tags, domains, the business glossary, context documents, and per-table metadata are edited in the portal, under the same persona grants that govern the agent and in the same audit log.
212 - Seeing the shape of what your team knows
The portal draws your knowledge corpus as its reference network and measures it: node size is how much of the corpus an entity holds together, and a citation the catalog cannot confirm is stated rather than drawn as if it resolved.