Chroma’s official MCP server: vector search and collection management for RAG workflows.
Myriade is installed from its publisher's own source and answers where it runs, so this marketplace is not in the path of a single call. There is no address here to send one to, and a panel that pretended otherwise would be showing you an answer we made up. Install it and call it from your own client — the Installation tab has the entry for each one.
What it does
Explore and query your data warehouse through Myriade's AI data analyst agent.
Quickstart
# 1 — add it to Claude Code
claude mcp add --scope user --transport http myriade-mcp https://app.myriade.ai/mcp/
# 2 — ask your agent for something these tools do
# myriade_list_databases, myriade_get_database_info, myriade_list_tables and 15 more
Myriade costs nothing on mcprush: there is no plan to choose here, no cap to set and nothing mcprush can bill you for.
Collected from a public index. Nobody has claimed this account, so nothing here was written by its author — claim it if it is yours.
Where are you running it?
Every route below installs the same thing and ends at the same approval screen. Nothing here runs on your machine and nothing runs on ours: this server answers at its publisher’s own address, and what you install is the connection straight to it.
This is a public server: it answers at its publisher’s own address and this marketplace is not in the path. Claude Code registers it in one command; --scope user makes it available in every project. The transport below is http, as the publisher's own manifest declares it.
claude mcp add --scope user --transport http myriade-mcp https://app.myriade.ai/mcp/Reconnect, or start a new session, and the tools appear in the model’s tool list.
One config entry pointing straight at the publisher’s own address — this marketplace is not in the path, and nothing from this listing executes on your machine.
18 tools, with what each one reads, writes and reaches shown before you agree — the same list on every route above. Read the tool surface.
Tool surface
What the model actually sees. Descriptions are diffed on every release — see version history.
List databases configured in Myriade (paginated, sorted by name). Returns paginated database connections with their IDs, names, engines, and descriptions. Use the database ID with other tools.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| limit | integer | no | Maximum results to return (1-200) |
| offset | integer | no | Number of results to skip for pagination |
Get detailed information about a specific database connection. Returns information about the database including its name, engine type, description, write mode, and any AI memory notes.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| database_id | string | yes | UUID of the database (from myriade_list_databases) |
List tables in a database (paginated, sorted by database/schema/name). Returns a flat, paginated list of tables. Each item has database_name, schema, and name fields.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| database_id | string | yes | UUID of the database |
| limit | integer | no | Maximum tables to return (1-500) |
| offset | integer | no | Number of tables to skip for pagination |
Get the column-level schema for a specific table. Returns column names, data types, and descriptions for the table. Raises if the user has no access to the table under governance.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| database_id | string | yes | UUID of the database |
| table_name | string | yes | Name of the table to inspect |
| schema_name | no | Optional schema name to disambiguate same-named tables |
Execute a read-only SQL query against a database. Write operations (INSERT, UPDATE, DELETE, DROP, etc.) are blocked. Returns up to 50 rows of results with column metadata. Successful queries are saved in Myriade; the response's query_id can be replayed later with myriade_get_query_results without resending SQL.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| database_id | string | yes | UUID of the database |
| sql | string | yes | Read-only SQL query (writes are blocked) |
| title | no | Optional name for the saved query, shown in Myriade |
Re-execute a saved Myriade query and return fresh results. The query's SQL always re-runs under the caller's governance policies (table permissions, column masking) — results are never served from Myriade's cached snapshot. Prefer this over myriade_query for recurring metrics (dashboards, cockpits): the SQL stays governed in Myriade instead of travelling through prompts. Write statements are blo
| Parameter | Type | Required | Notes |
|---|---|---|---|
| query_id | string | yes | UUID of a saved Myriade query (from a Myriade query link, e.g. in myriade_ask responses) |
Get sample rows from a table to understand the data. Returns a random sample of up to `limit` rows (max 20).
| Parameter | Type | Required | Notes |
|---|---|---|---|
| database_id | string | yes | UUID of the database |
| table_name | string | yes | Name of the table to sample |
| schema_name | string | yes | Schema containing the table |
| limit | integer | no | Rows to sample (1-20) |
| database_name | no | Optional warehouse-side database name (e.g. for Snowflake) |
Search the data catalog for tables, columns, or terms by name/description. Uses fuzzy matching and full-text search. Keep queries short (1-2 words) for best results.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| database_id | string | yes | UUID of the database |
| text | string | yes | Search query — keep short (1-2 words) for best results |
| asset_type | no | Filter: "TABLE", "COLUMN", or "TERM" | |
| limit | integer | no | Maximum results to return (1-50) |
Get detailed information about a catalog object (table, column, schema, or glossary term — assets and terms share one id space). Returns the asset's description, tags, status, columns (for tables), sample data, parent hierarchy, and activity feed; for a glossary term, its definition, synonyms, related terms, and activity feed.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| database_id | string | yes | UUID of the database |
| asset_id | string | yes | UUID of the catalog object (asset or glossary term) |
Update a catalog asset's documentation (requires edit rights). - `description replaces the existing description (auto-sets status to "draft" if status is null). - tag_ids replaces all tags (accepts names or UUIDs; auto-creates missing tags). - status is "draft" (needs review) or "published". Only use "published" with high confidence. Use myriade_request_catalog_change` instea
| Parameter | Type | Required | Notes |
|---|---|---|---|
| database_id | string | yes | UUID of the database |
| asset_id | string | yes | UUID of the asset to update |
| description | no | Replaces existing description; auto-sets status='draft' if status is null | |
| tag_ids | no | Tag names or UUIDs (replaces all tags). Auto-creates missing tags. | |
| status | no | "draft" (needs review) or "published" (production-ready) |
Propose a catalog change for the data team to review (no edit rights needed). Creates a reviewable suggestion routed to the asset's reviewers. Does NOT change the published catalog until approved. Use this instead of `myriade_update_asset` when you lack edit rights or are not confident enough to write directly.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| database_id | string | yes | UUID of the database |
| asset_id | string | yes | UUID of the asset to propose a change for |
| field | string | yes | Field to change: "description" or "tags" |
| proposed_value | string | yes | Proposed description text, or JSON-encoded list of tag names |
| rationale | string | yes | Why this change is proposed — shown to reviewers and in the activity feed |
List or search reports (documents) written in Myriade. Without `query returns the most recently updated reports first; with query` returns the best matches first. Only reports the caller may see are returned. Read one with myriade_read_report.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| database_id | no | UUID of the database whose reports to list. Omit for organisation-level reports (not bound to a database). | |
| query | no | Optional search terms (title, description, content); results are ranked by relevance | |
| limit | integer | no | Maximum results to return (1-50) |
Read a report's full markdown content. Applies the same visibility rule as the web app; a report the caller may not see returns a "not found" error. To create or edit a report, use myriade_ask — the analyst agent knows how reports are structured.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| document_id | string | yes | UUID of the report (from myriade_list_reports) |
Ask a natural language question about a database using Myriade's data analyst agent. The agent will explore the database schema, search the catalog, run SQL queries, and analyze the results to answer your question. Use this for complex analytical questions that require multiple steps; for simple schema lookups or direct SQL, prefer the other tools. Note: the agent has access to catalog write ope
| Parameter | Type | Required | Notes |
|---|---|---|---|
| database_id | string | yes | UUID of the database |
| question | string | yes | Natural-language question about the data |
Snapshot of a database's monitoring board: check count, standing alerts (open / acknowledged / known) with their headlines, recent notifications and triage notes, followed by the open alerts as JSON. Alert ids feed myriade_triage_alert; check ids feed myriade_get_check. Investigation details are redacted unless you manage the database.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| database_id | string | yes | UUID of the database |
Get a monitoring check (name, SQL, severity, cadence, status) and its most recent run results, newest first. On governed databases the SQL and evidence rows are redacted unless you manage the database or authored the proposal.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| check_id | string | yes | UUID of the monitoring check |
| limit | integer | no | Run results to return (1-100) |
Propose a monitoring check for the user to review in Myriade. This creates a PROPOSAL, never an active check: nothing runs until a database owner or org admin accepts it in the app. The SQL is test-run once under your governance context to validate it. Contract for `check_sql: it MUST return rows ONLY when something is wrong (zero rows = healthy) and use relative time (now() - interval`),
| Parameter | Type | Required | Notes |
|---|---|---|---|
| database_id | string | yes | UUID of the database |
| name | string | yes | Short human-readable name (unique per database) |
| check_sql | string | yes | SQL returning zero rows when healthy, rows when wrong |
| severity | string | no | Severity raised when the check trips |
| interval_minutes | integer | no | Cadence in minutes (minimum 5) |
| description | string | no | One sentence, prospective tense: "Trips when <condition> (baseline ~X)" |
| group_name | no | Cluster to file the check under (reuse an existing group's exact name), or omit to leave it unfiled |
Triage an alert (requires manage access: database owner or org admin). - `resolve: the underlying problem is handled or gone. - acknowledge: keep it standing with a statement of what is happening — only for a situation that may worsen. - dismiss: false positive / expected; refused while the check still trips (it would just respawn). - snooze: silence for hours with a `
| Parameter | Type | Required | Notes |
|---|---|---|---|
| alert_id | string | yes | UUID of the alert |
| action | string | yes | Transition to apply to the alert |
| statement | no | One SHORT present-tense plain-text sentence (~120 chars, no Markdown) shown as the alert headline. Required for acknowledge, snooze and reopen. | |
| note | no | Optional note appended to the alert details (resolve, dismiss) | |
| hours | no | Snooze window in hours (1-168). Required for snooze. |
- Every tool — any call limit is its publisher’s, not ours
- No card, and mcprush charges nothing for it
- Runs at its publisher’s own address — this marketplace is not in the path
- Nothing to cap, because mcprush bills nothing
What counts against your monthly calls
| Tool | Unit | Calls used | Out of the allowance |
|---|
Nothing here is billable: mcprush charges nothing to install Myriade or to call it, at any volume.
Two independent axes, because powerful and malicious are different questions. The grade is threat only. The capability level is blast radius, and it is never a penalty on the grade — it is priced as one subtract-only term in the score, where you can see it.
This listing is an address its publisher runs, and you connect to it directly — this marketplace is not in the path. The scanner reads packages and public source, and an address is neither. So there is no grade — not a withheld one, an unmeasured one.
Release history
This is an address its publisher runs: which release it serves is theirs to choose, so there is nothing here to pin. The history below is for reading; the current release on file is 1.187.1.
No release note was published with this version.
One review per account, from a signed-in account that does not publish this listing. Nothing else is asked — you can say what you think before you install it. Publishers can reply once per review, and a review can be edited or deleted by whoever wrote it.
Any signed-in account that does not publish Myriade can review it, once — before installing it or after. A review from an account that has installed it is marked as one.
Nobody has reviewed this listing. The rating on the card is the mean of the reviews written here and nothing else, so there is no rating until somebody writes the first — which takes a signed-in account that does not publish it, and nothing else.