Adding MCP Server documentation #25
Conversation
|
Azure Static Web Apps: Your stage site is ready! Visit it here: https://delightful-desert-0513ad50f-25.eastus2.3.azurestaticapps.net |
There was a problem hiding this comment.
Pull request overview
Adds a new “MCP Server” documentation section to the Developer Center, including introductory and usage guidance, and wires it into the Docusaurus sidebar and deployment configuration.
Changes:
- Add a new “MCP Server” category to the docs sidebar.
- Add new MCP Server docs pages: Introduction, Getting Started, and Tools reference.
- Set
DOCUSAURUS_URLin Azure Static Web Apps workflows to control Docusaurusurlper environment.
Reviewed changes
Copilot reviewed 6 out of 6 changed files in this pull request and generated 4 comments.
Show a summary per file
| File | Description |
|---|---|
| sidebars.ts | Adds the MCP Server docs category and links to the new pages. |
| docs/mcp-server/introduction.md | Introduces the OnceHub MCP Server and its primary endpoint. |
| docs/mcp-server/getting-started.md | Provides setup steps (API key, endpoint, and basic prompting guidance). |
| docs/mcp-server/tools.md | Documents the two MCP tools and their basic behavioral rules. |
| .github/workflows/azure-static-web-apps-nice-meadow-0c0634100.yml | Sets DOCUSAURUS_URL for the dev deployment. |
| .github/workflows/azure-static-web-apps-delightful-desert-0513ad50f.yml | Sets DOCUSAURUS_URL for the prod deployment. |
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
| https://mcp.oncehub.com/sse | ||
| ``` | ||
|
|
||
| You must configure this endpoint in your MCP compatible AI Agent to begin interacting with the scheduling tools. |
There was a problem hiding this comment.
Minor hyphenation: "MCP compatible" is typically written as the compound adjective "MCP-compatible".
| You must configure this endpoint in your MCP compatible AI Agent to begin interacting with the scheduling tools. | |
| You must configure this endpoint in your MCP-compatible AI Agent to begin interacting with the scheduling tools. |
|
|
||
| - Guest name | ||
| - Guest email | ||
| - Selected Date: Format: `YYYY-MM-DDTHH:MM:SSZ` |
There was a problem hiding this comment.
The documented Selected Date format (YYYY-MM-DDTHH:MM:SSZ) is not an ISO 8601 representation and is likely to be misread (uppercase MM commonly denotes month, not minutes). Please update this to a correct ISO 8601 example/format (e.g., include a concrete timestamp like 2026-02-11T13:45:00Z, and/or use the correct minute/second tokens) so consumers send valid values.
| - Selected Date: Format: `YYYY-MM-DDTHH:MM:SSZ` | |
| - Selected Date: Must be provided as an ISO 8601 timestamp (e.g., `2026-02-11T13:45:00Z`) |
| - Buffer settings | ||
|
|
||
| :::note | ||
| The only exception to the Booking Settings tab is Bookable days; instead the search window is determined by the specific date range provided in the tool request. |
There was a problem hiding this comment.
Minor grammar: "instead the search window" reads like a missing comma and is slightly unclear. Consider changing to "instead, the search window is determined by…" for readability.
| The only exception to the Booking Settings tab is Bookable days; instead the search window is determined by the specific date range provided in the tool request. | |
| The only exception to the Booking Settings tab is Bookable days; instead, the search window is determined by the specific date range provided in the tool request. |
|
|
||
| The AI Agent calls this tool to obtain available times for you to choose from. | ||
|
|
||
| ## 2. Schedule A Meeting |
There was a problem hiding this comment.
The section title uses inconsistent capitalization ("Schedule A Meeting") while the tool name and surrounding text use "Schedule a meeting". Aligning the heading casing improves scanability and avoids implying a different proper noun.
| ## 2. Schedule A Meeting | |
| ## 2. Schedule a meeting |
Adding MCP Server section