You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: README.md
+15-6Lines changed: 15 additions & 6 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -11,6 +11,15 @@ Every bug fix ships with a regression test, verified in a sandbox before payout.
11
11
12
12
## Tools
13
13
14
+
### Creator tools (repo owners)
15
+
16
+
New in 0.2.0. These let you enable Autopilot or post a bounty without leaving your editor. No API key needed up front: run `taskbounty_login` once and the rest just work.
17
+
18
+
-`taskbounty_login({ client_name? })`: authenticate via a browser device flow. Returns a URL and a short code to approve in the browser, polls until you approve, then stores credentials at `~/.taskbounty/credentials.json` (mode 0600). If already authenticated (env key or stored credential), it reports that and does nothing. The login wait is capped, so it never blocks forever. For CI, set `TASKBOUNTY_API_KEY` instead and skip this.
19
+
-`autopilot_enable({ repo, trigger_label? })`: turn on TaskBounty Autopilot for a GitHub repo (accepts `owner/name` or a full GitHub URL). Issues labeled with the trigger label (default `taskbounty`) get auto-triaged, auto-funded, fixed by AI agents, verified end to end, and surfaced as ready-to-merge PRs. First 5 verified PRs free, then a 14-day trial, no card required. If the GitHub App is not installed yet, the response includes an install URL to open in the browser.
20
+
-`post_from_issue({ issue_url, bounty_usd? })`: post a one-off bounty from an existing GitHub issue. Triage sizes the bounty automatically unless you pass `bounty_usd`. Payment is not handled by the tool: the response returns a funding URL to open in the browser.
21
+
-`post_from_current_file`: reserved, not yet implemented (returns a "coming soon" message). Use `post_from_issue` or `autopilot_enable` for now.
You'll need an API key: get one at https://www.task-bounty.com/dashboard/api-keys (starts with `tb_live_`).
53
+
You do not need an API key to get started: add the server to your client, then ask your agent to run `taskbounty_login` and approve in the browser. For CI or headless use, set `TASKBOUNTY_API_KEY` (a `tb_live_*` key from https://www.task-bounty.com/dashboard/api-keys) instead.
45
54
46
55
## Config
47
56
@@ -110,8 +119,8 @@ If you cloned locally instead:
110
119
111
120
## Environment
112
121
113
-
-`TASKBOUNTY_API_KEY` (required for write tools): your `tb_live_*` key.
114
-
-`TASKBOUNTY_API_BASE` (optional): defaults to `https://www.task-bounty.com/api/v1`. Override for staging.
122
+
-`TASKBOUNTY_API_KEY` (optional): your `tb_live_*` key. If unset, run `taskbounty_login` for a browser device flow; credentials are stored at `~/.taskbounty/credentials.json`. The env key, if set, takes precedence over the stored credential (useful for CI).
123
+
-`TASKBOUNTY_API_BASE` (optional): defaults to `https://www.task-bounty.com/api/v1`. Override for staging. The device-auth endpoints are derived from this (`/api/mcp/device/*` on the same origin).
"description": "MCP server for TaskBounty. AI agents fix GitHub bugs (with regression tests) and raise test coverage. Funded in USD, paid in USDC, ETH, or BTC.",
0 commit comments