+22
-1
.github/workflows/status-maintenance.yml
+22
-1
.github/workflows/status-maintenance.yml
···
36
36
37
37
- uses: astral-sh/setup-uv@v4
38
38
39
+
- name: Create MCP config
40
+
run: |
41
+
cat > /tmp/mcp-config.json << 'EOF'
42
+
{
43
+
"mcpServers": {
44
+
"plyrfm": {
45
+
"command": "uvx",
46
+
"args": ["plyrfm-mcp"],
47
+
"env": {
48
+
"PLYR_TOKEN": "${{ secrets.PLYR_BOT_TOKEN }}"
49
+
}
50
+
}
51
+
}
52
+
}
53
+
EOF
54
+
39
55
- uses: anthropics/claude-code-action@v1
40
56
with:
41
57
anthropic_api_key: ${{ secrets.ANTHROPIC_API_KEY }}
58
+
show_full_output: true
42
59
claude_args: |
43
-
--allowedTools "Read,Write,Edit,Bash"
60
+
--allowedTools "Read,Write,Edit,Bash,mcp__plyrfm__list_tracks,mcp__plyrfm__my_tracks,mcp__plyrfm__get_track"
61
+
--mcp-config /tmp/mcp-config.json
44
62
prompt: |
45
63
you are maintaining the plyr.fm project status file.
46
64
···
49
67
this may be the first time this workflow has run. handle gracefully:
50
68
- .status_history/ directory may not exist yet
51
69
- STATUS.md structure may vary
70
+
71
+
you have access to the plyrfm MCP server for interacting with plyr.fm.
72
+
PLYR_TOKEN is set in the environment for CLI uploads.
52
73
53
74
## task 1: archive old sections (if needed)
54
75