Agent-operable. Email, API & MCP

Support and feedback,
run by your agent.

A real help desk, feedback board, roadmap, and changelog. Email lands on your board. Your agent sorts it, drafts the reply, and updates the docs. You approve what goes out.

No credit card · you approve every send

Board · Support
SB
New3

Invoice #4021 charged twice

urgentLN

Can't reset my password

accountOB

CSV export cuts off rows

bugGR
Triaging2

Feature request: dark mode

featureCL

Webhook retries firing twice

apiMW
✦ draft reply ready
Resolved2

Onboarding email typo

shippedLH

Slow board loading

shippedMW

1

board for tickets, feedback, and bugs

15+

agent tools over MCP and REST

1 click

to approve a drafted help doc

0

replies sent without your OK

The problem

Support is a pile of email
nobody wants to touch.

Tickets sit for days. The same question gets answered fifty times. The help docs went stale three releases ago, and you find out when a customer does. You care. It just never reaches the top of the list.

How it works

Your inbox, handled
in three steps.

01· connect

Connect your inbox

Forward your support email. Every message becomes a ticket on your board, sorted and tagged.

02· work

Your agent works the board

It reads every ticket, sets priority, links duplicates, and drafts a reply in your voice. Same tools your team uses.

03· approve

You approve

One click sends the reply. The help doc and changelog update themselves. Nothing goes out without you.

The board

One board
for everything.

Support tickets, feature requests, and bugs land in one place. Drag a card, change its status, ship it. It's a normal Kanban board. Your agent can move every card too.

New

Invoice #4021 charged twice

urgent

Can't reset my password

account

CSV export cuts off rows

bug
Triaging

Feature request: dark mode

feature

Webhook retries firing twice

api
Resolved

Onboarding email typo

shipped

Slow board loading

shipped

What's inside

A complete support stack,
not a widget.

Help desk

Email tickets on a Kanban board. Statuses, priorities, tags, assignees.

Feedback & roadmap

Public boards with upvotes. Ship an idea and everyone who asked hears about it.

Help center

Docs that write themselves. Ship a feature, approve the draft, it's live.

Changelog

Post product updates to a public page and your subscribers' inboxes.

API & MCP

Every action is a tool. Point your agent at it and it runs your support.

The agent layer

Every button is a tool
your agent can use.

Superboard exposes the whole product over a REST API and an MCP server. Give Claude, or any agent, a key. It can triage tickets, answer them, publish docs, and cut a changelog. You decide what ships.

claude mcp add --transport http superboard \
  https://superboard.dev/api/mcp \
  --header "Authorization: Bearer sb_live_..."
One command in your terminal. Keys come from Settings → API keys.

Close the loop

The loop closes itself.

A user votes
You ship it
Everyone who asked gets notified
It becomes a changelog entry

Early access

Get early access.

We're onboarding teams now. Leave your email and we'll set up your board.

Waitlist status

FAQ

Fair questions.

Is it just an AI chatbot?

No. It's a full support and feedback platform you can run by hand. The agent is an operator on top, not the only way in.

Do replies send automatically?

Only if you turn that on. By default your agent drafts and you approve.

How does email work?

Forward your support address to Superboard. Replies come from your domain.

Can I use my own agent?

Yes. Anything that speaks MCP or HTTP can drive Superboard.

Your agent, tomorrow morning

Triage today's tickets, draft the replies, and update the docs for what we shipped.

Give your support desk an operator.

Get early access