@kissflow/sdk-mcp

A Model Context Protocol (MCP) server that exposes Kissflow SDK knowledge as callable tools for AI assistants (Claude, Cursor, etc.). Instead of guessing how the SDK works, the AI calls this server directly to get accurate, up-to-date answers.

Runs over stdio and is registered via .mcp.json at the repo root so Claude Code picks it up automatically on startup.

Architecture

AI Assistant (Claude)
       │  calls tools over MCP protocol
       ▼
  sdk-mcp server (index.ts)
       │
       ├── get_sdk_reference  →  data/reference.ts   (static SDK docs)
       ├── get_sdk_example    →  data/examples.ts    (runnable code snippets)
       └── scaffold_component →  tools/scaffold.ts   (React component generator)

Tools

get_sdk_reference

Returns API docs for a specific class or the full SDK.

Input: optional className — one of Dataform, Board, Process, Page, Popup, Component, Client, Formatter, Application, CustomComponent

Backed by data/reference.ts — a hand-authored data structure with every class, method, parameters, return types, and examples.

get_sdk_example

Fuzzy-matches a use-case phrase to a curated runnable code example.

Input: useCase string (e.g. "approve process task", "table with delete column")

Backed by data/examples.ts — a list of { useCase, description, code } objects.

scaffold_component

Generates a complete React component for a given flow and set of operations. Also returns required_inputs (values the user must supply, e.g. viewId for boards) and warnings.

Input: flowType (dataform | board | process), flowId, operations[] (list, create, update, delete, approve, submit, reject, archive)

tools/scaffold.ts contains three generator functions — generateDataformComponent, generateBoardComponent, generateProcessComponent — that programmatically build JSX strings based on which operations are requested.

File Structure

src/
├── index.ts              # MCP server entry — routes tool calls, formats output
├── tools/
│   ├── get-reference.ts  # Thin handler, delegates to reference.ts
│   ├── get-example.ts    # Fuzzy search over examples.ts
│   └── scaffold.ts       # React component code generator + input collector
└── data/
    ├── reference.ts      # Source of truth for all SDK docs
    └── examples.ts       # Curated runnable examples

dist/ contains the compiled output (committed, so no build step needed to use the server).

Development

# Build
npm run build

# Run directly
npm start

When updating SDK behaviour (e.g. response shapes, new methods), update data/reference.ts and data/examples.ts first, then regenerate scaffold.ts generated strings to match.