Open source · MCP server · Works in Claude and Codex
Work the room. Keep everything.
event-hog gives a team working a conference one shared workspace inside the AI they already use. Prep before. Contacts, notes and slides during. Follow-ups after. You talk to it in plain words, and nobody stops a conversation to fill in a form.
Apache-2.0 · first worked the floor at the 7x24 Exchange, Fall 2026
- “Who is this?”
- “Log this person. We talked about cooling loads.”
- “Who have we met from Schneider?”
- “What's the plan for today?”
- “Write up these slides.”
- “Quiz me on the acronyms.”
- “Move today's contacts into the CRM.”
Why it exists
The lost
& found desk
A conference is days of conversations that matter, and most of them get lost. By the time anyone opens the CRM, the week is a blur. event-hog keeps it while you're still in the room.
- 001 Lost Badge photos, forgotten in a camera roll Found One contact file per person, made from the photo
- 002 Lost Notes split across four phones Found One shared workspace, every entry signed
- 003 Lost Two teammates met the same buyer, separately Found Both conversations land in the same file
- 004 Lost 200 slide photos nobody reopens Found Transcribed, summarized, searchable
- 005 Lost The CRM, updated a week too late Found Proposed the same day, yours to approve
What it does
The program
Everything event-hog does, laid out like the agenda it's built for. Each session names the skill Claude loads and the tools it calls, so you can check the claim against the code.
Before
Know the room before you walk in.
- Day 0 · 09:00
Read the conference for you
Hand it the event's site. It reads the agenda, the speakers and the sponsors, and builds a prep map: who's in the room, why they matter, which sessions count, and how the team splits up.
In progress The event-prep skill isn't in the kit yet. It lives in lossless-agent-skills, written for Twenty.
Room prep/
Track event-prep
- new_event
- event_brief
- Day 0 · 14:00
Research speakers and panelists
A thin event-app bio, often just a screenshot, becomes a sourced profile. Social accounts first, then coverage about them, then quotes, then video. Capped at what's relevant, so it reads in a minute.
Room speakers/
Track augment-speakers-panelists
- save_speaker_profile
- set_my_research_tools
During
Keep everything while you talk.
- Day 1 · all day
Keep one contact list for the whole team
Log someone from a badge photo, a business card, a voice memo, or two thumb-typed lines. One file per person; every teammate's interactions and observations append to it, so two people who met the same buyer see each other's notes. A database underneath answers "who have we met from this company?" and "who's in Texas?". The CSV is always current.
Room contacts/
Track log_contact
- log_contact
- search
- query_crm
- who_is_in
- contacts_csv
- Day 1 · 10:45
Write ahead of you
Before a panel, it drafts what you'll want: flash cards for the acronyms and standards likely to come up, and post drafts with [gaps] to fill. After you log something, it fills the gaps from your notes, in the company's voice or yours. It never invents what was said, and it never posts.
Room flash-cards/ · drafts/
Track parallel-content-generation-starters
- save_flash_cards
- flash_cards
- save_draft
- add_to_draft
- Day 2 · 11:30
Capture slides, with metadata
Each photo is shrunk to the smallest size that's still legible, with its location data stripped. Each slide gets a verbatim transcript, its type, a one-sentence core message, metrics as printed, claims worth checking, and alt text. Each session gets a write-up that tells the talk slide by slide.
Room slides/
Track capture-slides
- upload_link
- slides
- view_slide
- save_slide_notes
- Day 2 · 18:00
Keep the team in step
"Who did we meet today, and by whom? Which priority people has nobody found yet? What follow-ups are open?" One question at the end of the day, answered on a phone screen.
Room the lobby
Track daily-brief
- event_brief
- recent_activity
After
Turn the week into something.
- Day 4 · 09:30
Recreate slides in your brand
A slide worth keeping is rebuilt as a clean slide in your own design system, credited to its source, ready for your own decks. No DESIGN.md yet? It drafts one from your company's site first.
Room slides/
Track recreate-slides-in-brand
- save_recreated_slide
- get_design_system
- extract_brand
- save_design_system
- Day 4 · 13:00
Share the write-up
Slide notes and recreated slides become a page at a link, for the people who weren't there.
In progress Recreated slides publish themselves. A whole slide-notes page is still published by hand.
Room /media/
Track hosted pages
- upload_link
- Day 4 · 16:00
Send contacts on to your CRM
Each contact is proposed first and created only after a person says yes, owned by whoever met them. HubSpot works today through a paired connector. Any other CRM gets an import file.
Room exports/
Track crm-sync
- crm_queue
- mark_crm_synced
- export_hubspot_csv
Two ways to run it
Pick your pass
Both passes run the same server and make the same workspace: plain markdown files, one per contact, and a CSV. Start on ours; move to your own when you want the data on your account.
-
Pass 1
Use our Cloudflare
- Copy one prompt, paste it into your agent, done
- A shared workspace per event: git repo, database, image host
- Attendee research with lead enrichment built in
- Contacts, meetings and follow-ups go to your CRM after a yes
Needs Nothing to deploy. Pick up your badge below.
All Access
-
Pass 2
Self host
- The same server, on your own Cloudflare account
- Your data never reaches us
- Your own people, your own enrichment key
- Fork it and change anything
Needs A Cloudflare account with Artifacts, D1 and R2.
Exhibitor
Registration
Pick up your badge
Copy this prompt and paste it into Claude, ChatGPT, Cursor, Claude Code or Codex. It carries your own private link, and your agent connects itself, or walks you through the two clicks.
- Your agent asks which company you represent and which conference you're going to.
- It works out whether you're before, during or after the show, and picks up from there.
Your setup prompt
Set it up by hand instead
Your link:
- Claude (web, desktop, mobile): Settings, Connectors, Add custom connector. Name it event-hog and paste your link.
- Cursor: add
"event-hog": { "url": "your link" }undermcpServersin~/.cursor/mcp.json. - Claude Code:
claude mcp add --transport http event-hog your-link - Codex: in
~/.codex/config.toml, add[mcp_servers.event-hog]withurl = "your link".
Your link works like a password: anyone with it can write as you. This browser remembers it, so come back here to copy it again. Everything you log goes into a workspace shared with everyone on this deployment. event-hog never posts or emails anything, and never writes to your CRM by itself.
The workspace
Floor plan
Every event gets the same layout: a folder of plain markdown files anyone can read, with or without us. Databases and CRMs are views of it, and can be rebuilt from it.
Fine print
What's enforced, what's asked
Some behaviour is guaranteed by the server's code. Some is an instruction to the model, which a model can fail to follow. We list both, because "does it do what we think it does?" is the first question a CTO should ask.
The server guarantees
- Every write is a git commit authored as the person who made it.
- Writes add or append. A contact’s known fields are never overwritten.
- Upload links are signed, single use, and expire in 15 minutes.
- Recreated slides with scripts, or without a source credit, are refused.
- Hosted HTML is served sandboxed: no scripts, no forms.
It asks the model to
- Search before logging someone, and never invent a field.
- Propose CRM records, and create them only after a yes.
- Draft posts; never post.
- Keep hallway conversations out of anything public.
Your data is yours. On your own Cloudflare account it never reaches us. On ours, it's stored so your team can use it and is never looked at or used commercially. Read the data policy.
Exhibitors wanted