Developer · Remote MCP server
Flowboard
Discover cloud shapes and create, inspect, validate, patch, and review architecture diagrams.
What the MCP Registry states
The entry as published to the official MCP Registry (read 2026-10-04), latest version.
- Registry name
io.github.FlowboardStudio/flowboard- Version
- 3.4.5
- Status
- Active
- Category
- developer
- Transport
- Streamable HTTP
- Published
- 2026-09-26
- Updated
- 2026-09-26
- Publisher
- FlowboardStudio (GitHub)
- Namespace
- Namespace verified by the MCP Registry via GitHub (github.com/FlowboardStudio) · how
- Repository
- github.com/FlowboardStudio/flowboard
- Source
- Registry API entry
Remote endpoints
| Transport | URL | Headers declared |
|---|---|---|
| Streamable HTTP | https://flowboard.studio/mcp | Authorization (required, secret) |
Live check
This directory connected to each remote endpoint and asked for its list of tools. The check connects and lists tools only; it doesn't run tools, sign in or test security.
- Reachable
- Yes (HTTP 200)
- Handshake
- flowboard 3.4.7@076575bba5a2281cb89bc4bb412ba9f885 · protocol 2025-06-18
- Tools discovered
23 - show names
list_diagram_revisions,get_diagram_revision,restore_diagram_revision,list_shapes,create_diagram,list_diagrams,get_diagram,update_diagram,patch_diagram,propose_diagram_changes,list_diagram_proposals,decide_diagram_proposal,validate_diagram,delete_diagram,list_agent_errors,submit_agent_feedback,list_agent_feedback,get_architecture_decision,search_architecture_decisions,get_architecture_model,update_architecture_model,list_architecture_revisions,get_architecture_revision- Checked on
- 2026-10-05
How to connect Flowboard
Flowboard is a remote MCP server: there is nothing to install. Its endpoint is https://flowboard.studio/mcp, served over Streamable HTTP. In an assistant that accepts remote MCP servers (often under a setting named connectors, integrations or tools), add a new server and give it this URL; in a client configured by file, add it as a remote (HTTP) server with the same URL.
The registry entry declares an HTTP header for the connection: Authorization (required, secret). A secret header usually carries an API key or token issued by the service; clients that accept custom headers set it with the server's URL.
Derived from the registry entry; the live check above only shows whether the endpoint answered. What the server does, and on what terms, is set by its publisher; check its repository or website before giving it access to your accounts or files. How to add an MCP server to an assistant · Before you connect
More developer servers
| Server | Runs |
|---|---|
| Flipside MCPFlipside Crypto SQL API: run queries, check status, fetch results. | Local · stdio |
| FloomDeploy Python functions as web apps with auto-generated UI, REST API, and shareable links. | Local · stdio |
| FlootBuild and publish full-stack web and mobile apps on Floot from any MCP client. Building is free. | Remote · HTTPLive check: sign-in required |
| Flow NexusCloud-powered AI platform with multi-agent swarms, sandboxes, and workflow automation. | Local · stdio |
| FlowCastleBuild, edit, and deploy Telegram bots on FlowCastle's hosted visual flow platform. | Remote · HTTPLive check: ✓ handshake |
| FlowSentrySecurity scanner for n8n workflows + live MCP Trust-Check. 18 rules, OWASP mapped. Paid x402 API. | Remote · HTTPLive check: ✗ no handshake |
| FluidTalkCreate AI Characters and generate their DM and comment replies from any MCP client. | Remote · HTTPLive check: sign-in required |
| FlurryPORTWebhook capture and replay, delivery pipes, and signed multi-agent rooms. No signup to start. | Remote & Local · HTTP, stdioLive check: sign-in required |