TaskFuel.ai

io.github.taskfuelPublished by GitHub account taskfuelv1.0.0Updated Oct 24, 2026

Specialist tools for any job — a lead, an image, a song, live data, and more.

VerifiedStreamable HTTPWeb executableProductivity & Workflow

Overview

AI-generated overview

TaskFuel.ai is a remote MCP server offering specialist tools for tasks such as leads, images, songs and live data, reached over OAuth-authenticated HTTP.

What you can do
  • The listing gives no tool list, so capabilities are only broadly described.
  • It advertises specialist tools for any job, naming leads, images, songs and live data as examples.
  • Assistants connect to it as a hosted remote endpoint rather than a local package.
When to use it
Consider it when you want an assistant to reach a hosted collection of task-specific tools, such as lead lookups, image or song generation, or live data, without installing anything locally. Check the actual tool list in the app before relying on it.
Requirements
A remote MCP endpoint at app.taskfuel.ai over streamable HTTP, with OAuth sign-in required. No environment variables or headers are declared, and no local runtime or package is needed.
Before you install
OAuth grants the server access under your account, so review the scopes requested at sign-in. The tool list is not published, so what the tools read, write or send to third parties is unknown; confirm before letting an assistant act on your behalf.

Installation

In SourceWeft

  1. Open TaskFuel.ai in the dashboard and add it to a workspace.
  2. Connect the required credentials. They are stored privately and never shown on public pages.
  3. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/io.github.taskfuel%2Ftaskfuel/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config. The client completes OAuth sign-in on first connect.

{
  "mcpServers": {
    "taskfuel-ai": {
      "type": "http",
      "url": "https://app.taskfuel.ai/mcp"
    }
  }
}

Tools

0
This server asks you to sign in, so SourceWeft could not read its tools without an account and has not indexed them. What a connected account sees can depend on that account and its permissions.

Version history

1
  1. v1.0.0LatestSep 16, 2026

Score

67% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • LicenseNot applicable

    A hosted service is used under its provider's terms, so no license is expected here. This check is left out of the percentage.