FlowZap - Not another Diagramming tool - Introducing the FlowZap MCP Server: The Fastest Path from LLM Agent to Interactive Diagrams

Overview

I just launched a public, robust MCP (Model Context Protocol) server at https://flowzap.xyz/api/mcp. Now, any agent—Claude, ChatGPT (custom functions), DeepSeek, Qwen, Grok, you name it—can generate, update, and hand off business process diagrams using a dead-simple JSON-RPC 2.0 API over HTTP. It’s secure, fast, and universal.

Why Build a Remote MCP for FlowZap?

Business process diagramming is collaborative, iterative, and (let’s face it) often annoyingly manual. FlowZap already lets you create, tweak, and collaborate on process flows with a modern UI and a code-friendly DSL. But with LLM agents becoming core to workflow automation, integration friction was a bottleneck—for us, and for every dev team trying to wire up their agent to a real diagramming backend.

We wanted to fix that for everyone, not just our own stack. No proprietary lock-in, no “wait for our plugin to launch”. Just: if your agent can speak JSON-RPC over HTTP, it can speak FlowZap—period.

Add FlowZap to Claude

Claude supports Custom Connectors via Remote MCP for Pro, Max, Team, and Enterprise plans. Note: As of September 2025, some users experience OAuth connection issues with Claude Desktop. If the connection doesn't persist after clicking "Connect", this is a known Claude Desktop issue. We're monitoring for updates from Anthropic.

Open Claude → Settings → Connectors → Add custom connector, then paste the FlowZap MCP base URL (from the Quickstart) and click Add.
After adding, enable the connector’s tools for the conversation; Claude can invoke them during chat and in Research mode when permitted.
Custom connectors are remote MCP servers, which means no local setup is required; the model securely calls FlowZap’s JSON‑RPC tools over HTTPS.
Anthropic recommends enabling only the specific tools needed, reviewing tool call requests, and using trusted servers—best practices that FlowZap MCP follows by design.
If building or extending connectors later, Claude also supports developer workflows for Remote MCP servers, so teams can iterate without changing end‑user setup.

Tip: Keep the user flow focused on “URL + FlowZap Code” so Claude users get a great preview and then head to FlowZap to register and save, which aligns with the conversion funnel outlined in this post.

Troubleshooting Claude Desktop Connection

If the connector shows “Disconnected” after setup:

This is a known issue with Claude Desktop's OAuth handling
Your browser may briefly show “success” but the connection won't persist
This is not an issue with the FlowZap MCP server
Alternative: Use the API directly with other LLM clients that support JSON‑RPC

Perplexity status (what works today)

Perplexity explicitly states that local MCP “connectors” are available on the Mac app today, and that Remote MCP (cloud‑hosted/custom servers) is “coming soon,” with rollout to paid subscribers first—so broader custom‑connector support is planned but not yet generally available on Windows/Web.

Local MCP on Perplexity Mac requires installing the Perplexity helper (PerplexityXPC) and then adding the MCP under Connectors; this path is documented and live now for macOS users.
For enterprise customers, Perplexity already offers App/File Connectors (e.g., Google Drive, OneDrive, Box) as managed integrations; these are curated first‑party connectors, not arbitrary custom servers.
Until Remote MCP rolls out on more platforms, Windows/Web users will only see the built‑in connector list, which matches what many users observe in the current UI.

The FlowZap MCP API in a Nutshell

Base: https://flowzap.xyz/mcp (browser landing)
SSE Connector: https://flowzap.xyz/mcp/api/sse

Health Check: GET /mcp/api/health
Example:

curl -s https://flowzap.xyz/mcp/api/health | jq

JSON-RPC Endpoint: POST /mcp/api/rpc — This is where you do the real work (tools/list, tools/call, etc.)
OpenAPI + Postman:
- OpenAPI stub — for quick schema discovery, and if you’re using tools like Swagger or Postman
- Postman collection — for hands-on API fiddling
Session UX: Returned Playground links are always public, clean, and expire after 5 minutes for unsaved diagrams—so your flows stay fresh, stateless, and secure.

Top Flows (With Real Copy/Paste Examples!)

1. List Available Tools

Get a feel for the toolbox:

curl -s -X POST https://flowzap.xyz/api/mcp/messages  -H "Content-Type: application/json"   --data '{"jsonrpc":"2.0","id":1,"method":"tools/list","params":{}}' | jq

2. Register a New Agent (Get API Token)

curl -s -X POST https://flowzap.xyz/api/mcp/messages   -H "Content-Type: application/json"   --data '{"jsonrpc":"2.0","id":2,"method":"tools/call","params":{"name":"flowzap.register_agent","arguments":{"name":"Partner Agent","email":"<partner@example.com>","termsAccepted":true}}}' | jq

You’ll get an API token—stash it securely.

3. Authenticate (Swap Token for JWT)

curl -s -X POST https://flowzap.xyz/api/mcp/messages   -H "Content-Type: application/json"   --data '{"jsonrpc":"2.0","id":3,"method":"tools/call","params":{"name":"flowzap.authenticate_agent","arguments":{"apiToken":"<YOUR_API_TOKEN>"}}}' | jq

4. Create a Playground Session

This gives you a 5-minute “unsaved” public diagram link + the FlowZap Code (for code-gen or direct editing):

curl -s -X POST https://flowzap.xyz/api/mcp/messages   -H "Content-Type: application/json"   --data '{"jsonrpc":"2.0","id":4,"method":"tools/call","params":{"name":"flowzap.playground_create_session","arguments":{"code":"node A
node B
A -> B"}}}' | jq

You’ll get a result like:

{
  "success": true,
  "url": "https://flowzap.xyz/playground/xyz...",
  "code": "node A\nnode B\nA -> B"


Note: The playground link dies after 5 minutes unless the user registers and saves their work—which helps partners drive conversion.

What You Can Build

  Claude (or any Anthropic agent): Add us as a remote MCP custom connector: Settings → Connectors → Add custom connector → Enter https://flowzap.xyz/api/mcp/sse.
  ChatGPT (API, Plugins, or Actions): Implement function calling that posts to https://flowzap.xyz/api/mcp/messages (JSON-RPC 2.0). Use OpenAPI or Postman to wire tools as functions.
  DeepSeek, Qwen, Grok, and Others: Same deal—if your orchestrator or agent framework does external tool calls/functions (LangChain, Hugging Face Agents, custom code, whatever), just point it to our endpoint with a valid payload.
  CLI, Browser Agents, Server Bots: The server is CORS-permissive (Access-Control-Allow-Origin: *), so you can even run this in-browser for hacky demos or frontends (just don’t expose your tokens to the wild).


Real-World Flow (The Developer’s Iterative Loop)

  Agent (Claude, ChatGPT, DeepSeek, Grok, etc.) sends a JSON-RPC call → FlowZap MCP spins up a sandboxed, unsaved playground session for the user.
  User sees a public diagram (URL) and editable FlowZap Code for 5 minutes → Playground session is interactive (drag, drop, edit), but Save is disabled until registration.
  User asks agent for more adjustments → You call the API again, get a fresh link/code.
  User wants to save it → They’re smoothly nudged to register/log in on flowzap.xyz, which unlocks all team/collaboration features.

No image previews. No binary hacks. What you get is always a clean URL + FlowZap Code—no fat, just workflow.

Authentication

  OAuth 2.0: The MCP server supports OAuth 2.0 with dynamic client registration.
  Claude Desktop: OAuth flow is automatic (when it works properly).
  Direct API access: Register via the registration endpoint, then authenticate to obtain tokens.
  Testing: Mock authentication is available for testing purposes.


Designed for Control and Growth

  For you: Drive users to your apps, not just to endless sandboxes. No saved diagrams means the conversion funnel is always running.
  For the ecosystem: Build bridges, not silos. We're here for open agents, not gatekeeping.
  For partners: Want dedicated, branded, or high-volume flow? Let’s chat.


Wrap Up
The FlowZap MCP is your fast lane to workflow diagrams, with frictionless handoff from LLMs to interactive UIs and, ultimately, to paying, collaborating users. Plug it in, try it out, and let us know what you build.

  Discovery: https://flowzap.xyz/api/mcp
  SSE: https://flowzap.xyz/api/mcp/sse
  Messages: POST https://flowzap.xyz/api/mcp/messages
  Health: GET https://flowzap.xyz/api/mcp/health
  OpenAPI Stub: GET https://flowzap.xyz/openapi.json
  Postman: GET https://flowzap.xyz/postman.json
  Support: feedback@flowzap.xyz
  FlowZap Code GitHub: https://github.com/flowzap-xyz/code

Questions? Feedback? Hit me up. If you connect, test, or ship with /api/mcp, tell me!
FlowZap MCP: The open, agent-friendly bridge to real business diagrams. Build the workflows you want, how you want.