You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
@@ -23,6 +23,8 @@ A Model Context Protocol server for interacting with Appwrite's API. This server
23
23
24
24
> Before launching the MCP server, you must setup an [Appwrite project](https://cloud.appwrite.io/) and create an API key with the necessary scopes enabled.
25
25
26
+
The server validates the credentials and scopes required for its built-in Appwrite service set during startup. If the endpoint, project ID, API key, or scopes are wrong, the MCP server will fail to start instead of waiting for the first tool call to fail.
27
+
26
28
Create a `.env` file in your working directory and add the following:
27
29
28
30
```env
@@ -64,7 +66,7 @@ When using [`uv`](https://docs.astral.sh/uv/) no specific installation is needed
64
66
use [`uvx`](https://docs.astral.sh/uv/guides/tools/) to directly run *mcp-server-appwrite*.
Both the `uv` and `pip` setup processes require certain arguments to enable MCP tools for various Appwrite APIs.
85
+
The server no longer accepts service-selection or mode flags. It always starts in a compact workflow so the MCP client only sees a small operator-style surface while the full Appwrite catalog stays internal.
84
86
85
-
> When an MCP tool is enabled, the tool's definition is passed to the LLM, using up tokens from the model's available context window. As a result, the effective context window is reduced.
86
-
>
87
-
> The default Appwrite MCP server ships with only the Databases tools (our most commonly used API) enabled to stay within these limits. Additional tools can be enabled by using the flags below.
87
+
- Only 2 MCP tools are exposed to the model:
88
+
-`appwrite_search_tools`
89
+
-`appwrite_call_tool`
90
+
- The full Appwrite tool catalog stays internal and is searched at runtime.
91
+
- Large tool outputs are stored as MCP resources and returned as preview text plus a resource URI.
uv run python -m unittest discover -s tests/unit -v
254
+
```
255
+
256
+
### Live integration tests
257
+
258
+
These tests create and delete real Appwrite resources against a real Appwrite project. They run automatically when valid Appwrite credentials are available in the environment or `.env`.
0 commit comments