targetprocess-mcp-server 2.6.6 → 2.6.7
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 +45 -0
- package/package.json +1 -1
package/README.md
CHANGED
|
@@ -159,6 +159,51 @@ Developer Tools
|
|
|
159
159
|
---
|
|
160
160
|
|
|
161
161
|
## Installation
|
|
162
|
+
### As a Claude Code Plugin
|
|
163
|
+
|
|
164
|
+
**Prerequisites:** Claude Code CLI installed, and a Targetprocess account with API access.
|
|
165
|
+
|
|
166
|
+
1. **Get your Targetprocess API token**
|
|
167
|
+
In Targetprocess, go to *Settings → Authentication and Security → New Access Token* and copy it.
|
|
168
|
+
|
|
169
|
+
2. **Add this repo as a plugin marketplace**
|
|
170
|
+
Run inside Claude Code:
|
|
171
|
+
```bash
|
|
172
|
+
/plugin marketplace add SerhiiMaksymiv/targetprocess-mcp-server
|
|
173
|
+
```
|
|
174
|
+
|
|
175
|
+
3. **Install the plugin**
|
|
176
|
+
```bash
|
|
177
|
+
/plugin install targetprocess-mcp
|
|
178
|
+
```
|
|
179
|
+
|
|
180
|
+
4. **Fill in the configuration prompts**
|
|
181
|
+
Claude Code will ask for each value in turn:
|
|
182
|
+
| Prompt | What to enter |
|
|
183
|
+
|---|---|
|
|
184
|
+
| Targetprocess API Token | The token from step 1 (input is masked) |
|
|
185
|
+
| Targetprocess Base URL | Your API endpoint, e.g. `https://yourcompany.tpondemand.com/api/v1` |
|
|
186
|
+
| Targetprocess Owner ID | Your user ID — leave the default flow, install first and run the `get_logged_in_user` tool to look it up if you don't know it yet |
|
|
187
|
+
| Targetprocess Project ID *(optional)* | Look up via the `get_projects` tool — press Enter to skip |
|
|
188
|
+
| Targetprocess Team ID *(optional)* | Look up via the `get_teams` tool — press Enter to skip |
|
|
189
|
+
|
|
190
|
+
Values are stored by Claude Code (the token is kept masked/sensitive) — no manual editing of `settings.json` needed.
|
|
191
|
+
|
|
192
|
+
5. **Restart Claude Code** (or start a new session) so the plugin's MCP server connects with the new config.
|
|
193
|
+
|
|
194
|
+
6. **Verify it's connected**
|
|
195
|
+
```bash
|
|
196
|
+
/mcp
|
|
197
|
+
```
|
|
198
|
+
`targetprocess` should show as connected. Try asking Claude something like *"show me the current active release"* to confirm the tools work end to end.
|
|
199
|
+
|
|
200
|
+
**Updating config later:** re-run `/plugin install targetprocess-mcp` (or use `/plugin` to manage installed plugins) to be re-prompted for values.
|
|
201
|
+
|
|
202
|
+
**Uninstalling:**
|
|
203
|
+
```bash
|
|
204
|
+
/plugin uninstall targetprocess-mcp
|
|
205
|
+
```
|
|
206
|
+
|
|
162
207
|
### Local Installation for Development
|
|
163
208
|
```json
|
|
164
209
|
{
|