A
licenseA
qualityD
maintenanceAI workflow orchestration platform with 100+ integrations, knowledge graph, and unified credits. Build, manage, and execute workflows from Claude Code, Cursor, or any MCP client.
40
359 npm
3
MIT
DPF
by dpf-admin
Related Servers
Alternatives to DPF
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityAmaintenanceEnables AI clients to discover, inspect, and run 2,000+ models and APIs through OAuth-backed MCP tools, including free data APIs and paid model calls.556,724 npmMIT
@matihlabs/mcpofficial
AlicenseNot gradedqualityDmaintenanceConnects AI clients to the Matih data platform, enabling SQL queries, table profiling, analytics, chart creation, and file uploads through MCP tools with OAuth/PKCE authentication.53 npmApache 2.0- AlicenseNot gradedqualityAmaintenanceEnables AI clients to discover, inspect, and run 2,000+ AI models and APIs through MCP, with free data APIs, OAuth sign-in, and rollback.556,724 npmMIT
- AlicenseNot gradedqualityBmaintenanceTurns Google Sheets, CSV, Excel, and Parquet files into durable, queryable data for AI agents. Lets clients securely discover datasets, inspect semantic models, run bounded analytics, and manage approved semantic overlays.Apache 2.0
- AlicenseNot gradedqualityDmaintenanceEnables automated dataset processing and onboarding using Google Drive integration. Provides metadata extraction, data quality assessment, and contract generation for CSV/Excel files through natural language interactions.1MIT
TDQS
A4.1/5.0
Scored across 16 tools
Disambiguation4/5
Each tool maps to a distinct workflow step or resource (query, workspace, spec, job, trigger, connection), and the finish_* helpers are clearly paired with their initiating tools. The main ambiguity is between list_data and submit_query, though the descriptions explicitly disambiguate them.
Naming Consistency4/5
Tool names are consistently snake_case and mostly verb-first, with clear patterns like finish_* pairing with onboard/update/run. The generic manage_ prefix on manage_connection and manage_trigger is a minor deviation from the more action-specific verbs used elsewhere.
Tool Count4/5
At 16 tools, the set is slightly above the typical 3-15 range, but the tools cover multiple distinct workflows including workspaces, specs, jobs, triggers, and connections. The finish_* helpers add count but serve necessary asynchronous continuation steps.
Completeness4/5
The tool surface covers the core data integration lifecycle end-to-end: workspace creation, spec onboarding/update/delete, job processing, triggers, scheduled pulls, status polling, and SQL querying. Minor gaps like workspace deletion or job cancellation are not exposed, but call_dpf_api partially offsets this and billing is intentionally left to the web UI.
Maintenance
ActivityStale
ResponsivenessNo issues