taskfuel: MCP setup

One of three alternative ways to set taskfuel up, for a client where you cannot run shell commands but can add a remote MCP server yourself. An agent with shell access should take CLI setup instead, which is the preferred path where a shell exists. If you are following this one, it is the only one you do. Do not also install the CLI.

Add https://app.taskfuel.ai/mcp as a Streamable HTTP MCP server, then run your own client's MCP sign-in for it (for example claude mcp add --transport http --scope user taskfuel https://app.taskfuel.ai/mcp followed by claude mcp login taskfuel, or codex mcp add taskfuel --url https://app.taskfuel.ai/mcp followed by codex mcp login taskfuel). The server signs the user in with their browser; no key is copied anywhere. It exposes five tools: discover, call, rate, feedback and balance.

A client that cannot sign in with a browser can instead send an sk-402- API key as Authorization: Bearer. The user creates one at https://app.taskfuel.ai/keys.

An MCP server you just added does not take effect in the session you are already in. The tools appear only after the client reloads them (in Claude Code, /reload-plugins; other clients may need a restart). So do the setup, tell the user how to reload, and carry on once the tools are actually there.

If it turns out you cannot add an MCP server here after all, switch to CLI setup or manual setup. Switch to it, do not add it alongside this.

Next: Using taskfuel, which covers quoting before you pay, the spending limits, and what to show the user first.