Brickbank

cc.brickbankPublished by brickbank.ccOfficial publisherv0.1.0Updated Oct 31, 2026

Finished jobs, paid per result. One MCP address for every live tool action in the store's blocks.

VerifiedStreamable HTTPWeb executableProductivity & WorkflowBusiness & Commerce

Overview

AI-generated overview

Brickbank is a remote MCP endpoint that gives an assistant access to a store of live tool actions, with finished jobs paid per result.

What you can do
  • Connect to a single MCP address that exposes the live tool actions available in the Brickbank store's blocks.
  • Run jobs through those actions and receive finished results.
  • Results are billed per result rather than by subscription, according to the provider's description.
When to use it
Worth considering when you want an assistant to reach a catalog of ready-made tool actions through one remote endpoint and are comfortable paying per completed result.
Requirements
A remote streamable HTTP endpoint at brickbank.cc; no local package or runtime is needed. A Brickbank run key is required as a bearer token in the Authorization header, created in the provider's account area. Network access to the endpoint is required.
Before you install
The Authorization header carries a secret run key, so treat it as a credential and keep it out of logs and shared transcripts. Usage is paid per result, so jobs can incur charges. The manifest lists no tools, so what the actions do and what data they send to the provider cannot be verified from the supplied information.

Installation

In SourceWeft

  1. Open Brickbank in the dashboard and add it to a workspace.
  2. Connect Authorization token 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/cc.brickbank%2Fbrickbank/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.

{
  "mcpServers": {
    "brickbank": {
      "type": "http",
      "url": "https://brickbank.cc/mcp",
      "headers": {
        "Authorization": "Bearer <YOUR_TOKEN>"
      }
    }
  }
}

Tools

0
This server asks for a credential such as an API key, so SourceWeft could not read its tools without one and has not indexed them.

Version history

1
  1. v0.1.0LatestOct 31, 2026

Score

56% 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

    Publish an icon in the registry entry.

  • 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.