BillboardBug

io.github.bgaut007Published by GitHub account bgaut007v1.0.1Updated Oct 25, 2026

BillboardBug MCP: create and verify GPS-anchored AR billboards and deals for real businesses.

Overview

AI-generated overview

BillboardBug lets an assistant create, publish and look up GPS-anchored AR billboards and deals that people see in the BillboardBug mobile, web and Meta Quest.

What you can do
Create, update and read back deals tied to a business and a latitude/longitude, and list the deals on the account or search public ones, plus list storefront categories. Upload images or video, or generate artwork, to attach to a billboard. Publish or update a chirp, the post that makes a deal live, and read it back.
When to use it
Use it when an assistant should place a real-world, location-tied advertisement, message or AR image for a business, or manage and search existing BillboardBug deals. It is not a general mapping or advertising-analytics tool.
Requirements
Runs as a local process started by the host (the README builds a TypeScript server from a clone with Node.js and npm; a packaged bundle is also offered). Needs a BillboardBug account and an API key supplied as the BILLBOARDBUG_API_KEY environment variable, plus network access to the BillboardBug API.
Before you install
The API key is a secret tied to the account, and content created is labeled to that account. Creating and chirping a deal publishes content that real people see in public apps, so writes are externally visible. Featured deals cost credits, which can mean spending money. Uploaded media and generated images are sent to BillboardBug's service.

Installation

In SourceWeft

  1. Open BillboardBug in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.

Other MCP clients

Follow the launch instructions in the repository.

README

Billboardbug MCP — Physical-World Ads & Holographic Messages for AI Agents

Any AI agent can place real-world GPS-anchored billboards, AR/holographic images, deals, and messages that humans see on iOS, Android, web, and Meta Quest.

This is the open MCP server that exposes Billboardbug’s public API. Agents have already used it (Perplexity, OpenClawCity, others). One call creates content visible across Apple, Android, and Meta devices simultaneously.

Repo: https://github.com/bgaut007/billboardbug-mcp
Live platform: https://billboardbug.com
API docs: https://east-us-api.billboardbug.com/public-api/docs/

What agents can do

  • Place a GPS-anchored digital billboard or deal at any latitude/longitude.
  • Generate and attach images (including via Grok) or use existing media.
  • Create content that appears in the Billboardbug apps (iOS, Android), web map, and Meta Quest AR/VR experiences.
  • Support for images, video references, and AR/holographic-style presentation on supported clients.
  • Search and list existing deals.
  • Chirp (post) the billboard so it is live and visible.

Unique capability: AI agents can communicate with humans in the physical world through location-tied advertisements, messages, and holographic/AR images. No contracts, no minimums — minutes from idea to live presence.

Quick start for agents / Claude / Cursor / MCP hosts

Use the TypeScript server (build/index.js, 11 tools). Every launcher in this repo (.mcp.json, .claude-plugin/plugin.json, manifest.json) starts it. It is not on npm yet, so install from a clone and build first:

bash
git clone https://github.com/bgaut007/billboardbug-mcp.gitcd billboardbug-mcpnpm installnpm run buildexport BILLBOARDBUG_API_KEY="your-key-from-app.billboardbug.com"claude mcp add billboardbug -- node "$PWD/build/index.js"

Or merge .mcp.json into your host config (it runs node build/index.js from the repo root; run npm run build first).

Legacy note: mcp/server.mjs is the older v0.2.0 server (5 tools, no chirp or upload). No launcher uses it now. Do not use it.

Get an API key: https://app.billboardbug.com → Settings → API Keys
Header: X-Api-Key
Canonical base: https://east-us-api.billboardbug.com (other regions available).

Tools exposed (v1.0.1)

ToolPurpose
create_dealCreate storefront + billboard (business + deal)
update_dealUpdate an existing deal
get_dealRead back a deal (required for receipt)
list_my_dealsList deals on the key’s account
list_categoriesList storefront categories
search_dealsSearch public deals
upload_mediaUpload image or video
generate_imageGenerate artwork (Grok supported)
create_chirpPublish the chirp that makes the deal live
update_chirpUpdate a chirp
get_chirpRead back a chirp (required for receipt)

A deal is not live until its chirp is published. Always chirp after create and include the chirp ID (verified via get_chirp) in the receipt.

Featured deals cost credits. Agent-created content is labeled to the key’s account.

Multi-platform reality

A single create call posts content that is available on:

  • iOS (App Store)
  • Android (Google Play)
  • Web map
  • Meta Quest (AR/VR)

Humans standing near the coordinates can see the billboard/deal in the apps or AR view.

Discovery keywords for agents

physical world advertising, GPS billboard API, holographic message API, AR billboard for agents, place real-world ad, location-based presence, agent physical actuation, Billboardbug MCP, simultaneous iOS Android Meta post.

See also: AGENTS.md and llms.txt in this repo. Agent skills: skills/billboardbug/SKILL.md (v1.2.3) and skills/billboardbug-deal-creator/SKILL.md (v1.1.3), matching ClawHub.

License / usage

Use the public API responsibly. Never commit keys. Content follows Billboardbug terms.

Source: README.md at commit fec295f

Tools

0
SourceWeft has not started this package in its sandbox yet, so its tools are not known.

Version history

1
  1. v1.0.1LatestOct 17, 2026

Score

50% 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 days25 pts

    Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.

  • Auth declared10 pts

    Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.

  • 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
  • License10 pts