Add Appwrite Power - Backend-as-a-Service with MCP Server 2.0 - #118
Open
iamaanahmad wants to merge 5 commits into
Open
Add Appwrite Power - Backend-as-a-Service with MCP Server 2.0#118iamaanahmad wants to merge 5 commits into
iamaanahmad wants to merge 5 commits into
Conversation
- Add comprehensive Appwrite power with dual MCP servers (API + Docs) - Include modular API access with command-line flags - Add best practices steering file - Support for databases, auth, storage, functions, messaging, and sites - Update README with Appwrite entry
- Updated POWER.md with MCP 2.0 two-tool architecture - Removed all service flag documentation (--users, --storage, etc.) - Added natural language query examples and workflows - Enhanced steering.md with MCP 2.0 best practices - Simplified configuration (all services now automatic) - Updated to mcp-server-appwrite v0.4.1+ Key improvements: - Zero configuration - no service flags needed - Reduced context usage - only 2 tools exposed - Natural language support - conversational queries - Startup validation - credentials checked on launch - All Appwrite services automatically available
|
Hi @iamaanahmad, thank you for your contribution! Please note that if you haven't already, you would also need to submit your power officially at kiro.dev/powers/submit so it can be reviewed for listing in the Kiro powers registry. |
…nance - Add .gitignore with environment variables, IDE, OS, and log file exclusions - Add CONTRIBUTING.md with guidelines for reporting issues and submitting changes - Add BSD-3-Clause LICENSE file for project governance - Update POWER.md with simplified onboarding for Appwrite Cloud hosted MCP server - Update mcp.json configuration for MCP Server 2.0 compatibility - Enhance steering/steering.md with improved documentation structure - Streamline setup process by removing local API server requirements - Focus documentation on Appwrite Cloud project operations and integrated documentation search
… configuration - Update Appwrite power description to reflect consolidated single MCP server approach - Remove version field from POWER.md metadata - Restructure "Hosted server capabilities" section to "Available MCP Servers" with detailed server configuration - Document appwrite server at https://mcp.appwrite.io/ with OAuth authentication via HTTP transport - Clarify that server combines Appwrite Cloud operations, workspace context, and documentation search - Add guidance on context/search tools before calling detailed project operations - Add new "Available Steering Files" section referencing steering/steering.md for comprehensive Appwrite guidance - Update README.md to reflect single MCP server instead of multiple servers (appwrite-api, appwrite-docs) - Consolidate server information with OAuth authentication details for clearer user reference
…cumentation - Add appwrite-self-hosted MCP server configuration using uvx with stdio transport - Add deployment support table comparing Cloud (OAuth) and self-hosted (API key) options - Update onboarding to include prerequisites and configuration steps for both deployment methods - Restructure POWER.md with clearer sections for deployment options, server descriptions, and steering guidance - Add environment variable configuration for self-hosted: APPWRITE_PROJECT_ID, APPWRITE_API_KEY, APPWRITE_ENDPOINT - Update README.md to reflect dual MCP server support (appwrite-cloud enabled, appwrite-self-hosted disabled by default) - Add keywords for cloud and self-hosted deployment discovery - Enhance guidance on confirming target deployment before destructive operations
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This PR adds a new Appwrite power to the Kiro Powers repository, enabling developers to build backend services with Appwrite directly from their IDE. The power leverages MCP Server 2.0 (v0.4.1+) with a revolutionary two-tool architecture that provides zero-configuration setup and natural language query support.
What's New
🎉 New Power: Appwrite
Appwrite is an open-source backend-as-a-service platform that provides:
🚀 MCP Server 2.0 Architecture
This power uses the latest MCP Server 2.0 with:
appwrite_search_toolsandappwrite_call_tool)📁 Power Structure
Following Kiro's standard power structure:
Configuration
Simple Setup:
{ "mcpServers": { "appwrite-api": { "command": "uvx", "args": ["mcp-server-appwrite"], "env": { "APPWRITE_PROJECT_ID": "${APPWRITE_PROJECT_ID}", "APPWRITE_API_KEY": "${APPWRITE_API_KEY}", "APPWRITE_ENDPOINT": "${APPWRITE_ENDPOINT}" } } } }Prerequisites:
uvpackage manager (for running the MCP server)That's it! All Appwrite services are automatically available - no additional configuration needed.
Key Features
Usage Examples
Natural Language Queries:
How It Works:
appwrite_search_toolsto find the right tool based on your queryappwrite_call_toolwith the specific tool name and parametersExample Workflows:
Technical Details
mcp-server-appwritev0.4.1+Why Appwrite?
Appwrite is a popular open-source backend platform with:
Why This Power?
This power brings Appwrite's full capabilities to Kiro IDE with:
Documentation Included
POWER.md
steering/steering.md
Testing & Validation
Supported Services
All services are automatically available:
References
Checklist
Note: This update maintains backward compatibility while providing a clear migration path. Users can upgrade by simply removing service flags from their configuration.
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.