Mcp MCP Server

Budna MCP

Use Budna from any compatible MCP client. Explore the public marketplace with no account or API key, or optionally connect your Budna account so your AI assistant can read your own account, listings, bids, offers, watchlists, saved searches, purchases, sales, disputes, messages, payments, notifications and ratings, with the permissions you choose. Budna MCP is read-only: it cannot change marketplace data.

Quick start

Shell (macOS / Linux)

Install a prebuilt binary without Node.js or Rust:

curl --proto '=https' --tlsv1.2 -LsSf https://github.com/budna-marketplace/mcp/releases/latest/download/budna-mcp-installer.sh | sh

PowerShell (Windows)

Run in PowerShell 5.1 or newer:

irm https://github.com/budna-marketplace/mcp/releases/latest/download/budna-mcp-installer.ps1 | iex

Restart your terminal if the installer adds its directory to PATH, then check budna-mcp --version.

npm / npx

Requires Node.js.

npm install --global @budna-marketplace/mcp

For clients that launch the server through npx:

command: npx
arguments: --yes @budna-marketplace/mcp

Homebrew

brew install budna-marketplace/tap/budna-mcp

Homebrew installs Rust automatically and builds from source.

Cargo

You need Rust 1.88 or newer.

Install the latest published release:

cargo install budna-mcp --locked

To install from a local checkout:

cargo install --path crates/budna-mcp --locked

Add to Codex

On macOS or Linux:

codex mcp add budna -- "$(command -v budna-mcp)"
codex mcp get budna

On Windows PowerShell:

$budna = (Get-Command budna-mcp).Source
codex mcp add budna -- $budna
codex mcp get budna

Start a new Codex task after adding the server, then ask:

Use Budna to find public camera listings.

The Codex MCP documentation covers project-scoped configuration and other client options.

Add to another stdio MCP client

Configure the absolute path returned by command -v budna-mcp (or (Get-Command budna-mcp).Source on Windows) with no arguments:

command: /absolute/path/to/budna-mcp
arguments: none

For JSON-config clients:

{
  "mcpServers": {
    "budna": {
      "command": "/absolute/path/to/budna-mcp",
      "args": []
    }
  }
}

What you can do

Budna MCP is read-only today. Public tools work with no account in the local budna-mcp binary and at https://api.budna.se/mcp. Account tools are available only on the hosted account resource, after you connect your Budna account and grant the permission they need. The account resource also serves every public tool, so one connection covers both the public marketplace and your own data.

In compatible MCP Apps clients you can also browse interactive listing cards and explicitly ask the AI to compare two to four selected listings.

Budna MCP cannot currently bid, make offers, buy, message, record views, change account settings, or otherwise change marketplace data.

Permissions you control

• When you connect an app, Budna shows exactly what it asks for and you choose which permissions to grant: Account (account:read), Listings (listings:read), Bids (bids:read), Offers (offers:read), Watchlists and saved searches (watchlist:read), Orders (orders:read), Notifications (notifications:read), Ratings (ratings:read), Payments (payments:read), Messages (messages:read), Profile (profile:read), Selling (selling:read), Following (following:read) and Company (company:read).
• Account tools name the other buyer or seller only by the public username the app shows, and never reveal who bid on a listing. Addresses, contact details and notification text are never included; message text is shared only with the Messages permission, and dispute statements only with the Orders permission.
• Under Account → Security → Connected apps you can remove a permission or disconnect an app at any time. Removing a permission takes effect immediately, including for access the app already holds; restoring it requires approving the app again.
• A connection lasts at most seven days before you approve it again.
• Disconnecting stops future access, but cannot recall information already shared with the AI service.

Where Budna MCP is going

Budna MCP is growing toward everything you can do in the Budna app and on the web. Next come actions such as bidding, making offers, buying, selling and managing your listings, and messaging. Each new capability will arrive behind its own permission that you grant per app, sensitive actions such as bids and purchases will ask for your explicit confirmation, and you can reduce or revoke access at any time. None of these actions are available yet.

Connect your Budna account

Add https://api.budna.se/account/mcp to your AI client as a remote (Streamable HTTP) MCP server. The client opens your browser to sign in to Budna at https://connect.budna.se and shows which permissions it requests; you choose which to grant. See Permissions you control for reducing or removing access later.

Other clients are not accepted yet. See Account access for the full permission model and the data each tool returns.

Use a non-production environment

Configure these values together so API requests, public listing links, and images stay in the same environment:

Remote API URLs must use HTTPS; HTTP is accepted only for loopback development servers. Listing and image values must be canonical HTTPS origins with no credentials, path, query, fragment, or wildcard host. The binary does not load .env files itself; .env.example is reference material.

For example, register a separate Codex server for another environment:

codex mcp add budna-nonprod -- /absolute/path/to/budna-mcp \
  --api-url https://api.your-environment.example/api/v1 \
  --public-listing-origin https://marketplace.your-environment.example \
  --image-origin https://images.your-environment.example

Equivalent environment variables are supported when your client can provide them.

Interactive cards

The Marketplace Explorer is embedded in the binary. Clients that support the MCP Apps extension can render listing cards, details, related/seller listings, and comparison selection. Other clients receive the same text and structured JSON fallback. See the extension support matrix for client coverage.

See the Marketplace Explorer guide for local HTTP testing, temporary-tunnel safety, privacy and attribution behavior, UI development, and release checks.

The project is licensed under the MIT License.