bvandeusen/FabledScribe
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases 50 Wiki Activity

feat: add .env and Claude config downloads to API key reveal

Browse Source 
After creating a key, two download buttons appear:
- 'Download .env' — pre-filled FABLE_URL + FABLE_API_KEY
- 'Download Claude config' — ready-to-paste mcpServers JSON block

Also adds Future Task A (in-app install instructions) and Future Task B
(Forgejo MCP) to the implementation plan.

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
This commit is contained in:
Bryan Van Deusen
2026-03-23 21:44:34 -04:00
parent 66571e16c1
commit 6180ee65c3
2 changed files with 67 additions and 1 deletions
Download Patch File Download Diff File Expand all files Collapse all files
docs/2026-03-23-fable-mcp-plan.md
+30
View File
@@ -2057,3 +2057,33 @@ Ask Claude: "Use Fable to list my projects." Verify a real response comes back.
git add fable-mcp/
git commit -m "feat: fable-mcp v0.1.0 — complete MCP server with all tool groups"
```
---
## Future Tasks (post v0.1.0)
### Future Task A: In-app MCP install instructions (PyPI/Forgejo registry)
Once `fable-mcp` is published to a package registry (PyPI or the Forgejo package registry at `git.fabledsword.com`), add an install instructions panel to the API Keys tab in Settings. This replaces manual `pip install -e` with a one-liner and links the version shown to the package registry.
**Files:**
- Modify: `frontend/src/views/SettingsView.vue` — add "Install" section above the create form showing:
- `pip install fable-mcp` (or registry-specific command)
- Current published version badge (fetched from registry API)
- Link to full documentation/README
**Depends on:** fable-mcp extracted to its own Forgejo repo and published as a package.
---
### Future Task B: Forgejo MCP server
A second MCP server (`forgejo-mcp/`) that gives Claude direct access to the Forgejo instance at `git.fabledsword.com` for CI/CD automation. Capabilities: list/create/merge PRs, trigger CI runs, read build logs, manage releases, push config files.
**Scope:** Separate spec + plan session. Key questions to resolve in brainstorming:
- Authentication: Forgejo personal access token vs. OAuth app
- Which Gitea/Forgejo API endpoints to expose as tools
- Whether to use an existing `gitea-mcp` or build from scratch (check Forgejo's MCP compatibility)
- CI automation: trigger builds, read job logs, manage runner labels
**Prerequisite:** fable-mcp v0.1.0 working and registered in Claude Code.