Mindflow MCP
Turn notes into explanations, tasks and structured work connected to Notion.
Our use of Claude spans service API workflows, parallel LLM processing, and software development. We connect that experience to MCP tools and the AI infrastructure we are building next.
Mindflow is one concrete Claude API workflow inside a wider portfolio. Across the products below, we use Claude and reusable Skills to move from problem definition to implementation, debugging, documentation, and workflow design. Runtime provider use is labeled separately from development use.
Turn notes into explanations, tasks and structured work connected to Notion.
Make multilingual symbol discovery and copying easier through a focused web service.
Turn public Path of Exile 2 economy data into searchable prices and history.
Make train and platform guidance easier to read for a specific travel route.
Generate a storefront’s content and visual direction from an industry and brief.
Explore tools that place useful game information near the player’s workflow.
Explore AI and sensor signals for unusual situations affecting people living alone.
Help young people learn financial products through onboarding and data workflows.
Problem or user input → service/API or data layer → model-assisted interpretation where appropriate → connected output or developer-facing interface → telemetry, review, and iteration. The exact model and runtime path depend on the product; all products are not represented as live Claude API services.
Mindflow is one concrete Claude API workflow inside a wider portfolio. Across the products below, we use Claude and reusable Skills to move from problem definition to implementation, debugging, documentation, and workflow design. Runtime provider use is labeled separately from development use.
Turn notes into explanations, tasks and structured work connected to Notion.
Make multilingual symbol discovery and copying easier through a focused web service.
Turn public Path of Exile 2 economy data into searchable prices and history.
Make train and platform guidance easier to read for a specific travel route.
Generate a storefront’s content and visual direction from an industry and brief.
Explore tools that place useful game information near the player’s workflow.
Explore AI and sensor signals for unusual situations affecting people living alone.
Help young people learn financial products through onboarding and data workflows.
Problem or user input → service/API or data layer → model-assisted interpretation where appropriate → connected output or developer-facing interface → telemetry, review, and iteration. The exact model and runtime path depend on the product; all products are not represented as live Claude API services.
BlueCL uses Claude API in running service workflows and parallel LLM processing. Claude and reusable Claude Skills also support our software development work.
| Area | Current use |
|---|---|
| Service API workflows | Claude API calls support AI features in our services. |
| Mindflow MCP | Implemented note summarization, task and deadline extraction, MCP tools, and Notion integration. |
| Parallel processing | Claude summarization runs alongside independent model and parsing tasks, with results combined into a connected workflow. |
| Development | Claude and reusable Skills support software development and API integration work. |
Mindflow addresses the manual handoff between understanding study notes, identifying tasks, and organizing the result in Notion. Claude supplies the explanatory study content inside a workflow connected to external tools.
POST /process and POST /process-file. The implementation uses the signed-in user’s Notion connection and destination database.title, task, and due JSON. These tasks do not wait for each other to start.Generate Markdown with headings, explanations, examples, common misunderstandings, and a final key-summary section. A separate Claude extraction tool returns task and due-date JSON. The source uses Claude Haiku 4.5 for these calls.
The Notion writer converts Markdown to blocks, appends them in batches of up to 100, and includes bounded retry/backoff logic for rate-limit and server-error responses. This is implemented handling, not a measured reliability guarantee.
Input: “Review database normalization, including 1NF and 2NF. Submit the comparison assignment by October 16, 2026.”
Claude branch → Markdown study notes: concepts, examples, key takeaways
Parallel extraction → {"title":"Normalization","task":"Compare 1NF and 2NF","due":"2026-10-16"}
Connected output → Notion page with study content + task/date metadata in the API responseAn illustrative product scenario, not a captured live response or benchmark. The implemented composite extractor’s prompt requests Korean output. Exact outputs vary with the input and configuration.
These endpoints belong to the Mindflow service implementation; the BlueCL company homepage is a separate site. Workflow code is implemented, with further product development and user validation continuing.
Our ongoing priorities are Korean-language summary quality, dependable task and deadline extraction, connected-tool reliability, and visibility into API latency and cost.
Evaluate summaries and extracted tasks against representative inputs.
Improve coordination, error handling, and recovery across model and tool calls.
Measure workflow timing and API usage to guide practical improvements.
Developers running several inference servers need to understand where requests go, which requests slow down, and how those observations relate to GPU server health. We are developing a real-time LLM load-balancing and GPU-monitoring product around that need.
The product direction brings request distribution and GPU observations into one dashboard. Its purpose is to help developers inspect their own model-serving environment with operational context.
A planned extension prepares selected metric snapshots and request context for Claude. Claude would explain the observations and propose investigation points alongside the underlying measurements. Provider integration is also planned.
This is the target design for the Claude extension, not a deployed feature.
| Layer | Responsibility | Status |
|---|---|---|
| Request distribution | Route LLM requests across inference servers. | In development |
| GPU monitoring | Collect and present server observations. | In development |
| Context preparation | Select operational metrics and request context for an explanation. | Planned Claude extension |
| Claude API | Return understandable explanations and suggested checks. | Planned |
| Developer control | Display measurements with explanations; developers decide how to respond. | Target design |
Claude is intended to support interpretation of operational information. The target extension keeps request routing and infrastructure controls separate from the language-model explanation step.
BlueCL is based in Mokpo, South Korea, and builds on a business established on February 24, 2023. Founder Dongju Kang develops software products and independently conducted research into MCP-based parallel LLM learning support and LLM-based website generation with visual editing.
South Korea business registration number: 494-52-00728
Two 2026 KSCI conference publications document these studies, with publication authors Soojung Lee and Dongju Kang.
Talk to us about AI workflows, connected tools, and LLM infrastructure.
bluecl@bluecl.cloud