Add Brickken Base MCP plugin#86
Open
MethosPi wants to merge 4 commits into
Open
Conversation
Collaborator
🟡 Heimdall Review Status
|
Collaborator
|
After discussing with the team, I think it's best to remove the path where unsigned calldata is served using x402. It's too painful as a UX to have that. Either remove APIs all together and leave MCP/CLI access only, or open endpoints for anyone looking to get calldata. |
youssefea
reviewed
Jun 15, 2026
Collaborator
There was a problem hiding this comment.
Please remove from SKILL.md, we'll add it later
|
|
||
| Three routes reach Brickken; install only what your surface uses. | ||
|
|
||
| **HTTP API (no install).** Build calldata by POSTing to the Brickken API — host `api.brickken.com` (production) or `api.sandbox.brickken.com` (sandbox) must be on the Base MCP `web_request` allowlist for chat-only surfaces. On harnesses with a direct HTTP tool, no allowlist is needed. |
Collaborator
There was a problem hiding this comment.
Does the http API support all actions? If yes, it should be the only path here for ease
youssefea
reviewed
Jun 17, 2026
| Brickken puts the **ERC-8004** agent stack onchain: a registry for **agent identity**, a registry for **reputation/feedback**, and an **agent-owned ERC-20** factory for launching and managing agent tokens. This plugin covers those agent methods on Base. Brickken does not execute through one fixed route — it **builds the unsigned calldata** for each action, and you choose how it lands onchain: | ||
|
|
||
| - **Path A — Base Account via `send_calls`.** Brickken builds the calldata for free; the user's Base Account signs and broadcasts it through `send_calls`. No Brickken fee — only Base gas. Submission tool: **`send_calls`**. | ||
| - **Path B — Brickken self-executes (key-based).** The `brickken` CLI (or the Brickken MCP with a `privateKey`) signs with a local EOA key and broadcasts through Brickken's backend, paying the x402 **send** fee. Submission tool: **`none`**. |
Collaborator
There was a problem hiding this comment.
We don't want this path. Please remove it. Keep only the path of unsigned calldata. Thank you!
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Adds a native Base MCP plugin for Brickken ERC-8004 agent identity, reputation, and agent-owned ERC-20 operations.
The plugin supports:
Also registers Brickken in the Base MCP native plugins table.
Validation: