Skip to content
Skill

marmot

by marmotdata

AI Summary

This skill helps you interact with a Marmot data catalog. Marmot catalogs data assets (databases, tables, topics, APIs, dashboards) across an organisation's data stack and tracks lineage between them. The user needs the Marmot CLI installed and authenticated. If not already set up: opens a browser f

Install

Copy this and paste it into Claude Code, Cursor, or any AI assistant:

I want to install the "marmot" skill in my project.

Please run this command in my terminal:
# Install skill into your project
mkdir -p .claude/skills/marmot && curl --retry 3 --retry-delay 2 --retry-all-errors -o .claude/skills/marmot/SKILL.md "https://raw.githubusercontent.com/marmotdata/marmot/main/SKILL.md"

Then restart Claude Code (or reload the window in Cursor) so the skill is picked up.

Description

Interact with a Marmot data catalog instance. Use this skill when the user wants to search for data assets, view lineage, browse glossary terms, check pipeline runs, manage tags or owners, view metrics, or do anything related to their data catalog. Covers the Marmot CLI, REST API and MCP server.

Setup

The user needs the Marmot CLI installed and authenticated. If not already set up: `bash curl -fsSL get.marmotdata.io | sh marmot login https://marmot.example.com ` marmot login opens a browser for OAuth 2.0 PKCE authentication and caches the token locally. Alternatively, use an API key: `bash export MARMOT_HOST=https://marmot.example.com export MARMOT_API_KEY=<key> ` Or pass --host and --api-key as flags on any command.

MCP Server

Marmot has a built-in MCP (Model Context Protocol) server. If the user has configured MCP, you can interact with the catalog directly using these tools instead of the CLI: • discover_data — unified data discovery. Supports natural language queries, lookups by ID or MRN (e.g. postgres://db/schema/table), filtering by type/provider/tags and metadata-based queries. • find_ownership — bidirectional ownership queries. "Who owns this asset?", "What does this user own?", "Show all data owned by the data-eng team". Works for assets and glossary terms. • lookup_term — business glossary lookups. Search for terms by name or retrieve definitions. MCP configuration lives in ~/.claude.json (user-level) or .mcp.json (project-level): `json { "mcpServers": { "marmot": { "type": "http", "url": "https://<marmot-server>/api/v1/mcp", "headers": { "X-API-Key": "<api-key>" } } } } ` Prefer MCP tools when available. Fall back to the CLI or REST API for operations MCP doesn't cover (e.g. writes, metrics, admin).

CLI Reference

All commands follow the pattern marmot <resource> <action> [args] [flags]. Use --output json (or -o json) to get machine-readable output. Supported output formats: table (default), json, yaml.

Assets

`bash marmot assets list # list assets (paginated) marmot assets search <query> # search assets marmot assets get <id> # get asset details marmot assets summary # counts by type, provider, tag marmot assets tags add <id> <tag> # add a tag marmot assets tags remove <id> <tag> # remove a tag marmot assets owners <id> # list owners marmot assets delete <id> # delete (prompts for confirmation) ` Filters: --types, --providers, --tags. Pagination: --limit, --offset.

Discussion

0/2000
Loading comments...

Health Signals

MaintenanceCommitted Today
Active
Adoption100+ stars on GitHub
577 ★ · Growing
DocsREADME + description
Well-documented

GitHub Signals

Stars577
Forks19
Issues19
UpdatedToday
View on GitHub
MIT License

My Fox Den

Community Rating

Sign in to rate this booster

Works With

Claude Code