mfs-ingestlisted

Register, update, or re-sync data sources for MFS so they become searchable — postgres / mysql / mongo / snowflake / bigquery, github / jira / linear / notion / hubspot / zendesk, slack / discord / gmail / feishu, s3 / gdrive / web / file. Use whenever the user wants to ADD a new data source to MFS, change an existing connector's config, re-ingest / re-index a source, list registered connectors, or troubleshoot a sync that's not picking up data. Trigger phrases include "add X to MFS", "ingest my [postgres/slack/github/etc]", "register this repo / database / workspace", "make X searchable", "re-sync Y", "update the slack token", "what connectors do I have". Do NOT use for: searching / finding / reading content (use `mfs-find`); raw mutation of the source itself (MFS only reads).
zilliztech/mfs · ★ 70 · AI & Automation · score 88

Install: claude install-skill zilliztech/mfs

# MFS — register / update / re-sync data sources ## 1. What this skill does Walks the user through getting a data source into MFS so it's searchable. The work splits into: 1. Picking the right connector scheme. 2. Collecting credentials (preferring `env:VAR` / `file:/path` indirection over plaintext). 3. Writing a connector TOML. 4. Calling `mfs add <uri> --config <toml>` and monitoring the returned job. Each connector has its own field set, credential acquisition story, and gotchas. Per-connector details live in `reference/connectors/<scheme>.md` — **read the matching one before collecting fields** for any scheme. ## Step 0: Pre-flight (always run first) ```bash mfs --version # missing? `cargo install mfs-cli` (see install row below) mfs status # server reachable? connectors/jobs visible? mfs config show # endpoint/profile/client id/server-info debugging mfs connector list # what's already configured? ``` Branch on the result: | Signal | Action | |---|---| | `mfs` not found | install the CLI (Rust): `cargo install mfs-cli`, or the shell installer from the project's GitHub releases page. | | `mfs status` connection refused | the configured server is down. Tell the user how to bring it up — pre-release, the server runs from source: `git clone https://github.com/zilliztech/mfs.git && cd mfs/server/python && uv sync && uv run mfs-server setup && uv run mfs-server run` — and wait. Work only through the configured endpoint rather