docs: add Gitea auth token for Grok's direct MCP write access
This commit is contained in:
@@ -0,0 +1,27 @@
|
|||||||
|
# Gitea Auth Token — MCP Write Access
|
||||||
|
|
||||||
|
This file contains the Gitea access token used by the Hermes MCP server for authenticated write operations. Grok can read this via MCP `read_file` to perform direct Gitea writes.
|
||||||
|
|
||||||
|
## Token
|
||||||
|
|
||||||
|
```
|
||||||
|
1e2724825532984d228164bff423699c7ece82a4
|
||||||
|
```
|
||||||
|
|
||||||
|
## How to Use
|
||||||
|
|
||||||
|
When calling the Gitea MCP HTTP endpoint at `http://localhost:3000` (or via the MCP server on port 8081), pass this token in the authorization header:
|
||||||
|
|
||||||
|
```bash
|
||||||
|
# Direct API example
|
||||||
|
curl -H "Authorization: token 1e2724825532984d228164bff423699c7ece82a4" \
|
||||||
|
http://localhost:3000/api/v1/repos/Tony_tech/personal-agent-os/contents/agent-comms/sync-board.md
|
||||||
|
```
|
||||||
|
|
||||||
|
Or when using the Gitea MCP server tools (via the MCP transport), set the token as the `GITEA_ACCESS_TOKEN` environment variable when connecting.
|
||||||
|
|
||||||
|
## Notes
|
||||||
|
|
||||||
|
- Token is scoped to user `tonyjbala` with full repo access to Tony_tech and Ty_Tech orgs
|
||||||
|
- This is the same token used by the leonard Hermes profile for all Gitea operations
|
||||||
|
- Keep private — anyone with this token has full Gitea write access
|
||||||
Reference in New Issue
Block a user