Secoda MCP server

What the model can do

Secoda data catalog: tables, columns, dashboards, metrics and other catalog resources with descriptions, documentation, owners, tags and usage, monitors and data-quality incidents with measurements, documents, questions and their answers, lineage between resources, and tags; when you ask, can document or verify a resource, write, edit or delete documents, ask or answer a question, add tags, collections and lineage, run monitors, delete a resource or lineage link, and invite a user.

Reads

• secoda_search_catalogSearch Secoda's catalog: tables, columns, schemas, dashboards, charts, metrics, glossary terms and other resources, with description, owners, tags…
• secoda_get_resourceOne Secoda resource by id with its full description and markdown documentation, owners, tags, collections, parent, flags, size and usage.
• secoda_monitorsData-quality monitors: what each watches (target resource id), metric (row count, freshness, nulls, custom SQL…), status (normal, incident, error…
• secoda_incidentsData-quality incidents raised by monitors: name, status (active, acknowledged, resolved, expired), the monitor and target…
• secoda_documentsDocuments in Secoda (written knowledge, runbooks, definitions), by title: title, a preview of the content, owners, collections and last change.
• secoda_questionsQuestions asked in Secoda: title, status (answered or not), priority, the accepted answer, votes and who it is assigned to (a user id).
• secoda_lineageManual lineage links in Secoda: which resources feed which (from and to resource ids, direction).
• secoda_tagsTags in the Secoda workspace: id, name, description and colour.

Acts, when you ask

These change something in Secoda. The model is told to use them only when you ask for exactly that, and each one is granted by name: per team on a shared connection, by the owner on a personal one.

• secoda_create_documentCreates a document in Secoda with the markdown content given, visible to the workspace's editors (and to viewers if published).
• secoda_update_documentEdits a Secoda document: replaces its content (the whole markdown body), description, tags, collections or published flag.
• secoda_delete_documentDeletes a Secoda document.
• secoda_update_resourceEdits a Secoda catalog resource's metadata: description, markdown documentation, verified, PII and published flags, owners (user ids), tags…
• secoda_delete_resourceDeletes a resource from the Secoda catalog, with the documentation written on it in Secoda.
• secoda_ask_questionAsks a question in Secoda, visible to the workspace; when assigned to a user, that person is notified.
• secoda_answer_questionReplies to a Secoda question with the answer given, optionally marking it the accepted answer; the asker sees it.
• secoda_create_tagCreates a tag in the Secoda workspace.
• secoda_create_collectionCreates a collection in Secoda; resources join it through secoda_update_resource.
• secoda_run_monitorsRuns the named Secoda monitors now, as a background job: each runs its query against the connected warehouse…
• secoda_add_lineageRecords in Secoda that one resource feeds another (from → to, DOWNSTREAM by default); Secoda adds the opposite direction itself.
• secoda_delete_lineageDeletes a manual lineage link in Secoda by its id (from secoda_lineage).
• secoda_invite_userInvites a person to the Secoda workspace with the role given: Secoda emails them an invitation, and once they accept they have that access…

Connect it

First connect Secoda on Dashboard → Connections, then add Memtro to your client once. The Secoda tools appear alongside the tools of everything else you have connected; nothing is configured per connector.

claude plugin marketplace add memtro-org/claude-memtro
claude plugin install memtro@memtro --config api_key=sk-memtro-...

{
  "mcpServers": {
    "memtro": {
      "url": "https://platform.memtro.com/api/mcp",
      "headers": {
        "Authorization": "Bearer sk-memtro-..."
      }
    }
  }
}

{
  "mcp": {
    "memtro": {
      "type": "remote",
      "url": "https://platform.memtro.com/api/mcp",
      "headers": {
        "Authorization": "Bearer sk-memtro-..."
      }
    }
  }
}

Who may use it

The key identifies the person, and the server offers that person the tools they may use everywhere else in Memtro. A shared Secoda connection is used by the teams an administrator granted it to, tool by tool, on the Permissions page; a personal connection is used by its owner alone, and its tools that act stay off until the owner allows them. See Teams and permissions and Connectors.

Ask it like this

• › Which data-quality incidents are active right now?
• › Who owns the orders table?
• › What feeds the revenue dashboard?
• › Is there a document on how churn is defined?
• › Which questions are still unanswered?

Questions

Is this an official Secoda MCP server?

No. It is Memtro's MCP server with Memtro's Secoda connector behind it: the connector reads Secoda through its API with the credentials you connect on Dashboard → Connections, and Secoda publishes nothing here. The same endpoint carries every other system you connect and Memtro's memory tools.

What does it cost?

Nothing on top of Memtro. One price per organisation by its number of users, from $50 a month for up to 10 users after a 7-day free trial, with every connector, the MCP server, jobs and memory included. You bring your own model keys.

Can it change anything in Secoda?

Only when you ask, and only what it has been granted: create a document; edit a document; delete a document; edit a resource's description, documentation, owners, tags or flags; delete a catalog resource; ask a question (the assignee is notified); answer a question; create a tag; create a collection; run monitors now (queries the warehouse); add lineage between two resources; delete a lineage link; invite a user to the workspace. Every other tool reads, searches or lists. An administrator grants each acting tool by name per team, and a personal connection acts only after its owner allows it.

Which clients work?

Any MCP client that speaks Streamable HTTP: Claude Code, Cursor, Claude Desktop, OpenCode, Codex, Zed, Windsurf, Cline and the Anthropic and OpenAI SDKs. There is no local process to run; the server is remote and authenticated with your key.

Other MCP servers · Databases and warehouses

• Postgres MCP server
• MySQL and MariaDB MCP server
• SQL Server MCP server
• BigQuery MCP server
• Snowflake MCP server
• AWS Athena MCP server