{"passport":{"unfragile":{"@version":"1.0","version":"2026-05","artifact":{"id":"awesome-dolt","slug":"dolt","name":"Dolt","type":"mcp","url":"https://github.com/dolthub/dolt-mcp","page_url":"https://unfragile.ai/dolt","categories":["mcp-servers"],"tags":[],"pricing":{"model":"open_source","free":true,"starting_price":null},"status":"active","verified":false},"capabilities":[{"id":"awesome-dolt__cap_0","uri":"capability://data.processing.analysis.version.controlled.database.schema.and.data.diffing","name":"version-controlled database schema and data diffing","description":"Exposes Dolt's Git-like version control system as MCP tools, enabling clients to diff database schemas and data rows across commits, branches, and tags. Implements a commit-based snapshot model where each database state is immutable and addressable by commit hash, allowing precise tracking of structural and content changes without requiring external diff computation.","intents":["I want to see what changed in a table schema between two database versions","I need to understand which rows were modified, added, or deleted in a specific commit","I want to compare the current database state against a previous branch to audit changes","I need to generate a changelog of all schema migrations across database history"],"best_for":["data engineers building automated data quality pipelines","teams requiring audit trails and compliance tracking for database changes","developers integrating version control into LLM-powered data analysis agents"],"limitations":["Diff computation scales linearly with row count; large tables (>1M rows) may incur latency","No built-in support for diffing computed columns or views across versions","Requires Dolt binary and initialized Dolt repository; cannot work with standard SQL databases"],"requires":["Dolt CLI installed and in PATH","Initialized Dolt repository with at least one commit","MCP client compatible with tool-calling protocol"],"input_types":["table names (string)","commit hashes or branch names (string)","SQL WHERE clauses for row filtering (string)"],"output_types":["structured diff objects (JSON with added/modified/deleted row counts)","schema change descriptions (column additions, type changes, constraints)","row-level diffs with before/after values"],"categories":["data-processing-analysis","version-control"],"confidence":0.5,"matches":0,"success_rate":0},{"id":"awesome-dolt__cap_1","uri":"capability://data.processing.analysis.branch.aware.database.querying.and.context.switching","name":"branch-aware database querying and context switching","description":"Provides MCP tools to execute SQL queries against specific Dolt branches, allowing clients to switch execution context between parallel database versions without managing separate connections. Implements branch isolation at the query execution layer, where each query is routed to the correct branch's data files and indexes before SQL compilation.","intents":["I want to run the same query against multiple database branches to compare results","I need to execute a query on a feature branch without affecting the main production database","I want to test a schema change on a branch before merging it to production","I need to query historical data by checking out a specific commit as a temporary branch"],"best_for":["teams using branch-based database development workflows","LLM agents that need to compare query results across multiple database states","data scientists prototyping schema changes without impacting live queries"],"limitations":["Branch switching incurs file I/O overhead; rapid context switching between many branches may cause latency spikes","No automatic query optimization across branches; each branch uses its own index statistics","Concurrent writes to different branches require explicit merge conflict resolution; no automatic three-way merge for data"],"requires":["Dolt repository with multiple branches created","SQL query syntax compatible with Dolt's MySQL dialect","MCP client with stateful connection management"],"input_types":["branch name (string)","SQL query (string)","query parameters for prepared statements (JSON)"],"output_types":["query result sets (JSON array of objects)","execution metadata (rows affected, query time, branch name)"],"categories":["data-processing-analysis","tool-use-integration"],"confidence":0.5,"matches":0,"success_rate":0},{"id":"awesome-dolt__cap_2","uri":"capability://data.processing.analysis.commit.based.database.snapshots.and.rollback","name":"commit-based database snapshots and rollback","description":"Exposes Dolt's commit history as queryable snapshots, allowing clients to restore the database to any previous commit state or create temporary read-only views of historical data. Implements rollback via Dolt's internal commit graph, where each commit is immutable and contains complete table state, enabling O(1) logical rollback without transaction logs.","intents":["I want to restore the database to a specific point in time after a bad migration","I need to query what the data looked like at a specific commit for auditing purposes","I want to create a read-only snapshot of the database at a particular version for testing","I need to compare the current state against multiple historical snapshots to find when a bug was introduced"],"best_for":["teams with strict data recovery and compliance requirements","developers debugging data corruption issues by examining historical states","LLM agents performing root-cause analysis on data anomalies"],"limitations":["Rollback is a logical operation that rewrites the working directory; large databases (>10GB) may take minutes","No point-in-time recovery for in-flight transactions; rollback is at commit granularity only","Snapshot queries require materializing the full table state in memory for large tables"],"requires":["Dolt repository with commit history","Sufficient disk space for snapshot materialization","Write permissions to the Dolt working directory for rollback operations"],"input_types":["commit hash (string)","branch name (string)","tag name (string)"],"output_types":["confirmation of rollback completion (JSON with commit hash and timestamp)","snapshot query results (JSON array of historical rows)","commit metadata (author, message, timestamp, parent commit)"],"categories":["data-processing-analysis","automation-workflow"],"confidence":0.5,"matches":0,"success_rate":0},{"id":"awesome-dolt__cap_3","uri":"capability://data.processing.analysis.schema.aware.merge.conflict.detection.and.resolution","name":"schema-aware merge conflict detection and resolution","description":"Provides MCP tools to detect and resolve merge conflicts when combining database branches, with schema-level conflict detection that identifies incompatible column type changes, constraint violations, and data conflicts. Implements a three-way merge algorithm that compares the common ancestor, source branch, and target branch to determine if changes are compatible or require manual intervention.","intents":["I want to merge a feature branch that added columns into main and see if there are conflicts","I need to detect if two branches modified the same column in incompatible ways","I want to automatically resolve conflicts where one branch added a column and another didn't","I need to understand which rows conflict when merging two branches with overlapping data changes"],"best_for":["teams with parallel database development workflows requiring conflict resolution","data engineers managing schema migrations across multiple feature branches","LLM agents automating database merge operations in CI/CD pipelines"],"limitations":["Merge conflict resolution is schema-aware but not semantically aware; cannot resolve conflicts based on business logic","Large merges (>100K row conflicts) require manual intervention; no automatic conflict resolution strategy for data conflicts","Constraint violations during merge are detected but not automatically fixed; requires explicit data remediation"],"requires":["Dolt repository with multiple branches to merge","Common ancestor commit between branches (automatic if branches diverged from same parent)","Write permissions to target branch"],"input_types":["source branch name (string)","target branch name (string)","merge strategy preference (string: 'ours', 'theirs', 'manual')"],"output_types":["merge conflict report (JSON with conflicted tables, columns, and rows)","merge status (success, conflicts detected, merge aborted)","conflict resolution suggestions (JSON with recommended actions)"],"categories":["data-processing-analysis","automation-workflow"],"confidence":0.5,"matches":0,"success_rate":0},{"id":"awesome-dolt__cap_4","uri":"capability://search.retrieval.commit.history.traversal.and.ancestry.querying","name":"commit history traversal and ancestry querying","description":"Exposes Dolt's commit graph as queryable MCP tools, allowing clients to traverse commit history, identify common ancestors, and analyze lineage relationships between branches. Implements graph traversal using Dolt's internal commit DAG (directed acyclic graph) structure, enabling efficient ancestor lookup and branch divergence analysis without scanning the entire history.","intents":["I want to find the common ancestor between two branches to understand when they diverged","I need to list all commits between two points in history to generate a changelog","I want to identify which commits modified a specific table or column","I need to trace the lineage of a data change back to its origin commit"],"best_for":["developers building automated changelog and release note generators","data lineage and audit systems that track data provenance","LLM agents analyzing database evolution and change patterns"],"limitations":["Ancestry queries on very deep histories (>10K commits) may incur traversal latency","No built-in filtering by commit author or message; requires post-processing of results","Commit graph traversal is read-only; cannot modify commit history or rewrite ancestry"],"requires":["Dolt repository with commit history","MCP client capable of handling potentially large result sets"],"input_types":["commit hash (string)","branch name (string)","table name for filtering commits (string, optional)"],"output_types":["commit list with metadata (hash, author, message, timestamp, parent hashes)","common ancestor commit (JSON with commit details)","divergence point information (commit where branches split)"],"categories":["search-retrieval","data-processing-analysis"],"confidence":0.5,"matches":0,"success_rate":0},{"id":"awesome-dolt__cap_5","uri":"capability://data.processing.analysis.table.schema.inspection.and.metadata.extraction","name":"table schema inspection and metadata extraction","description":"Provides MCP tools to introspect Dolt table schemas, including column definitions, data types, constraints, indexes, and primary keys. Implements schema inspection by querying Dolt's internal information schema tables (INFORMATION_SCHEMA), which are automatically maintained and reflect the current branch state.","intents":["I want to get the full schema definition of a table to understand its structure","I need to list all columns and their data types for a table","I want to identify which columns are indexed or part of the primary key","I need to check if a table has foreign key constraints before modifying it"],"best_for":["developers building schema-aware code generation tools","LLM agents that need to understand database structure before generating queries","data engineers validating schema consistency across branches"],"limitations":["Schema inspection is read-only; cannot modify schemas via this capability","No support for custom data types or user-defined functions; limited to standard SQL types","Constraint information is limited to what Dolt's MySQL dialect supports; some advanced constraints may not be visible"],"requires":["Dolt repository with initialized tables","Read access to INFORMATION_SCHEMA tables"],"input_types":["table name (string)","database name (string, optional)"],"output_types":["column definitions (JSON array with name, type, nullable, default, constraints)","index information (JSON with index name, columns, uniqueness)","primary key definition (JSON with column names)"],"categories":["data-processing-analysis","search-retrieval"],"confidence":0.5,"matches":0,"success_rate":0},{"id":"awesome-dolt__cap_6","uri":"capability://data.processing.analysis.data.import.and.bulk.loading.with.version.tracking","name":"data import and bulk loading with version tracking","description":"Provides MCP tools to import data from external sources (CSV, JSON, SQL dumps) into Dolt tables with automatic commit creation and version tracking. Implements bulk loading by leveraging Dolt's native LOAD DATA INFILE and INSERT statements, which automatically create a new commit with the import as a tracked change.","intents":["I want to import a CSV file into a Dolt table and create a commit for the import","I need to bulk load data from an external database and track it as a version","I want to import data and have it automatically tracked in the commit history for audit purposes","I need to import data into a specific branch without affecting main"],"best_for":["data engineers building ETL pipelines with version control","teams importing external data sources and requiring audit trails","LLM agents automating data ingestion workflows"],"limitations":["Import performance depends on table size and index complexity; large imports (>1GB) may take significant time","No built-in data validation or transformation; requires pre-processing of source data","Commit message for imports is auto-generated; no custom commit metadata support"],"requires":["Dolt repository with target table schema already defined","Source data file accessible to Dolt process (local path or URL)","Write permissions to target branch"],"input_types":["file path or URL (string)","file format (string: 'csv', 'json', 'sql')","target table name (string)","branch name (string, optional)"],"output_types":["import confirmation (JSON with rows imported, commit hash, timestamp)","import errors or warnings (JSON array with error details)"],"categories":["data-processing-analysis","automation-workflow"],"confidence":0.5,"matches":0,"success_rate":0},{"id":"awesome-dolt__cap_7","uri":"capability://automation.workflow.branch.creation.and.management","name":"branch creation and management","description":"Provides MCP tools to create, delete, and list database branches, with support for branching from specific commits or other branches. Implements branch creation by creating a new reference in Dolt's ref system that points to a commit, enabling isolated database development without copying data.","intents":["I want to create a feature branch to test a schema change without affecting main","I need to create a branch from a specific commit for debugging purposes","I want to list all existing branches and their current commit","I need to delete a branch after merging it back to main"],"best_for":["teams using branch-based database development workflows","developers testing schema changes in isolation","LLM agents automating database environment provisioning"],"limitations":["Branch creation is a metadata operation; does not copy data, so branches share storage with parent","No automatic branch cleanup; deleted branches must be explicitly removed","Branch names must follow Git naming conventions; special characters may be rejected"],"requires":["Dolt repository initialized","Write permissions to create/delete refs"],"input_types":["branch name (string)","source commit or branch (string, optional)"],"output_types":["branch creation confirmation (JSON with branch name, commit hash)","branch list (JSON array with branch names and current commits)","deletion confirmation (JSON with deleted branch name)"],"categories":["automation-workflow","tool-use-integration"],"confidence":0.5,"matches":0,"success_rate":0},{"id":"awesome-dolt__cap_8","uri":"capability://automation.workflow.tag.based.release.marking.and.version.pinning","name":"tag-based release marking and version pinning","description":"Provides MCP tools to create and query Git-like tags that mark specific commits as releases or milestones, enabling version pinning and release tracking. Implements tags as immutable references to commits, allowing clients to query database state at specific release versions without managing separate snapshots.","intents":["I want to tag the current database state as a release version for production deployment","I need to query the database as it was at a specific release tag","I want to list all release tags and their associated commits","I need to create a tag for a specific commit for auditing purposes"],"best_for":["teams managing database releases and version control","developers pinning database schemas to application versions","LLM agents tracking database state across application releases"],"limitations":["Tags are immutable; cannot be modified after creation (must delete and recreate)","No automatic tag cleanup; old tags must be explicitly deleted","Tag names must follow Git naming conventions"],"requires":["Dolt repository with commits to tag","Write permissions to create/delete tags"],"input_types":["tag name (string)","commit hash (string, optional; defaults to HEAD)","tag message (string, optional)"],"output_types":["tag creation confirmation (JSON with tag name, commit hash, timestamp)","tag list (JSON array with tag names and associated commits)","tag deletion confirmation"],"categories":["automation-workflow","tool-use-integration"],"confidence":0.5,"matches":0,"success_rate":0},{"id":"awesome-dolt__cap_9","uri":"capability://automation.workflow.working.directory.state.management.and.commit.staging","name":"working directory state management and commit staging","description":"Provides MCP tools to inspect the current working directory state, stage changes, and create commits with custom messages. Implements staging via Dolt's index system, where changes are accumulated before being committed as an atomic unit with a commit message.","intents":["I want to see what changes have been made to the database since the last commit","I need to stage specific table changes and commit them with a descriptive message","I want to discard uncommitted changes and revert to the last commit","I need to create a commit with a specific message for audit purposes"],"best_for":["developers making intentional database changes with descriptive commit messages","teams requiring audit trails of who changed what and when","LLM agents automating database modifications with tracked changes"],"limitations":["Staging is at the table level; cannot stage individual rows or columns","Commit messages are free-form text; no structured metadata support","No support for partial commits or cherry-picking specific changes"],"requires":["Dolt repository with uncommitted changes","Write permissions to create commits"],"input_types":["commit message (string)","table names to stage (string array, optional; defaults to all changed tables)"],"output_types":["working directory status (JSON with modified, added, deleted tables)","commit confirmation (JSON with commit hash, message, timestamp, author)"],"categories":["automation-workflow","tool-use-integration"],"confidence":0.5,"matches":0,"success_rate":0}],"trust":{"score":28,"verified":false,"data_access_risk":"high","permissions":["Dolt CLI installed and in PATH","Initialized Dolt repository with at least one commit","MCP client compatible with tool-calling protocol","Dolt repository with multiple branches created","SQL query syntax compatible with Dolt's MySQL dialect","MCP client with stateful connection management","Dolt repository with commit history","Sufficient disk space for snapshot materialization","Write permissions to the Dolt working directory for rollback operations","Dolt repository with multiple branches to merge"],"failure_modes":["Diff computation scales linearly with row count; large tables (>1M rows) may incur latency","No built-in support for diffing computed columns or views across versions","Requires Dolt binary and initialized Dolt repository; cannot work with standard SQL databases","Branch switching incurs file I/O overhead; rapid context switching between many branches may cause latency spikes","No automatic query optimization across branches; each branch uses its own index statistics","Concurrent writes to different branches require explicit merge conflict resolution; no automatic three-way merge for data","Rollback is a logical operation that rewrites the working directory; large databases (>10GB) may take minutes","No point-in-time recovery for in-flight transactions; rollback is at commit granularity only","Snapshot queries require materializing the full table state in memory for large tables","Merge conflict resolution is schema-aware but not semantically aware; cannot resolve conflicts based on business logic","builder identity is not verified yet","no observed match outcomes yet"],"rank_breakdown":{"adoption":0.05,"quality":0.3,"ecosystem":0.39999999999999997,"match_graph":0.25,"freshness":0.6,"weights":{"adoption":0.25,"quality":0.25,"ecosystem":0.15,"match_graph":0.23,"freshness":0.12}},"observed_outcomes":{"matches":0,"success_rate":0,"avg_confidence":0,"top_intents":[],"last_matched_at":null},"maintenance":{"status":"active","updated_at":"2026-06-17T09:51:03.038Z","last_scraped_at":"2026-05-03T14:00:15.503Z","last_commit":null},"community":{"stars":null,"forks":null,"weekly_downloads":null,"model_downloads":null,"model_likes":null}},"distribution":{"claim_url":"https://unfragile.ai/submit?claim=dolt","compare_url":"https://unfragile.ai/compare?artifact=dolt"}},"signature":"/ZvjcWd7UxzYMyF76isIP+UQTyaWYIzfQeLrrx7deeovp4VlcNa4xZEhC5jbaSoVZftfD8Dttms5vW67WpcHCA==","signedAt":"2026-06-20T19:46:00.438Z","signedBy":"unfragile.ai","version":1},"_links":{"self":"https://unfragile.ai/api/v1/passport/dolt","artifact":"https://unfragile.ai/dolt","verify":"https://unfragile.ai/api/v1/verify?slug=dolt","publicKey":"https://unfragile.ai/api/v1/trust-passport-public-key","spec":"https://unfragile.ai/trust","schema":"https://unfragile.ai/schema.json","docs":"https://unfragile.ai/docs"}}