Add remote mcp docs#3095
Conversation
Appwrite WebsiteProject ID: Website (appwrite/website)Project ID: Tip Messaging handles push notifications, emails, and SMS through one unified API |
Greptile SummaryThis PR migrates all Appwrite MCP documentation from the local
Confidence Score: 4/5Documentation-only change; the remote server URL and OAuth flow are consistently applied across the agent pages, and the previously broken angle-bracket URLs are properly fixed. The three integration pages still use the server key appwrite while every dedicated agent docs page uses appwrite-api, which could leave users with duplicate entries if they follow both sets of docs. src/routes/integrations/mcp-claude/+page.markdoc, src/routes/integrations/mcp-cursor/+page.markdoc, src/routes/integrations/mcp-windsurf/+page.markdoc — server name should be aligned with the agent docs pages. Important Files Changed
Prompt To Fix All With AIFix the following 1 code review issue. Work through them one at a time, proposing concise fixes.
---
### Issue 1 of 1
src/routes/integrations/mcp-claude/+page.markdoc:59-70
**Inconsistent MCP server name across docs**
The integration pages (`mcp-claude`, `mcp-cursor`, `mcp-windsurf`) register the server under the name `"appwrite"`, while every agent docs page (`claude-code`, `cursor`, `windsurf`, `vscode`, `zed`, etc.) registers it as `"appwrite-api"`. A user who follows both sets of docs ends up with two differently-named entries pointing to the same remote URL. Standardising on a single name (e.g. `"appwrite-api"`) across all pages would prevent that duplication. The same pattern appears in `mcp-cursor/+page.markdoc` and `mcp-windsurf/+page.markdoc`.
Reviews (1): Last reviewed commit: "Add remote mcp docs" | Re-trigger Greptile |
![greptile-apps[bot]](https://avatars.githubusercontent.com/in/867647?s=60&v=4){kind=small}
| { | ||
| "mcpServers": { | ||
| "appwrite": { | ||
| "command": "uvx", | ||
| "command": "npx", | ||
| "args": [ | ||
| "mcp-server-appwrite" | ||
| ], | ||
| "env": { | ||
| "APPWRITE_API_KEY": "<your-api-key>", | ||
| "APPWRITE_PROJECT_ID": "<your-project-id>", | ||
| "APPWRITE_ENDPOINT": "https://<REGION>.cloud.appwrite.io/v1" | ||
| } | ||
| "mcp-remote", | ||
| "https://mcp.appwrite.io/mcp" | ||
| ] | ||
| } | ||
| } | ||
| } | ||
| ``` |
There was a problem hiding this comment.
The integration pages (mcp-claude, mcp-cursor, mcp-windsurf) register the server under the name "appwrite", while every agent docs page (claude-code, cursor, windsurf, vscode, zed, etc.) registers it as "appwrite-api". A user who follows both sets of docs ends up with two differently-named entries pointing to the same remote URL. Standardising on a single name (e.g. "appwrite-api") across all pages would prevent that duplication. The same pattern appears in mcp-cursor/+page.markdoc and mcp-windsurf/+page.markdoc.
Prompt To Fix With AI
This is a comment left during a code review.
Path: src/routes/integrations/mcp-claude/+page.markdoc
Line: 59-70
Comment:
**Inconsistent MCP server name across docs**
The integration pages (`mcp-claude`, `mcp-cursor`, `mcp-windsurf`) register the server under the name `"appwrite"`, while every agent docs page (`claude-code`, `cursor`, `windsurf`, `vscode`, `zed`, etc.) registers it as `"appwrite-api"`. A user who follows both sets of docs ends up with two differently-named entries pointing to the same remote URL. Standardising on a single name (e.g. `"appwrite-api"`) across all pages would prevent that duplication. The same pattern appears in `mcp-cursor/+page.markdoc` and `mcp-windsurf/+page.markdoc`.
How can I resolve this? If you propose a fix, please make it concise.
1 participant
What does this PR do?
(Provide a description of what this PR does.)
Test Plan
(Write your test plan here. If you changed any code, please provide us with clear instructions on how you verified your changes work.)
Related PRs and Issues
(If this PR is related to any other PR or resolves any issue or related to any issue link all related PR and issues here.)
Have you read the Contributing Guidelines on issues?
(Write your answer here.)