Skip to content

Comments

Add Zenflow to MCP integration docs#2719

Open
starlightknown wants to merge 6 commits intoappwrite:mainfrom
starlightknown:doc-2701-add-zenflow-to-mcp-docs
Open

Add Zenflow to MCP integration docs#2719
starlightknown wants to merge 6 commits intoappwrite:mainfrom
starlightknown:doc-2701-add-zenflow-to-mcp-docs

Conversation

@starlightknown
Copy link

@starlightknown starlightknown commented Jan 28, 2026

What does this PR do?

This PR adds Zenflow https://zencoder.ai/zenflow a desktop app to the MCP integration docs. I have added the light and dark logo, added the file to the navigation.

Related PRs and Issues

#2701

Have you read the Contributing Guidelines on issues?

Yes

image image image

Summary by CodeRabbit

Release Notes

  • Documentation
    • Added a comprehensive Zenflow integration guide with step-by-step setup, configuration examples, and testing prompts for Appwrite MCP servers.
    • Added Zenflow to the MCP IDE/tools catalog with both light and dark card variants.
    • Added a Zenflow navigation entry in the Integrations section for easy access.

@coderabbitai
Copy link
Contributor

coderabbitai bot commented Jan 28, 2026

Walkthrough

Adds Zenflow as a new MCP integration in the docs: inserts Zenflow cards into the MCP IDE/tools catalog (light and dark variants), adds a Zenflow navigation item under Integrations in the MCP docs layout, and creates a new documentation page at /docs/tooling/mcp/zenflow with prerequisites, JSON configuration examples for API and Docs servers, setup steps, and testing prompts.

Estimated code review effort

🎯 3 (Moderate) | ⏱️ ~20 minutes

🚥 Pre-merge checks | ✅ 3
✅ Passed checks (3 passed)
Check name Status Explanation
Description Check ✅ Passed Check skipped - CodeRabbit’s high-level summary is enabled.
Title check ✅ Passed The pull request title clearly and concisely describes the main change: adding Zenflow to the MCP integration documentation, which aligns with all modifications across three files.
Docstring Coverage ✅ Passed No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

✏️ Tip: You can configure your own custom pre-merge checks in the settings.

✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Post copyable unit tests in a comment

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

Comment @coderabbitai help to get the list of available commands and usage tips.

Copy link
Contributor

@coderabbitai coderabbitai bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actionable comments posted: 3

🤖 Fix all issues with AI agents
In `@src/routes/docs/tooling/mcp/zenflow/`+page.markdoc:
- Around line 9-10: Replace the misspelled word "pre-requisites" in the heading
string "Before you begin, ensure you have the following **pre-requisites**
installed on your system:" with the correct single-word form "prerequisites" so
the heading reads "Before you begin, ensure you have the following
**prerequisites** installed on your system:"; update the exact string in
src/routes/docs/tooling/mcp/zenflow/+page.markdoc.
- Line 27: The sentence "To add the Appwrite MCP server, open Zenflow and go to
the **Settings** > **MCP servers** . From there, select your agent you want to
configure MCP for, and then add your custom MCP server." contains a stray space
before the period; edit the +page.markdoc content to remove the extra space so
the punctuation is "MCP servers." and ensure no additional spacing issues remain
in the same sentence.
- Around line 96-97: The two copy issues in the Markdoc text should be fixed:
change "you can creating one" to "you can create one" in the sentence that
starts "If you don't have an existing task," and change "how to setup Zenflow"
to the correct phrasing "how to set up Zenflow" in the link text; ensure the
sentences remain grammatically correct and punctuation is consistent in the
paragraph containing "Open **Zenflow Chat**" and the linked text.

starlightknown and others added 3 commits January 28, 2026 14:28
Co-authored-by: coderabbitai[bot] <136622811+coderabbitai[bot]@users.noreply.github.com>
Co-authored-by: coderabbitai[bot] <136622811+coderabbitai[bot]@users.noreply.github.com>
Co-authored-by: coderabbitai[bot] <136622811+coderabbitai[bot]@users.noreply.github.com>
Copy link
Contributor

@coderabbitai coderabbitai bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actionable comments posted: 1

🤖 Prompt for all review comments with AI agents
Verify each finding against the current code and only fix it if needed.

Inline comments:
In `@src/routes/docs/tooling/mcp/zenflow/`+page.markdoc:
- Around line 106-108: Replace the outdated terminology in the example prompts
that use "collections" and "document" with the new docs terminology "columns"
and "rows": update the strings `Show me the collections in my database` -> `Show
me the columns in my database`, `Create a new document in my collection` ->
`Create a new row in my column` (or `Create a new row in my table/collection`
consistent with your schema wording), and `Delete a specific user by ID` if it
references document semantics ensure any surrounding text uses "row" instead of
"document"; search other .markdoc content and generated SDK docs for occurrences
of "document(s)" and "collection(s)" and replace them with "row(s)" and
"column(s)" (or the singular/plural variants) so usage in content, metadata,
code samples and schemas is consistent.

ℹ️ Review info

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 2ba4973 and bcdbcaa.

📒 Files selected for processing (1)
  • src/routes/docs/tooling/mcp/zenflow/+page.markdoc

Comment on lines +106 to +108
- `Show me the collections in my database`
- `Create a new document in my collection`
- `Delete a specific user by ID`
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

⚠️ Potential issue | 🟡 Minor

Update terminology to rows/columns.

The example prompts still use “collections” and “document,” which should be replaced with “columns” and “rows” per the docs terminology update.

✏️ Proposed fix
- - `Show me the collections in my database`
- - `Create a new document in my collection`
+ - `Show me the columns in my database`
+ - `Create a new row in my column`

Based on learnings “In appwrite/website, update terminology to use 'rows' and 'columns' instead of 'documents' and 'collections' across all documentation files with the .markdoc extension, including generated SDK documentation. Ensure consistent usage in content, metadata, and any code samples or schemas.”

📝 Committable suggestion

‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.

Suggested change
- `Show me the collections in my database`
- `Create a new document in my collection`
- `Delete a specific user by ID`
- `Show me the columns in my database`
- `Create a new row in my column`
- `Delete a specific user by ID`
🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed.

In `@src/routes/docs/tooling/mcp/zenflow/`+page.markdoc around lines 106 - 108,
Replace the outdated terminology in the example prompts that use "collections"
and "document" with the new docs terminology "columns" and "rows": update the
strings `Show me the collections in my database` -> `Show me the columns in my
database`, `Create a new document in my collection` -> `Create a new row in my
column` (or `Create a new row in my table/collection` consistent with your
schema wording), and `Delete a specific user by ID` if it references document
semantics ensure any surrounding text uses "row" instead of "document"; search
other .markdoc content and generated SDK docs for occurrences of "document(s)"
and "collection(s)" and replace them with "row(s)" and "column(s)" (or the
singular/plural variants) so usage in content, metadata, code samples and
schemas is consistent.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants