Integrations
Connect it to what you already run
SignlOS integrates through open interfaces rather than a directory of logos: an MCP server for AI assistants, a scoped REST API, embeddable widgets, and public JSON for anything else.
Available today
What ships right now
Every item here works in the product as it stands. Nothing on this page is a plan.
MCP server
Claude and any other MCP client can read your boards, posts, votes, roadmap, changelog, and status — and write, with the right scopes. 9 tools on the same key as the REST API.
How it works →REST API
A versioned API at https://api.signlos.com/api/v1 with 14 scopes and per-key permissions. Everything the dashboard does against your data, your scripts can do too.
API reference →Embeddable widgets
Drop-in feedback, roadmap, and changelog widgets. One async script tag, no build step, and the feedback arrives with the context of the screen the user was on.
See widgets →Status badges
A live SVG badge for overall and per-component status. It is an image, so it works in a README, a docs site, a wiki, or an email — no script, no key.
Embed a badge →Public JSON endpoints
Everything published on your portal is readable without a key at /api/public/{workspace} — boards, posts, roadmap, changelog, and status. Build a dashboard, a bot, or a static page from it.
Read the docs →Email notifications
Status changes, release notes, and incident updates go to voters and subscribers automatically. There is no list to sync and no ESP to connect.
Release notes →Stripe billing
Subscriptions run through Stripe, including card management and invoices. Nothing to configure on your side.
Pricing →Not yet
What SignlOS does not have
If a native connector is a hard requirement, you should know before you sign up rather than after. These do not exist today:
- Native Slack, Jira, Linear, GitHub, or Zendesk connectors
- Outbound event webhooks
- A Zapier or Make app
- SAML or SCIM single sign-on
What to do about it
The REST API and MCP server cover most of what a native connector would do, with a script instead of a settings page. If you need one of the above natively, say so on the public board — the vote is what moves it up the roadmap, and you get told when it ships.
Request an integrationQuestions
Frequently asked
Your customers already told you what to build
It is in a support inbox, three Slack threads, and a spreadsheet nobody has opened since March. Put it somewhere it can be counted.
No credit card required to start. $0 forever.