Use with AI

These docs are published in two forms an agent can read: an MCP server and plain-text exports. Both are read-only and need no API key.

MCP server

The server at https://docs.flowsign.app/mcp exposes three tools: search the docs, read any page, and send feedback about a page. Connect it once and your agent can look up endpoints, webhook payloads and error codes without you pasting them in.

Claude Code
Cursor
Claude
VS Code

claude mcp add --transport http flowsign-docs https://docs.flowsign.app/mcp

Run claude mcp list to confirm it connected.

Open the MCP settings

Cursor Settings, then MCP, then Add new global MCP server.

Add the server

{
  "mcpServers": {
    "flowsign-docs": {
      "url": "https://docs.flowsign.app/mcp"
    }
  }
}

Add a custom connector

In Claude, open Settings, then Connectors, and choose Add custom connector.

Enter the details

Name it FlowSign docs and set the URL to https://docs.flowsign.app/mcp.

Enable it in a chat

Open the tools menu in a conversation and switch the connector on.

Create .vscode/mcp.json in your project:

{
  "servers": {
    "flowsign-docs": {
      "type": "http",
      "url": "https://docs.flowsign.app/mcp"
    }
  }
}

Plain-text exports

For agents that fetch pages rather than call tools:

URL	Contents
`https://docs.flowsign.app/llms.txt`	An index of every page with a one-line description and a link.
`https://docs.flowsign.app/llms-full.txt`	The whole site in one Markdown file.

Any page is also available as Markdown by adding .md to its URL, for example https://docs.flowsign.app/api-reference/pagination.md.

The MCP server and the text exports read documentation only. Neither calls the FlowSign API on your behalf, so an agent connected this way cannot send packages or look at your workspace. To let an agent act on FlowSign, use the REST API with an API key.

Start here

Concepts

Endpoints

MCP server

Plain-text exports

​MCP server

​Plain-text exports

MCP server

Plain-text exports