Bring Workflow Automation
to Claude Code
Learn how to connect Kissflow to Claude Code and start using 9 AI agent tools in minutes. Fully managed, enterprise secure, and ready to use without writing a single line of code.
What is the Kissflow MCP Server?
Connect your Kissflow account to any AI agent and manage workflows through natural conversation.
What you can do
- Process Management — List and inspect automated workflows and processes
- Request Tracking — Browse, create, and update requests within processes
- Form Access — View form fields and data schemas for each process
- Approval Monitoring — Track pending approvals and their status
- Data Access — Query process data with filters and pagination
How it works
1. Subscribe to this server
2. Enter your Kissflow Access Key ID, Secret Access Key, Subdomain, and Account ID
3. Start managing workflows from Claude, Cursor, or any MCP-compatible client
Who is this for?
- Operations — manage automated workflows and track requests
- Managers — monitor approvals and process bottlenecks
- IT Teams — access process data and configuration
Built-in capabilities (9)
Essential for reviewing detailed profile information. Get details for a specific user
Use this to export or review collected form data. List entries within a dataform
Dataforms are used for data collection without complex workflow logic. List all dataforms
Essential for querying master data or reference tables. List records within a dataset
Datasets serve as central tables for master data management. List all datasets
Useful for managing access control. List user groups
Useful for tracking the progress of individual flow requests. List items within a process
Processes are used to manage multi-step business logic. List all workflow processes
Use this to identify user IDs and email addresses. List all Kissflow users
Why Claude Code?
Claude Code registers Kissflow as an MCP server in a single terminal command. Once connected, Claude Code discovers all 9 tools at runtime and can call them headlessly. ideal for CI/CD pipelines, cron jobs, and automated workflows where Kissflow data drives decisions without human intervention.
- —
Single-command setup:
claude mcp addregisters the server instantly. no config files to edit or applications to restart - —
Terminal-native workflow means MCP tools integrate seamlessly into shell scripts, CI/CD pipelines, and automated DevOps tasks
- —
Claude Code runs headlessly, enabling unattended batch processing using Kissflow tools in cron jobs or deployment scripts
- —
Built by the same team that created the MCP protocol, ensuring first-class compatibility and the fastest adoption of new protocol features
Kissflow in Claude Code
Kissflow and 3,400+ other MCP servers. One platform. One governance layer.
Teams that connect Kissflow to Claude Code through Vinkius don't need to source, host, or maintain individual MCP servers. Every tool call runs inside a hardened runtime with credential isolation, DLP, and a signed audit chain.
Raw MCP | Vinkius | |
|---|---|---|
| Server catalog | Find and host yourself | 3,400+ managed |
| Infrastructure | Self-hosted | Sandboxed V8 isolates |
| Credential handling | Plaintext in config | Vault + runtime injection |
| Data loss prevention | None | Configurable DLP policies |
| Kill switch | None | Global instant shutdown |
| Financial circuit breakers | None | Per-server limits + alerts |
| Audit trail | None | Ed25519 signed logs |
| SIEM log streaming | None | Splunk, Datadog, Webhook |
| Honeytokens | None | Canary alerts on leak |
| Custom domains | Not applicable | DNS challenge verified |
| GDPR compliance | Manual effort | Automated purge + export |
Why teams choose Vinkius for Kissflow in Claude Code
The Kissflow MCP Server runs on Vinkius-managed infrastructure inside AWS — a purpose-built runtime with per-request V8 isolates, Ed25519 signed audit chains, and sub-40ms cold starts. All 9 tools execute in hardened sandboxes optimized for native MCP execution.
Your AI agents in Claude Code only access the data you authorize, with DLP that blocks sensitive information from ever reaching the model, kill switch for instant shutdown, and up to 60% token savings. Enterprise-grade infrastructure, zero maintenance.
* Every MCP server runs on Vinkius-managed infrastructure inside AWS - a purpose-built runtime with per-request V8 isolates, Ed25519 signed audit chains, and sub-40ms cold starts optimized for native MCP execution. See our infrastructure
How Vinkius secures
Kissflow for Claude Code
Every tool call from Claude Code to the Kissflow MCP Server is protected by DLP redaction, cryptographic audit chains, V8 sandbox isolation, kill switch, and financial circuit breakers.
Frequently asked questions
Can I create and track requests within processes?
Yes. Create new requests within any process, update request data, and track them through workflow stages including pending approvals.
Does Kissflow require four credentials?
Yes. Kissflow requires Access Key ID, Secret Access Key, Subdomain, and Account ID. Requests go to https://{subdomain}.kissflow.com/v1/{accountId}/.
Can I monitor pending approvals?
Yes. Track all pending approvals across processes with assignee, status, and deadline information.
How do I add an MCP server to Claude Code?
Run claude mcp add --transport http "" in your terminal. Claude Code registers the server and discovers all tools immediately.
Can Claude Code run MCP tools in headless mode?
Yes. Claude Code supports non-interactive execution, making it ideal for scripts, cron jobs, and CI/CD pipelines that need MCP tool access.
How do I list all connected MCP servers?
Run claude mcp in your terminal to see all registered servers and their status, or type /mcp inside an active Claude Code session.
Command not found: claude
Ensure Claude Code is installed globally: npm install -g @anthropic-ai/claude-code
Connection timeout
Check your internet connection and verify the Edge URL is reachable