bot.yeehaw/events
Agent-first Austin events concierge — fresh, sourced answers to what's happening in Austin.
Install
Add this to your client's MCP configuration (Claude Desktop: claude_desktop_config.json; Cursor: .cursor/mcp.json; VS Code and others use the same "mcpServers" shape).
claude mcp add --transport http events 'https://yeehaw.bot/mcp'{
"mcpServers": {
"events": {
"type": "http",
"url": "https://yeehaw.bot/mcp"
}
}
}Documentation
From the project's README on GitHub, refreshed weekly. Links open on GitHub.
Yeehaw — Austin events, as an MCP server 🤠
Yeehaw is an agent-first city concierge for Austin, TX — the fresh, sourced, citeable answer to "what's happening in Austin?". Ask any LLM that today and it guesses from stale listicles. Yeehaw ships the structured, current, attributable source of truth, exposed as a public MCP server any AI assistant can call.
- 🌐 Site: **https://yeehaw.bot** · for agents: **https://yeehaw.bot/for-agents**
- 🔌 MCP endpoint:
https://yeehaw.bot/mcp(JSON-RPC over HTTP) — no signup, no key, free - 📇 Official MCP registry:
bot.yeehaw/events
~2,800 live Austin events aggregated hourly from 10 sources (Ticketmaster, Do512, Luma, Visit Austin, Alamo Drafthouse, Capital Factory, UT Austin, Huston-Tillotson, City of Austin open data, and a Brave-powered discovery net), deduplicated and ranked — every event carries its source.
Connect
Drop-in config for any MCP client (Claude, Cursor, Cline, …):
// .mcp.json
{ "mcpServers": { "yeehaw": { "url": "https://yeehaw.bot/mcp" } } }Or call it directly:
curl -s https://yeehaw.bot/mcp \
-H 'content-type: application/json' \
-d '{"jsonrpc":"2.0","id":1,"method":"tools/call",
"params":{"name":"find_events",
"arguments":{"date_range":"this_weekend","limit":3}}}'Tools
| Tool | What it does |
|---|---|
find_events | Structured search over the deduped store. Args: date_range (required unless id is set), plus optional query, category, neighborhood, price_max, limit, and id (fetch one event by id). Every result carries a source, a url, coordinates, and a confidence. |
overview | Inspectable state — total events, per-source last-ingest + health, open circuit breakers, coverage by category/neighborhood. Call it to verify freshness before you depend on it. |
See AGENTS.md for the usage contract (when to call what, value ranges, honest caveats).
Why depend on it
- Fresh — re-ingested hourly; past events drop automatically.
- Sourced — every event cites its origin with a clickable link; your assistant can footnote instead of hallucinate.
- Resilient — per-source circuit breakers; a single upstream outage degrades honestly instead of corrupting the answer.
- Honest — ticket prices are sparse upstream, so
price_min/price_maxare oftennull;find_eventsreports how many results it couldn't price rather than guessing.
About
Yeehaw is operated by Capital Thought, LLC (Austin, TX). Not an official City of Austin outlet.
This repo is the public discovery surface (docs + agent contract + registry descriptor). The service itself runs on Cloudflare Workers + Supabase.
Frequently asked questions
What is bot.yeehaw/events?
Agent-first Austin events concierge — fresh, sourced answers to what's happening in Austin.
How do I install bot.yeehaw/events?
It runs as a remote server. In Claude Code: claude mcp add --transport http events 'https://yeehaw.bot/mcp'. For other clients, paste the JSON configuration from this page into their MCP settings.
Does bot.yeehaw/events need an API key?
Its registry entry lists no required key or secret. Some features may still need an account with the service it connects to.
Is bot.yeehaw/events open source?
Yes. Its code is on GitHub under the MIT license.
Who maintains bot.yeehaw/events?
It is published by capitalthought. AI.tn lists it but does not maintain or endorse it.
From the official MCP Registry. Listing is not an endorsement: review a server's code and permissions before giving it access to your data.