Budna

Find and compare new and pre-owned items.

Discover new and pre-owned items on Budna that fit your needs and budget. Compare options, check condition and compatibility, and plan pickup or delivery before you decide.

The plugin connects to Budna’s public, read-only marketplace MCP server and bundles six Recommerce skills for comparison, complete kits, inspection, collection planning, keep-or-replace decisions, and reassessment. No account, API key, local server, or runtime dependencies are required for the default connection.

The plugin compares and explains options. It cannot bid, buy, reserve items, or contact sellers. Prices, availability, contents, and condition need current evidence; a recommendation is not a reservation or an inspection.

Install

From this checkout, use a current Claude Code release:

claude plugin marketplace add .
claude plugin install budna@budna-marketplace

Or use Codex:

codex plugin marketplace add .
codex plugin add budna@budna-marketplace

Start a new session after installation. To install from GitHub, replace . in the marketplace command with budna-marketplace/plugins.

In Claude web or desktop, add this repository as a marketplace from Customize → Plugins → Add → Add marketplace. Add the bundled connector from the plugin’s Connectors tab. A repository marketplace is separate from a reviewed public directory listing.

Install Budna in Codex from this repository or the universal budna-vX.Y.Z.zip release bundle. The budna-vX.Y.Z-openai.zip asset is for ChatGPT plugin import: its explicit no-auth metadata is not accepted by Codex CLI 0.164.0’s strict Agent Plugins MCP parser. The repository and universal bundle keep the portable MCP configuration and connect to the same public endpoint without credentials.

Clients and distribution

Claude and Codex have completed live skill and MCP tasks. Cursor desktop and CLI have completed a public shipping-rate task. Gemini CLI and OpenCode have discovered the six skills and connected to the MCP server; Copilot CLI direct repository installation has been checked. Discovery and connection checks do not establish live task coverage. Public listings require a separate submission or catalog review.

Use

• “Find a complete cordless drill, new or pre-owned, delivered to Gothenburg for under 1,000 SEK.”
• “Compare these listings by fit, complete cost, and unresolved condition.”
• “Prepare an inspection checklist for this listing.”

MCP connection

The MCP configurations point to https://api.budna.se/mcp: .mcp.json for Claude and Codex compatibility, mcp.json for Agent Plugins, and gemini-extension.json for Gemini CLI. The connection exposes public marketplace data and interactive listing cards where the client supports MCP Apps. Other clients receive the text and structured-data output. The server is maintained separately in budna-marketplace/mcp.

Personal account access is optional and is not enabled by this package. Follow Budna’s account connection instructions to connect https://api.budna.se/account/mcp through OAuth. That resource also includes the public tools; use one Budna connection in a session to avoid duplicate tools. Each client signs in separately and the user chooses the account permissions.

For OpenCode 2, run OpenCode from this checkout's root and add this configuration to opencode.json. Skill paths resolve from the active working directory. When using another project, change ./skills to the absolute path of this bundle's skills directory. Merge these entries with existing settings:

{
  "$schema": "https://opencode.ai/config.json",
  "skills": ["./skills"],
  "mcp": {
    "servers": {
      "budna": {
        "type": "remote",
        "url": "https://api.budna.se/mcp",
        "oauth": false
      }
    }
  }
}

OpenCode's MCP configuration and skill discovery are separate from its executable plugin system. No API key or OAuth login is needed for Budna's public endpoint.

Maintain

The six skill folders are unchanged copies of Recommerce at commit 31694a65b30a20103ff98a03ab435d753e0dac68, including their references and MIT licenses. Keep upstream as the source of truth: update complete folders from an explicitly selected commit, inspect the changes, and update this provenance when refreshing the bundle. The installed bundle contains regular files; no submodules or build step are required.

The client manifests share the same plugin name, version, skills, and public MCP endpoint. Keep every versioned manifest aligned for a release. Validate with a current Claude Code release:

claude plugin validate --strict --profile directory .

Also verify each client discovers the package and all six skills, and test a real supplied-listing task in each client. The installed skills and remote connection require no hooks or executable runtime dependencies.

Releases

Run the local checks before releasing with Node.js 24.12 or later. The TypeScript release tools and tests use Node’s built-in APIs and require no npm dependencies:

node scripts/release.mts check
node --test tests/*.test.mts

Use immutable vMAJOR.MINOR.PATCH tags. The numeric version must match plugin.json, .claude-plugin/plugin.json, .codex-plugin/plugin.json, and gemini-extension.json. Merge the versioned source to main, then create and push a fresh tag:

git tag v0.1.0
git push origin v0.1.0

The Release workflow validates the tag and main ancestry, runs the tests, and creates a draft GitHub release containing the universal ZIP and SHA256SUMS. Inspect the draft, then publish it from GitHub or a user-authenticated GitHub CLI:

gh release edit v0.1.0 --draft=false

Publishing the draft starts six jobs gated by the claude, openai, gemini, cursor, copilot, and grok GitHub environments. Each environment requires mjovanc to review and permits only v* tags, matching the MCP repository’s release gates. Self-review is allowed. There are no provider credentials in the bundle or environment configuration.

After approval, each job verifies the original release assets against the tagged source and exports its platform ZIP and checksum. Existing assets are never overwritten: a retry must match the original bytes. Release-tag updates and deletions are blocked by the repository’s Release tags ruleset. Keep GitHub’s release-asset immutability setting off for this flow because platform assets are attached after publication; the workflow enforces byte consistency itself.

The Claude job also publishes the verified Claude ZIP contents to the generated claude branch for directory review. Configure the directory submission to track that branch at the repository root; keep development and marketplace installation on main. Each branch commit records the release tag, source commit, and archive checksum. Publication uses fast-forward updates, rejects older versions or changed bytes for an existing version, and verifies every published file against the archive. Do not edit the generated branch manually.

The GitHub release exposes installable bundles. It does not approve or publish a provider directory listing. Complete the relevant portal submission, gallery indexing, or upstream catalog review from the table above. The tested extension has the repository topic gemini-cli-extension, which makes it eligible for Gemini CLI’s daily gallery indexing.

Public listings require their own connection tests, listing assets, and review; pushing this repository does not publish a listing.

Privacy policy · MIT · Budna