Chroma’s official MCP server: vector search and collection management for RAG workflows.
Nothing to run from here
Dpf It 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.
18
tools declared
—
trust score
remote
at its publisher
—
calls last 7d
What it does
AI-powered data integration platform. Onboard users and run DPF data workflows.
Quickstart
# 1 — add it to Claude Code
claude mcp add --scope user --transport http dpf-it-mcp https://api.dpf-it.com/mcp
# 2 — ask your agent for something these tools do
# list_my_workspaces, create_workspace, list_data and 15 more
Dpf It costs nothing on mcprush: there is no plan to choose here, no cap to set and nothing mcprush can bill you for.
Publishernot claimed
DIAll 1 server
dpf-it1 server
1 category
Collected from a public index. Nobody has claimed this account, so nothing here was written by its author — claim it if it is yours.
Installation
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.
Claude Codedeclared by this listing
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 dpf-it-mcp https://api.dpf-it.com/mcpReconnect, or start a new session, and the tools appear in the model’s tool list.
Free on mcprush, and it answers at its publisher’s own address: this marketplace is not in the path, so there is no key of ours to hold and no card to add.
What it writes
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.
What you approve
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 every workspace the authenticated user has access to, including their permission on each.
No parameter schema on file.
Create a new workspace, owned by the authenticated user. Use this if list_my_workspaces returns none.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| name | string | yes | Workspace name |
| description | string | no | Optional workspace description. |
List either the data specs (parsing + mapping rule sets, resource: "specs") or the data processing jobs (executions of a spec, resource: "jobs") defined in a workspace. Each spec includes its specId and current status — poll a specific one with get_status. Both resources are paginated (default 25/page, max 100, newest first); pass the returned nextCursor to fetch more. A spec row also carries its
| Parameter | Type | Required | Notes |
|---|---|---|---|
| workspaceId | string | no | Workspace to act on. Defaults to your only workspace if you have exactly one. |
| resource | string | yes | Which kind of resource to list |
| pageSize | integer | no | Records per page (default 25). |
| cursor | string | no | Opaque nextCursor from a prior page (omit for the first page). |
Poll the status of either a data spec's own process (schema inference + code generation, run by start-analysis — pass specId, reaches "ready" or "failed") or a data-load job (pass jobId, reaches "complete" or "failed"). Pass exactly one of specId or jobId. Right after create-spec/update-spec + start-analysis, poll by specId; once that reaches "ready", its response's lastJobId (if present) points a
| Parameter | Type | Required | Notes |
|---|---|---|---|
| workspaceId | string | no | Workspace to act on. Defaults to your only workspace if you have exactly one. |
| specId | string | no | Poll a data spec's analysis status. Pass exactly one of specId or jobId. |
| jobId | string | no | Poll a data-load job's status. Pass exactly one of specId or jobId. |
Permanently delete a data spec and its associated configuration.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| workspaceId | string | no | Workspace to act on. Defaults to your only workspace if you have exactly one. |
| specName | string | yes | Name of the data spec to delete. |
Run a SQL query against the Iceberg tables loaded into a workspace. To list the tables that actually exist in the workspace, run SHOW TABLES — this is the authoritative source (unlike list_data's specs, which describe pipelines, not live tables). Qualified table references (catalog/schema prefixes, e.g. information_schema.tables) are rejected; reference tables by name only. Table functions that
| Parameter | Type | Required | Notes |
|---|---|---|---|
| workspaceId | string | no | Workspace to act on. Defaults to your only workspace if you have exactly one. |
| sql | string | yes | SQL query, e.g. SELECT * FROM customers LIMIT 10 |
Create, list, test, or delete a workspace connection to an external data source. Two types are supported: "sftp" and "aws_s3". For sftp, create generates a keypair and returns the public key — it must be installed in the remote server's authorized_keys before test (or a trigger using this connection) will succeed. For aws_s3, create generates an ExternalId and returns a trustPolicy plus dpfPrincip
| Parameter | Type | Required | Notes |
|---|---|---|---|
| workspaceId | string | no | Workspace to act on. Defaults to your only workspace if you have exactly one. |
| action | string | yes | Which operation to perform. |
| type | string | no | Connection type. Required for create; defaults to "sftp". |
| hostname | string | no | sftp only. Remote server hostname. Required for create. |
| username | string | no | sftp only. Remote username. Optional for create; defaults to "sftpuser". |
| roleArn | string | no | aws_s3 only. The IAM role the customer will create/update. Required for create. |
| connectionId | string | no | Existing connection to test or delete. Required for test/delete. |
Create, list, update, delete, or fire a workspace job trigger. Four types: - "sftp"/"aws_s3": pulls files from a connection (sftp: remote server; aws_s3: S3 bucket/prefix) into an already-analyzed data spec on a schedule (hourly/daily/monthly, UTC). Type must match the connection's type; aws_s3 also requires s3Bucket (s3Prefix optional). Natural-language preRules (which files to pick up) and postR
| Parameter | Type | Required | Notes |
|---|---|---|---|
| workspaceId | string | no | Workspace to act on. Defaults to your only workspace if you have exactly one. |
| action | string | yes | Which operation to perform. |
| triggerId | string | no | Existing trigger. Required for update/delete/run-now/clear-processed-files. |
| specName | string | no | The spec this trigger fires. Required for create. |
| connectionId | string | no | sftp/aws_s3 only. Connection to pull from. Required for create when type is "sftp"/"aws_s3". Also usable as a run-history filter. |
| type | string | no | Trigger type. Optional for create (defaults to "sftp"). For sftp/aws_s3 must match the connection's type. |
| s3Bucket | string | no | aws_s3 only. Bucket to poll. Required for create when type is "aws_s3", or to change it on update. Each run lists at most 5000 objects from the bucket/prefix (oldest key first) — past that, new files |
| s3Prefix | string | no | aws_s3 only. Optional key prefix; defaults to the whole bucket. |
| frequency | object | no | Required for create when type is "sftp", "aws_s3", or "schedule"; optional on update to change the schedule. Not applicable to spec_success. |
| upstreamSpecName | string | no | spec_success only. The spec whose successful job completion fires this trigger. Required for create when type is "spec_success". |
| preRules | string | no | sftp/aws_s3 only. Natural language: which files to pick up (e.g. "only *.csv under /outbound"). |
| postRules | string | no | sftp/aws_s3 only. Natural language: what to do after a file loads (e.g. "rename with .done suffix"). |
| dedupe | boolean | no | sftp/aws_s3 only. Required for create — ask the user rather than assuming a value; do not default it silently. Whether repeat pulls should skip files already loaded into this spec, matched by file nam |
| enabled | boolean | no | Whether the trigger is active. Defaults to true on create. |
| specId | string | no | run-history: filter to runs of triggers feeding this spec. |
| pageSize | integer | no | run-history: records per page (default 25). |
| cursor | string | no | run-history: opaque nextCursor from a prior page (omit for the first page). |
| startTime | string | no | run-history: ISO 8601 lower bound (inclusive) on when the run started. |
| endTime | string | no | run-history: ISO 8601 upper bound (inclusive) on when the run started. |
First step of setting up a new data integration: creates a data spec. By default (sourceType "file") this returns presigned upload URL(s) for the sample file (and optional format/target-schema file). Creating the spec does NOT upload anything: you must PUT each file to its URL yourself (or have the user attach it so your platform can), confirm the PUT returned HTTP 200, and only then call finish_d
| Parameter | Type | Required | Notes |
|---|---|---|---|
| workspaceId | string | no | Workspace to act on. Defaults to your only workspace if you have exactly one. |
| specName | string | yes | Name for the new data spec. |
| description | string | no | Optional description of the data spec. |
| sourceType | string | no | Defaults to "file" (upload a sample file). Use "tables" to query existing workspace table(s) — see sourceTables — instead of loading a new file. Use "compaction" to bin-pack the small data files of ex |
| sourceTables | array | no | Names of existing workspace tables. Required for sourceType "tables" (the tables the generated query reads from) and for sourceType "compaction" (the tables to compact). |
| expirePriorSnapshots | boolean | no | sourceType "compaction" only, default false. When false the job commits the compacted files and changes nothing else — prior snapshots still reference the replaced files, so no storage is freed. When |
| targetOption | string | no | Where transformed data should land — works the same for both sourceType values: "auto-infer" (default) lets the AI design the target table (for sourceType "tables", it designs the schema and the query |
| targetTables | array | no | Names of existing workspace tables to target — exactly one entry for sourceType "tables" (the generated query has a single target), one or more for sourceType "file". Required when targetOption is "ex |
| targetSchemaFileName | string | no | File name of a target schema file. Required when targetOption is "target-schema-file", for either sourceType. |
| sampleFileName | string | no | sourceType "file" only (and required for it). File name of the sample data file (e.g. "customers.csv") — used to derive content-type, not read from disk. |
| formatFileName | string | no | sourceType "file" only. File name of an optional format spec file. |
| merge | boolean | no | Upsert instead of plain append when true (default false). For sourceType "tables": generates a MERGE statement instead of an INSERT — use true for a running aggregate/summary that updates existing row |
| additionalPrompt | string | no | Instructions for the AI. For sourceType "tables", describe what the query should compute from the source table(s) (e.g. "count signups per day per region"). This is stored on the spec verbatim and reu |
| autoRefresh | string | no | sourceType "tables" only. Required for it — ask the user rather than assuming, and do not infer this from other jobs/triggers already in the workspace (a similar existing pipeline is not the user's an |
| autoRefreshUpstreamSpecName | string | no | Required when autoRefresh is "spec_success". The spec whose successful job completion should re-run this one. |
| autoRefreshFrequency | object | no | Required when autoRefresh is "schedule". |
Call ONLY after the file(s) returned by onboard_data_source have actually been uploaded (each PUT returned HTTP 200) — kicks off AI analysis and waits until the spec reaches "ready" or "failed". This tool verifies the upload against storage before starting anything. If a file is not there it refuses, spends no credits, and returns a fresh upload URL plus the exact curl command — complete the uplo
| Parameter | Type | Required | Notes |
|---|---|---|---|
| workspaceId | string | no | Workspace to act on. Defaults to your only workspace if you have exactly one. |
| specId | string | yes | specId returned by onboard_data_source. |
| specName | string | yes | Name of the data spec being onboarded. |
| loadSampleData | boolean | no | Whether to load the sample file and trigger the data-load job once analysis finishes (default true). |
Change an existing data spec's configuration. If no replacement file names are given, this runs synchronously (no upload needed): saves changes and — by default — re-runs AI analysis, returning the final status directly. If a replacement sample/format/target-schema file name IS given, this instead returns presigned upload URL(s); upload the file(s), then call finish_data_spec_update. Only pass the
| Parameter | Type | Required | Notes |
|---|---|---|---|
| workspaceId | string | no | Workspace to act on. Defaults to your only workspace if you have exactly one. |
| specName | string | yes | Name of the existing data spec to update |
| description | string | no | New description for the spec. Omit to keep the current value. |
| targetOption | string | no | Change where transformed data lands. Omit to keep the current setting. |
| targetTables | array | no | sourceType "file" specs: new list of existing workspace tables to load into. Required when setting targetOption to "existing-tables". sourceType "tables" specs: the query's single target table name — |
| targetSchemaFileName | string | no | File name of a replacement target schema file. Required when setting targetOption to "target-schema-file". Replacing this re-derives the whole mapping against the stored sample/format files — re-send |
| sampleFileName | string | no | sourceType "file" specs only. File name of a replacement sample data file. Send this whenever the source data the user is describing differs in any way from the stored sample — the regenerated parser |
| formatFileName | string | no | sourceType "file" specs only. File name of a replacement format spec file. The format spec outranks the sample when deriving field boundaries, so re-send it alongside a replacement sample rather than |
| sourceTables | array | no | sourceType "tables" specs only: replacement list of source tables the generated query reads from. |
| merge | boolean | no | Whether new data should merge/upsert into existing rows rather than append. For sourceType "tables" also changes the generated SQL between MERGE and INSERT. |
| computeSize | string | no | Compute size for analysis/processing. Omit to keep the current setting. |
| additionalPrompt | string | no | Extra natural-language guidance for the AI schema inference/mapping. Replaces the previously stored value when given (omit to keep it as-is), and is reused on every future re-analysis — keep it to ins |
| loadSampleData | boolean | no | Whether re-analysis should also trigger the data-load job (default true). Only used when runAnalysis is true. |
| runAnalysis | boolean | no | Whether to run analysis and wait for it after saving the changes (default true). Only applies to the synchronous (no-file-change) path. |
| confirmedCurrentInputs | boolean | no | Required (true) whenever this update changes something that feeds AI code generation and analysis will run. It asserts that you have read the spec's stored input set (list_data, resource: "specs"), ch |
Call ONLY after the file(s) returned by update_data_spec have actually been uploaded (each PUT returned HTTP 200) — kicks off AI analysis and waits until the spec reaches "ready" or "failed". The upload is verified against storage first: if a file is missing this refuses, spends no credits, and hands back a fresh upload URL with the curl command to use. If it returns before the spec settles (timed
| Parameter | Type | Required | Notes |
|---|---|---|---|
| workspaceId | string | no | Workspace to act on. Defaults to your only workspace if you have exactly one. |
| specId | string | yes | specId returned by update_data_spec. |
| specName | string | yes | Name of the data spec being updated. |
| runAnalysis | boolean | no | Default true — set false to skip analysis and just confirm the upload. |
| loadSampleData | boolean | no | Whether analysis should also trigger the data-load job (default true). |
First step of processing new data files through an already-configured data spec: creates a job and returns presigned upload URL(s) for each file. Upload the file(s) per the returned instructions, then call finish_data_job with the returned jobId to start processing and wait for it to complete. Do NOT call this right after onboard_data_source/finish_data_source_onboarding or update_data_spec/finis
| Parameter | Type | Required | Notes |
|---|---|---|---|
| workspaceId | string | no | Workspace to act on. Defaults to your only workspace if you have exactly one. |
| specName | string | yes | Name of the already-configured data spec to process files through. |
| fileNames | array | yes | File names of the data files to process (e.g. ["jan.csv", "feb.csv"]) |
Call after uploading the file(s) returned by run_data_job — starts processing and waits until the job completes or fails. If it returns before that (timedOut: true), do NOT call this tool again just to keep checking — that re-attempts starting the job. Poll with get_status (jobId) instead until it reaches a terminal status.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| workspaceId | string | no | Workspace to act on. Defaults to your only workspace if you have exactly one. |
| jobId | string | yes | jobId returned by run_data_job. |
| specName | string | yes | Name of the data spec this job belongs to. |
End-to-end workflow for "pull files from this SFTP server / S3 bucket on a schedule" requests: reuses a matching connection if one already exists in the workspace (same hostname/username for sftp, same roleArn for aws_s3), otherwise creates one; tests it; then creates a trigger that feeds an already-analyzed data spec (see onboard_data_source) on the given frequency. Pass hostname for an sftp pull
| Parameter | Type | Required | Notes |
|---|---|---|---|
| workspaceId | string | no | Workspace to act on. Defaults to your only workspace if you have exactly one. |
| hostname | string | no | sftp: SFTP server hostname to pull from. |
| username | string | no | sftp only. Defaults to "sftpuser". |
| roleArn | string | no | aws_s3: the IAM role the customer will create/update. |
| s3Bucket | string | no | aws_s3: bucket to poll. Required when roleArn is given. |
| s3Prefix | string | no | aws_s3 only. Optional key prefix; defaults to the whole bucket. |
| specName | string | yes | Already-analyzed data spec to load files into (see onboard_data_source) |
| frequency | object | yes | Pull schedule. |
| preRules | string | no | Natural language: which files to pick up (e.g. "only *.csv under /outbound") |
| postRules | string | no | Natural language: what to do after a file loads (e.g. "rename with .done suffix") |
| dedupe | boolean | no | Required — ask the user rather than assuming a value; omitting it fails the call. Whether repeat pulls should skip files already loaded into this spec, matched by file name. Has real consequences: wit |
Escape hatch for DPF capabilities that don't have a dedicated tool yet. ALWAYS prefer a dedicated tool when one exists — get_status, list_data, submit_query, delete_data_spec, onboard_data_source, update_data_spec, run_data_job, manage_connection, manage_trigger, setup_scheduled_pull, list_my_workspaces, create_workspace — and reach for this only when none of those fit (e.g. "how many credits do I
| Parameter | Type | Required | Notes |
|---|---|---|---|
| path | string | yes | API path, e.g. "/auth/billing" (leading slash, no query string). |
| action | string | yes | The "action" field this endpoint routes on, e.g. "get-balance". |
| workspaceId | string | no | Include for workspace-scoped actions. Omit entirely for account-level actions. |
| params | object | no | Additional action-specific fields to merge into the request body alongside action/workspaceId. |
Returns instructions for creating a DPF account, verifying its email, resending the verification code, or resetting a forgotten password — it never performs these itself and never asks for a password. A password typed into this chat would sit in the conversation transcript, so every action instead returns the DPF website's own form, or a curl command that reads the password from a shell variable t
| Parameter | Type | Required | Notes |
|---|---|---|---|
| action | string | yes | — |
| string | yes | — | |
| firstName | string | no | action "register" only |
| lastName | string | no | action "register" only |
| termsAccepted | boolean | no | action "register" only. Must be true. |
| otp | string | no | action "verify" and "reset-password" only. The 6-digit code from the email DPF sent. |
Send a message to the DPF team — request a demo, ask about licensing, report an issue, or request a feature. No authentication required. Always ask the user for their email if they have not already given it in this conversation.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| reason | string | yes | — |
| message | string | yes | — |
| string | yes | The sender's email address, so DPF can reply. | |
| name | string | no | — |
Free
$0 forever
- 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 Dpf It or to call it, at any volume.
Call allowance · this installenforced at the gateway
Monthly allowance, in calls
—
—
Alert at 80% · then the tool returns a normal MCP error
Used this month: —
—Grade not published
No rule-by-rule report on file for this release
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.0.0.
1.0.0
undated
latestNo release note was published with this version.
—
no reviews yet
Who can review
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.
Sign in to write one
Any signed-in account that does not publish Dpf It can review it, once — before installing it or after. A review from an account that has installed it is marked as one.
No reviews yet
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.