How to Use the Appwrite MCP in VS Code Copilot

Q: How do I roll out the Appwrite MCP Server to my team in VS Code Copilot?

You add the server configuration to your .vscode/mcp.json file and commit it to your Git repository. Every developer with VS Code 1.96+ and Copilot will automatically gain access to the MCP Server tools.

Share Appwrite schema access and storage checks across your entire dev team inside VS Code Copilot.

See Vinkius in Action

Works with every AI agent you already use

…and any MCP-compatible client

MCP Servers - Free for Subscribers

Connect Appwrite MCP to VS Code Copilot

Create your Vinkius account to connect Appwrite to VS Code Copilot and route execution through our secure gateway. The platform manages server hosting, runtime updates, and security layers. Configuration requires no manual server provisioning.

GDPR Free for Subscribers

Setup Appwrite with VS Code Copilot

Ask AI about this MCP

ChatGPT

Claude

Perplexity

Align your team with live Appwrite schemas in VS Code Copilot

This MCP Server exposes `list_databases`, `list_collections`, and `list_documents` to give your team's VS Code Copilot agents instant access to your shared Appwrite database structures. By committing the Appwrite configuration to your repository, every developer gets the same schema context inside VS Code Copilot automatically. This stops team members from writing code against outdated Appwrite collections inside VS Code Copilot. The VS Code Copilot agent references the live Appwrite backend setup to ensure everyone writes compatible queries.

Debug Appwrite cloud functions directly in VS Code Copilot

This integration exposes `list_functions` and `list_function_executions` to let VS Code Copilot monitor your Appwrite backend deployments. When an Appwrite serverless function fails, your team can ask VS Code Copilot to pull the execution history and diagnose the bug. It keeps your developers focused inside the VS Code Copilot editor instead of checking the Appwrite dashboard. They don't need to log into the Appwrite web console to check why a background job failed when VS Code Copilot can fetch it.

Monitor Appwrite project health and user lists in VS Code

This toolset uses `get_health_status` and `list_users` to let VS Code Copilot inspect your Appwrite backend status and user directory. Your team can run quick checks on Appwrite server uptime and verify user records during active development inside VS Code Copilot. It simplifies testing user-dependent Appwrite features in VS Code Copilot. The VS Code Copilot agent pulls real-time Appwrite health metrics to confirm your local environment is communicating with the backend.

Setup guide

Set up Appwrite MCP in VS Code Copilot

Prerequisites

VS Code 1.99 or later with GitHub Copilot extension
Active Vinkius subscription with a valid endpoint token

1

Open MCP configuration

Open the Command Palette (Cmd+Shift+P / Ctrl+Shift+P) and run "MCP: Add Server". Select HTTP (Streamable) as the server type. VS Code will create .vscode/mcp.json in your workspace.
2

Add the Appwrite MCP

Paste the JSON snippet shown on the right into your .vscode/mcp.json. Replace [YOUR_TOKEN_HERE] with your endpoint token from cloud.vinkius.com.
3

Switch to Agent mode

Open Copilot Chat (Cmd+Shift+I / Ctrl+Shift+I) and switch to Agent mode using the dropdown. MCP tools are only available in Agent mode — they do not appear in Edit or Ask modes.
4

Verify the connection

In the Copilot Chat input, type # to list available tools. You should see the Appwrite tools listed. Try asking: "List my recent Appwrite transactions" and Copilot will invoke them automatically.

.vscode/mcp.json

{
  "mcpServers": {
    "appwrite-mcp": {
      "url": "https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp"
    }
  }
}

Get your connection token →

Independent Platform Disclaimer: Vinkius is an independent platform and is not affiliated with, endorsed by, sponsored by, verified by, or otherwise authorized by Appwrite. All third-party trademarks, logos, and brand names are the property of their respective owners. Their use on this website is strictly for informational purposes to identify service compatibility and interoperability.

Why Choose Vinkius

Vinkius connects your tools to AI with real-time monitoring and automatic cost savings — all from one dashboard.

Connect Appwrite now

Real-time monitoring

Live

visibility into every interaction

Connect your favorite tools to your AI and see exactly what's happening — every request, every response, in real time.

Built-in savings

60%

lower AI costs

Vinkius compresses data between your apps and your AI automatically. Lower bills every month — no configuration required.

Single dashboard

One

place for every integration

Every tool your AI connects to, managed from a single screen. One account, complete control.

Common questions about Appwrite MCP in VS Code Copilot

You add the server configuration to your `.vscode/mcp.json` file and commit it to your Git repository. Every developer with VS Code 1.96+ and Copilot will automatically gain access to the MCP Server tools.

No, the server only reads configuration data using tools like `list_storage_buckets`. It cannot delete or modify buckets, ensuring your storage assets remain safe.

Yes, you can load your Appwrite API keys through local environment variables. VS Code Copilot reads these variables securely without exposing them in your shared repository config.

Yes, you can define different server profiles for development, staging, and production. Your team can toggle between these environments depending on which branch they are working on.

Your database collections, bucket files, and user lists are accessed on-demand and are not used for model training. All data transfers are encrypted and respect your VS Code Copilot enterprise privacy settings.

Use it with your favorite AI tools

Connect this server to Cursor, Claude, VS Code, and more.

OpenAI Agents SDK sdk-python

Google ADK sdk-python

Pydantic AI sdk-python

Vercel AI SDK sdk-typescript