Skip to content

Conversation

@SashenkaG
Copy link

@SashenkaG SashenkaG commented Nov 19, 2025

$Subject

Summary by CodeRabbit

  • Documentation
    • Added a comprehensive guide for generating and managing MCP (Model Context Protocol) servers from existing HTTP services, covering MCP basics, transport options, prerequisites, generation and deployment steps, and publish/subscribe workflows.
    • Includes guidance on token usage and lifecycle cautions, tool modification and deployment notes, illustrative images, and a new navigation entry for the guide.

✏️ Tip: You can customize this high-level summary in your review settings.

@CLAassistant
Copy link

CLAassistant commented Nov 19, 2025

CLA assistant check
All committers have signed the CLA.

@coderabbitai
Copy link

coderabbitai bot commented Nov 19, 2025

Walkthrough

Adds a new Devant documentation guide explaining how to generate MCP (Model Context Protocol) servers from existing HTTP services and updates the mkdocs navigation to include the new guide under "Configure VPN".

Changes

Cohort / File(s) Summary
MCP Server Documentation
en/docs/mcp-servers/generate-mcp-servers.md
New Markdown guide describing MCP fundamentals and transports (stdio, streamable HTTP), Devant's generation of MCP servers from HTTP services, prerequisites (organization/project), step-by-step generation and deployment notes, tool modification workflow, publishing/subscribing/token/connect/invoke flow using the MCP Inspector, lifecycle cautions, images, and UI tips.
Documentation Navigation
en/mkdocs.yml
Added mcp-servers/generate-mcp-servers.md as "Create MCP servers" under the "Configure VPN" navigation and adjusted indentation/formatting in that block.

Sequence Diagram(s)

sequenceDiagram
  autonumber
  participant Dev as Developer
  participant CLI as Devant CLI
  participant HTTP as Existing HTTP Service
  participant MCP as Generated MCP Server
  participant Inspector as MCP Inspector
  participant Client as Client (MCP)

  Dev->>CLI: run "generate mcp-server" for HTTP integration
  CLI->>HTTP: inspect API (endpoints, schemas, auth)
  CLI-->>MCP: scaffold MCP server (transports, tool manifest)
  rect rgb(232,245,233)
    note right of MCP: Generated artifact (server, tool schema, docs)
  end
  Dev->>MCP: review, edit tools, deploy/promote
  Client->>Inspector: connect using token (publish/subscribe)
  Inspector->>MCP: invoke tool
  MCP->>HTTP: translate/forward request
  HTTP-->>MCP: return response
  MCP-->>Inspector: relay response to client
Loading

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~10 minutes

  • Check en/docs/mcp-servers/generate-mcp-servers.md for command accuracy, image paths, and lifecycle/security cautions.
  • Validate en/mkdocs.yml nav insertion and site build/navigation ordering.

Poem

🐰 I hopped through docs with curious paws,
Turned HTTP routes into MCP laws,
Tokens tucked and ready to send,
Publish, subscribe — then recommend,
A tiny server, and many new paws 🥕

Pre-merge checks and finishing touches

❌ Failed checks (1 warning, 1 inconclusive)
Check name Status Explanation Resolution
Description check ⚠️ Warning The pull request description is entirely inadequate, containing only '$Subject' as a placeholder. It lacks all required template sections including purpose, goals, approach, and other essential information. Complete the PR description using the repository template. Provide details about the MCP documentation additions, the resolved issues, implementation approach, and other required sections.
Title check ❓ Inconclusive The title is vague and overly broad. 'Resolve reviews and update images' does not clearly convey the main change of adding new MCP server documentation. Revise the title to be more specific about adding MCP server documentation, e.g., 'Add guide for generating MCP servers from HTTP services'.
✅ Passed checks (1 passed)
Check name Status Explanation
Docstring Coverage ✅ Passed No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
✨ Finishing touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Post copyable unit tests in a comment

📜 Recent review details

Configuration used: CodeRabbit UI

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between fc54901 and 5bfbcbd.

📒 Files selected for processing (1)
  • en/docs/mcp-servers/generate-mcp-servers.md (1 hunks)
🧰 Additional context used
🪛 LanguageTool
en/docs/mcp-servers/generate-mcp-servers.md

[grammar] ~57-~57: Use a hyphen to join words.
Context: ...ory in Devant.

  1. Navigate to an HTTP based Integration as API type integrat...

(QB_NEW_EN_HYPHEN)


[grammar] ~83-~83: Use a hyphen to join words.
Context: ...n at this stage. The schema will be auto generated once you create the mapping to...

(QB_NEW_EN_HYPHEN)


[style] ~164-~164: Using many exclamation marks might seem excessive (in this case: 15 exclamation marks for a text that’s 7648 characters long)
Context: ... directly from the MCP Inspector UI.

!!!important
If you are using another ...

(EN_EXCESSIVE_EXCLAMATION)

🪛 markdownlint-cli2 (0.18.1)
en/docs/mcp-servers/generate-mcp-servers.md

20-20: Unordered list indentation
Expected: 2; Actual: 4

(MD007, ul-indent)


21-21: Unordered list indentation
Expected: 2; Actual: 4

(MD007, ul-indent)

🔇 Additional comments (2)
en/docs/mcp-servers/generate-mcp-servers.md (2)

23-54: Prerequisites section is well-structured.

The organization and project setup instructions are clear, properly formatted, and require no changes.


92-166: Invoke section is well-organized with clear workflow.

The 6-step workflow for invoking MCP tools is logically structured, with good use of prerequisites, images, and sequential instructions. The instructions are clear and actionable for users.

Tip

📝 Customizable high-level summaries are now available in beta!

You can now customize how CodeRabbit generates the high-level summary in your pull requests — including its content, structure, tone, and formatting.

  • Provide your own instructions using the high_level_summary_instructions setting.
  • Format the summary however you like (bullet lists, tables, multi-section layouts, contributor stats, etc.).
  • Use high_level_summary_in_walkthrough to move the summary from the description to the walkthrough section.

Example instruction:

"Divide the high-level summary into five sections:

  1. 📝 Description — Summarize the main change in 50–60 words, explaining what was done.
  2. 📓 References — List relevant issues, discussions, documentation, or related PRs.
  3. 📦 Dependencies & Requirements — Mention any new/updated dependencies, environment variable changes, or configuration updates.
  4. 📊 Contributor Summary — Include a Markdown table showing contributions:
    | Contributor | Lines Added | Lines Removed | Files Changed |
  5. ✔️ Additional Notes — Add any extra reviewer context.
    Keep each section concise (under 200 words) and use bullet or numbered lists for clarity."

Note: This feature is currently in beta for Pro-tier users, and pricing will be announced later.


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

@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: 2

📜 Review details

Configuration used: CodeRabbit UI

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between f89839f and 094194a.

⛔ Files ignored due to path filters (8)
  • en/docs/assets/img/mcp/create-mcp-form.png is excluded by !**/*.png
  • en/docs/assets/img/mcp/generate-mcp.png is excluded by !**/*.png
  • en/docs/assets/img/mcp/mcp-inspector-initial.png is excluded by !**/*.png
  • en/docs/assets/img/mcp/mcp-inspector.png is excluded by !**/*.png
  • en/docs/assets/img/mcp/mcp-overview.png is excluded by !**/*.png
  • en/docs/assets/img/mcp/mcp-publish.png is excluded by !**/*.png
  • en/docs/assets/img/mcp/mcp-token.png is excluded by !**/*.png
  • en/docs/assets/img/mcp/mcp-tools.png is excluded by !**/*.png
📒 Files selected for processing (2)
  • en/docs/mcp-servers/generate-mcp-servers.md (1 hunks)
  • en/mkdocs.yml (1 hunks)
🧰 Additional context used
🪛 LanguageTool
en/docs/mcp-servers/generate-mcp-servers.md

[grammar] ~57-~57: Use a hyphen to join words.
Context: ...ory in Devant.

  1. Navigate to an HTTP based Integration as API type integrat...

(QB_NEW_EN_HYPHEN)


[grammar] ~83-~83: Use a hyphen to join words.
Context: ...n at this stage. The schema will be auto generated once you create the mapping t...

(QB_NEW_EN_HYPHEN)


[style] ~166-~166: Using many exclamation marks might seem excessive (in this case: 15 exclamation marks for a text that’s 7553 characters long)
Context: ... directly from the MCP Inspector UI.

!!!important
If you are using another ...

(EN_EXCESSIVE_EXCLAMATION)

🪛 markdownlint-cli2 (0.18.1)
en/docs/mcp-servers/generate-mcp-servers.md

20-20: Unordered list indentation
Expected: 2; Actual: 4

(MD007, ul-indent)


21-21: Unordered list indentation
Expected: 2; Actual: 4

(MD007, ul-indent)

🔇 Additional comments (4)
en/mkdocs.yml (1)

113-116: Navigation placement may need reconsideration.

The new MCP servers section is nested under "Configure VPN," which semantically seems unrelated. MCP server generation is distinct from VPN configuration. Consider whether this should be:

  • A separate top-level navigation section (like "API Management" at line 111)
  • Placed under a more thematically appropriate section (e.g., "API Management" or "Devant Concepts")

Verify this placement aligns with your documentation architecture and user navigation patterns.

en/docs/mcp-servers/generate-mcp-servers.md (3)

1-168: Document structure and content quality—LGTM.

The guide is comprehensive and well-organized:

  • Clear overview of MCP concepts with links to official specifications
  • Logical flow from prerequisites → design/publish → invocation
  • Step-by-step instructions with helpful admonitions (info, important, tip)
  • Good use of visual callouts and notes for critical information
  • Prerequisites clearly outlined before each major section

Minor suggestions (optional):

  • Consider adding a "Troubleshooting" section for common issues
  • Link to API documentation or deployment track concepts if applicable
  • Clarify token expiration/rotation policies in Step 4

Overall, excellent first-pass documentation for the new feature.


1-11: External resource links—verify accessibility.

The document references two external resources:

Ensure these links remain current and are accessible to your documentation audience. Consider adding version pinning or archival notes if these resources are outside your control.


61-61: All image assets verified—no issues found.

All 8 referenced MCP images exist in en/docs/assets/img/mcp/ with correct filenames matching the documentation references.

Copy link

@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

♻️ Duplicate comments (1)
en/docs/mcp-servers/generate-mcp-servers.md (1)

20-21: Fix list indentation to use 2 spaces instead of 4.

The nested list items still use 4-space indentation but should use 2 spaces per Markdown standards and linter requirements (MD007). This issue was flagged in the previous review but remains unfixed.

Apply this diff:

 * Create MCP Servers from existing HTTP services under the category `Integration as APIs` from Devant.
-    * Automatically generates MCP tool schemas from the service definition.
-    * Secures the MCP Servers using OAuth2 authentication and authorization.
+  * Automatically generates MCP tool schemas from the service definition.
+  * Secures the MCP Servers using OAuth2 authentication and authorization.
📜 Review details

Configuration used: CodeRabbit UI

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between b239db4 and 4f6ec35.

📒 Files selected for processing (1)
  • en/docs/mcp-servers/generate-mcp-servers.md (1 hunks)
🧰 Additional context used
🪛 LanguageTool
en/docs/mcp-servers/generate-mcp-servers.md

[style] ~166-~166: Using many exclamation marks might seem excessive (in this case: 15 exclamation marks for a text that’s 7555 characters long)
Context: ... directly from the MCP Inspector UI.

!!!important
If you are using another ...

(EN_EXCESSIVE_EXCLAMATION)

🪛 markdownlint-cli2 (0.18.1)
en/docs/mcp-servers/generate-mcp-servers.md

20-20: Unordered list indentation
Expected: 2; Actual: 4

(MD007, ul-indent)


21-21: Unordered list indentation
Expected: 2; Actual: 4

(MD007, ul-indent)

Copy link

@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

♻️ Duplicate comments (1)
en/docs/mcp-servers/generate-mcp-servers.md (1)

20-21: Fix unordered list indentation (MD007).

The sublist items use 4 spaces but should use 2 spaces per Markdown best practices and linting rules.

Apply this diff:

 * Create MCP Servers from existing HTTP services under the category `Integration as APIs` from Devant.
-    * Automatically generates MCP tool schemas from the service definition.
-    * Secures the MCP Servers using OAuth2 authentication and authorization.
+  * Automatically generates MCP tool schemas from the service definition.
+  * Secures the MCP Servers using OAuth2 authentication and authorization.
📜 Review details

Configuration used: CodeRabbit UI

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 4f6ec35 and fc54901.

📒 Files selected for processing (1)
  • en/docs/mcp-servers/generate-mcp-servers.md (1 hunks)
🧰 Additional context used
🪛 LanguageTool
en/docs/mcp-servers/generate-mcp-servers.md

[style] ~166-~166: Using many exclamation marks might seem excessive (in this case: 15 exclamation marks for a text that’s 7554 characters long)
Context: ... directly from the MCP Inspector UI.

!!!important
If you are using another ...

(EN_EXCESSIVE_EXCLAMATION)

🪛 markdownlint-cli2 (0.18.1)
en/docs/mcp-servers/generate-mcp-servers.md

20-20: Unordered list indentation
Expected: 2; Actual: 4

(MD007, ul-indent)


21-21: Unordered list indentation
Expected: 2; Actual: 4

(MD007, ul-indent)

🔇 Additional comments (1)
en/docs/mcp-servers/generate-mcp-servers.md (1)

1-168: Well-structured MCP server documentation.

The document is comprehensive, clearly organized, and provides step-by-step guidance with proper visual aids. Prerequisites, creation workflow, tool modification, and invocation steps are all well-documented. Use of admonitions (info, important, tip) and notes is appropriate and enhances clarity.

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.

4 participants