dagster-mono-mcp
dagster-mono-mcp
Dagster 用の単一ツール MCP サーバーです。1つのツールで5つのアクションを実行でき、トークンオーバーヘッドを最小限に抑えます。
Dagsterには公式のMCPサーバーがありますが、導入が困難でした。これは、LLMでパイプラインをデバッグする際に実際に必要となるアクション(実行リストの取得、実行詳細の確認、ログの読み取り、およびその他のすべてのためのRaw GraphQL)をカバーする最小限の代替手段です。
Zero Trustの背後にあるDagsterインスタンス向けにCloudflare Accessをサポートしており、Dagsterインスタンスを簡単かつ無料で保護できます。
インストール
Claude Code
プロジェクトスコープ(プロジェクトルートの .mcp.json):
{
"mcpServers": {
"dagster": {
"command": "npx",
"args": ["-y", "github:pjatx/dagster-mono-mcp"],
"env": {
"DAGSTER_GRAPHQL_URL": "https://dagster.example.com/graphql",
"CF_ACCESS_CLIENT_ID": "your-client-id",
"CF_ACCESS_CLIENT_SECRET": "your-client-secret"
}
}
}
}グローバル(~/.claude.json — すべてのプロジェクトで利用可能):
{
"mcpServers": {
"dagster": {
"command": "npx",
"args": ["-y", "github:pjatx/dagster-mono-mcp"],
"env": {
"DAGSTER_GRAPHQL_URL": "https://dagster.example.com/graphql"
}
}
}
}Cursor
プロジェクトルートの .cursor/mcp.json に追加:
{
"mcpServers": {
"dagster": {
"command": "npx",
"args": ["-y", "github:pjatx/dagster-mono-mcp"],
"env": {
"DAGSTER_GRAPHQL_URL": "https://dagster.example.com/graphql",
"CF_ACCESS_CLIENT_ID": "your-client-id",
"CF_ACCESS_CLIENT_SECRET": "your-client-secret"
}
}
}
}Windsurf
~/.codeium/windsurf/mcp_config.json に追加:
{
"mcpServers": {
"dagster": {
"command": "npx",
"args": ["-y", "github:pjatx/dagster-mono-mcp"],
"env": {
"DAGSTER_GRAPHQL_URL": "https://dagster.example.com/graphql",
"CF_ACCESS_CLIENT_ID": "your-client-id",
"CF_ACCESS_CLIENT_SECRET": "your-client-secret"
}
}
}
}Related MCP server: MCP Access OAuth Server
環境変数
変数 | デフォルト | 必須 |
|
| いいえ |
| — | いいえ (CF Accessの背後にある場合は必須) |
| — | いいえ (CF Accessの背後にある場合は必須) |
使用方法
アクションディスパッチを備えた単一ツール dagster:
実行リストの取得
{"action": "runs"}
{"action": "runs", "status": "FAILURE"}
{"action": "runs", "job": "my_job", "limit": 5}実行詳細
{"action": "run", "id": "<run-id>"}イベントログ
{"action": "logs", "id": "<run-id>"}
{"action": "logs", "id": "<run-id>", "limit": 100}Raw GraphQL
{"action": "graphql", "query": "{ version }"}
{"action": "graphql", "query": "query($id: ID!) { runOrError(runId: $id) { __typename } }", "variables": {"id": "abc123"}}ヘルプ
{"action": "help"}利用可能なステータス、すべてのパラメータ、クエリ例を含む完全なドキュメントを返します。
設計
このプロジェクトはモノツールパターンに従っています。多数の小さなツールではなく、アクションディスパッチを備えた1つのMCPツールを採用しています。ツールが少ないほどLLMのトークンオーバーヘッドが減り、ツール選択が単純化されます。モデルは似たような名前の多数のツールから選択する必要がありません。LLMとMCPサーバーの対話方法を再考したCloudflareのCode Modeの記事に触発されています。
開発
npm install
npm run build # esbuild bundle -> dist/index.js
npm start # run the MCP server (stdio transport)ライセンス
MIT
Available Tools
1 tooldagsterC
Dagster runs & debugging. Actions: runs, run, logs, graphql, help
{"action": "runs"} -> recent runs {"action": "runs", "status": "FAILURE"} -> failed runs {"action": "run", "id": "abc123"} -> run details {"action": "logs", "id": "abc123"} -> run logs {"action": "graphql", "query": "{ version }"} -> raw GraphQL {"action": "help"} -> full documentation
Inputs: action (required), id, job, status, +3 more.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
TDQS
Scored across 1 tool
The single tool 'dagster' has clearly distinct actions (runs, run, logs, graphql, help) with no overlap in purpose. Each action targets a specific operation within the Dagster domain, making misselection impossible.
The tool naming is perfectly consistent as there is only one tool, 'dagster', and its actions follow a clear, uniform pattern (e.g., 'runs', 'run', 'logs') without any mixing of conventions or styles.
With only one tool, the server feels thin for a Dagster monitoring/debugging domain, as it bundles multiple distinct operations (e.g., querying runs, fetching logs, GraphQL) into a single tool. This may limit clarity and usability compared to a more granular tool set.
The tool covers core operations like retrieving runs, logs, and GraphQL queries, but lacks obvious lifecycle actions such as triggering new runs, pausing/resuming, or managing assets. This creates notable gaps for a full Dagster debugging workflow.
Maintenance
Related MCP Connectors
MCP server for AI agents to plan, verify, and deploy Cloudflare-native apps.
Zero-dependency Cloudflare Worker gateway turning websites and REST APIs into MCP tools.
Cloudflare Workers MCP server: ai-cost-optimizer
An MCP server that provides an API to LLMs to manage their JumpCloud resources.
Related MCP Servers
- FlicenseNot gradedqualityNot gradedmaintenanceA Cloudflare Workers-based MCP server that enables deployment of custom tools accessible via the Model Context Protocol without authentication requirements.-
- FlicenseNot gradedqualityCmaintenanceA Cloudflare Workers-based MCP server that enables secure remote connections using built-in OAuth authentication via Cloudflare Access. It provides identity-based access control for MCP tools and supports persistent state management through Durable Objects and SSE.-
- FlicenseNot gradedqualityDmaintenanceRemote MCP server with built-in OAuth authentication via Cloudflare Access, enabling secure tool invocation after user sign-in.-
- FlicenseNot gradedqualityNot gradedmaintenanceThis is an MCP server deployed on Cloudflare Workers with OAuth authentication, enabling remote MCP clients to connect and use tools.-