quill-flowy
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| APPFLOWY_EMAIL | Yes | The account to log in as. | |
| APPFLOWY_BASE_URL | Yes | Your instance URL. Use your self-hosted domain, not appflowy.com (the vendor cloud is a different backend). | https://flow.example.com |
| APPFLOWY_PASSWORD | Yes | The account password (see secure handling below). | |
| QUILL_FLOWY_WRITE | No | Set to '1' to register the mutating write tools. Off by default. | 0 |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| check_authA | Verify the configured account can log in to AppFlowy and reach it. Read-only. |
| list_workspacesA | List all AppFlowy workspaces (name, id, role, member count). Read-only. |
| list_pagesA | Show the page/view tree of a workspace (titles, ids, and type: document/grid/board/…). Read-only. |
| get_pageA | Return a document page's body rendered as Markdown. Accepts a page title or view id. Read-only. |
| search_pagesA | Find pages by title, or by body text when body=true (decodes each document). Returns matches with ids. Read-only. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 5 tools
Each tool has a clearly distinct purpose: auth verification, workspace listing, page tree listing, page content retrieval, and page search. The only minor overlap is get_page and search_pages by title, but their outputs differ enough to avoid real confusion.
All tools follow the same snake_case verb_noun pattern: check_auth, list_workspaces, list_pages, get_page, search_pages. The naming is predictable and makes the toolset easy to navigate.
Five tools is a well-scoped size for a read-only AppFlowy exploration server. Each tool covers a distinct need without redundancy or unnecessary bulk.
The read-only workflow is well covered: authenticate, list workspaces, browse the page tree, retrieve page bodies, and search content. The main gap is that list_pages mentions grid/board view types, but get_page only handles document page bodies, leaving non-document views without a retrieval path.