INDIVIDUAL MCP TOOL

run_data_job

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.

dpf-it.comnone authenticationAvailability not checked

LIVE ENDPOINT

https://api.dpf-it.com/mcp

No auth detected

Connect to this endpoint to inspect the live schema for run_data_job and invoke it with your own arguments.

{}

Potential side effects detected · medium confidence · heuristic, not a guarantee.

CONNECT WITH APPROVAL

Review this server and its permissions before adding it. Secret placeholders must be set locally.

Codex

~/.codex/config.toml

[mcp_servers.dpf-mcp-remote]
url = "https://api.dpf-it.com/mcp"
enabled = true

Claude Code

.mcp.json

{
  "mcpServers": {
    "dpf-mcp-remote": {
      "type": "http",
      "url": "https://api.dpf-it.com/mcp"
    }
  }
}

Claude Desktop

Settings → Connectors → Add custom connector

Name: dpf-mcp-remote
Remote MCP URL: https://api.dpf-it.com/mcp

Add this remote URL as a custom connector in Claude Desktop. Availability depends on the user plan and workspace policy.

Cursor

.cursor/mcp.json

{
  "mcpServers": {
    "dpf-mcp-remote": {
      "url": "https://api.dpf-it.com/mcp"
    }
  }
}

Visual Studio Code

.vscode/mcp.json

Add to Visual Studio Code

{
  "servers": {
    "dpf-mcp-remote": {
      "type": "http",
      "url": "https://api.dpf-it.com/mcp"
    }
  }
}

Generic MCP

Client-specific MCP configuration

{
  "name": "dpf-mcp-remote",
  "transport": "streamable-http",
  "url": "https://api.dpf-it.com/mcp"
}

MCP Inspector

Run the official MCP Inspector locally and enter the indexed Streamable HTTP endpoint.

list_my_workspaces — List every workspace the authenticated user has access to, including their permission on each.
create_workspace — Create a new workspace, owned by the authenticated user.
list_data — 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.
get_status — 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").
delete_data_spec — Permanently delete a data spec and its associated configuration.
submit_query — Run a SQL query against the Iceberg tables loaded into a workspace.
manage_connection — Create, list, test, or delete a workspace connection to an external data source.
manage_trigger — Create, list, update, delete, or fire a workspace job trigger.