wolfpack-mcp 1.0.15 → 1.0.16
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 +12 -0
- package/dist/index.js +8 -1
- package/package.json +1 -1
package/README.md
CHANGED
|
@@ -93,6 +93,15 @@ To pre-select a default team, add to your config:
|
|
|
93
93
|
}
|
|
94
94
|
```
|
|
95
95
|
|
|
96
|
+
## Project Focus
|
|
97
|
+
|
|
98
|
+
The MCP server is designed to work within **one project at a time**:
|
|
99
|
+
|
|
100
|
+
- The agent will identify which project you're working in before taking actions
|
|
101
|
+
- Once a project is identified, all operations stay within that project
|
|
102
|
+
- The agent will not perform bulk actions across multiple projects
|
|
103
|
+
- To switch projects, explicitly tell Claude (e.g., "switch to the Platform project")
|
|
104
|
+
|
|
96
105
|
## API Key Permissions
|
|
97
106
|
|
|
98
107
|
When creating your API key, select the permissions you need:
|
|
@@ -137,6 +146,9 @@ Verify [wolfpacks.work](https://wolfpacks.work) is accessible from your network.
|
|
|
137
146
|
- Permissions are configurable per key—grant only what you need
|
|
138
147
|
- Revoke keys anytime from Account Settings
|
|
139
148
|
|
|
149
|
+
For additional security, you can **restrict API keys to specific projects** when creating them in Account Settings. This
|
|
150
|
+
ensures the key can only access the projects you select, regardless of your team memberships.
|
|
151
|
+
|
|
140
152
|
## Available Tools Reference
|
|
141
153
|
|
|
142
154
|
<details>
|
package/dist/index.js
CHANGED
|
@@ -245,7 +245,14 @@ class WolfpackMCPServer {
|
|
|
245
245
|
// Team tools
|
|
246
246
|
{
|
|
247
247
|
name: 'list_teams',
|
|
248
|
-
description: 'List all teams you have access to.
|
|
248
|
+
description: 'List all teams (projects) you have access to. ' +
|
|
249
|
+
'IMPORTANT - PROJECT FOCUS RULES: ' +
|
|
250
|
+
'1) Call this FIRST to identify which project you are working in. ' +
|
|
251
|
+
'2) Once you identify a project, STAY WITHIN that project for all operations unless the user explicitly asks to switch projects. ' +
|
|
252
|
+
'3) NEVER perform bulk actions across multiple projects - always work in one project at a time. ' +
|
|
253
|
+
'4) If the user mentions a specific project, use that project for all subsequent operations. ' +
|
|
254
|
+
'5) If unclear which project to use, ASK the user before proceeding. ' +
|
|
255
|
+
'Returns team IDs, slugs, and names. Single-team users have their team auto-selected; multi-team users must specify team_id in other tool calls.',
|
|
249
256
|
inputSchema: {
|
|
250
257
|
type: 'object',
|
|
251
258
|
properties: {},
|