@softtor/coolify-mcp-server 1.0.1 → 1.0.2
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/README.md +10 -0
- package/package.json +1 -1
package/README.md
CHANGED
|
@@ -103,6 +103,16 @@ coolify_list_applications { team: "staging" }
|
|
|
103
103
|
3. Create a new token with appropriate permissions
|
|
104
104
|
4. Copy the token and use it as your API key
|
|
105
105
|
|
|
106
|
+
### Important: Tokens Are Team-Scoped
|
|
107
|
+
|
|
108
|
+
**Coolify API tokens are scoped by team.** Each token only provides access to resources within the team where it was created. This means:
|
|
109
|
+
|
|
110
|
+
- A token created in the "Infocell" team can only access Infocell's applications, databases, and servers
|
|
111
|
+
- To manage resources across multiple teams, you need a separate token for each team
|
|
112
|
+
- When using multi-team configuration, make sure each `COOLIFY_TEAM_<NAME>_API_KEY` corresponds to a token created in that specific team
|
|
113
|
+
|
|
114
|
+
See the [Coolify API documentation](https://coolify.io/docs/api-reference/authorization) for more details on token scopes and permissions.
|
|
115
|
+
|
|
106
116
|
## Available Tools
|
|
107
117
|
|
|
108
118
|
### Applications (6 tools)
|