AgentBill

io.github.marketinglior-pixelPublished by GitHub account marketinglior-pixelv0.3.1Updated Oct 24, 2026

One spend ceiling per agent job, as MCP tools. Bound to a task_ref you pass, not a calendar month.

VerifiedStreamable HTTPWeb executableFinanceAI & ML

Overview

AI-generated overview

AgentBill exposes per-job spend ceilings for AI agents as MCP tools, tied to a task reference you pass rather than a calendar month.

What you can do
  • Provides MCP tools that set and apply a spending ceiling for an agent job.
  • Ties each ceiling to a task reference supplied by the caller instead of a monthly billing period.
  • Available as a remote endpoint or as a local Python package over stdio.
  • No tool list is published, so the exact operations are not documented in the supplied material.
When to use it
Consider it when you want an assistant or agent workflow to operate under a defined budget per task, and you need that limit enforced through MCP rather than by monthly account caps.
Requirements
A remote endpoint at agentbill.dev or the local agentbill-mcp Python package over stdio. Authentication is OAuth and is required. No environment variables or headers are declared.
Before you install
It governs spending limits, so misconfiguration could allow more spend than intended; review how ceilings are set before relying on it. OAuth authorization grants the server access to your account. The tool list is not published, so verify what each tool does before use.

Installation

In SourceWeft

  1. Open AgentBill 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.marketinglior-pixel%2Fagentbill-mcp/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": {
    "agentbill": {
      "type": "http",
      "url": "https://agentbill.dev/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

3
  1. v0.3.1LatestSep 26, 2026
  2. v0.3.0Sep 25, 2026
  3. v0.1.1Sep 16, 2026

Score

60% 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.

  • License10 pts

    Declare a license in the repository or the registry entry.