Build
Connect your service
Your product, headless. Give an MCP server or an HTTP API a native front end inside a chat, with no app to build. What you need, how to paste it in, the preview, publishing and review.
More and more software is an API that people reach through agents. Alaskan gives yours a native front end inside a chat, with no app to build. If you have an MCP server, or an HTTP API with an OpenAPI file, it becomes an agent on Alaskan without any code written for us. You keep hosting it. Alaskan reads it, draws native screens for it, and calls it when people use it.
1. What you need
- An MCP server over Streamable HTTP (SSE works as a fallback), or an OpenAPI 3 file in JSON or YAML.
$refs are resolved. - If it needs a key: a bare token, which is sent as
Authorization: Bearer …, or one header line such asX-API-Key: ….
2. Paste the address into Alaskan
In the Alaskan iPhone app, paste the address to your agent (the first tab), or choose Connect a Service from the compose menu in Chats. Put the key after the address, or leave it out: if your service answers 401 or 403, your agent asks for it. Keys stay on the Alaskan server and never appear in listings.
3. Check the preview
Each tool or endpoint becomes a command, up to 12, and your agent lists what each one asks for. Say "call it …" to rename the bot. Operations that need a nested object as a required input are left out, and the preview names them.
| Your service has | People get |
|---|---|
| Input schemas | Native forms: text fields, date pickers, menus, steppers, sliders and toggles |
A destructive tool (destructiveHint: true) or a DELETE |
A confirmation before it runs |
| One text input on a tool like ask, query or search | Free text in the chat goes to it |
| Results | Label and value rows, stat tiles, tables, timelines, bar charts, images and link buttons |
For exact control, return {"_alaskan": {"nodes": [...]}} with nodes from the Alaskan protocol.
4. Publish
Tap Publish and choose the age rating (4+, 9+, 13+, 16+ or 18+), whether to list it in the directory, and the name people see as its maker. It gets a 4-digit code and a share page.
5. Review
A listed connected bot always waits for a moderator. Until it's approved, only you can use it. The moderator sees what it does, where its messages go and its age rating, then approves it or rejects it with a reason you'll see on the bot's page. Publishing a fix sends it back for review. An edit to a live bot that needs review is held: you see it straight away, and everyone else keeps the approved version until it's approved.
Once it's live
- Before installing, people see your maker name, your service's host as where messages go, and the age rating.
- Every call carries an
X-Alaskan-Userheader: an id for that person that only your service sees, so you can tell users apart. It stays the same for them on your bot, and it isn't a name, an email or their Alaskan id. - What your service receives is covered by your own privacy policy. See our privacy page and terms.
- People can report your bot. If several people who have used it report it, it's suspended until a moderator looks.
Bring your users with you
After you publish, your agent gives you a button to put on your site, in your docs and in emails. It opens your bot in Alaskan, or the App Store for people who don't have it yet:
<a href="https://alaskan.ai/b/1234"><img src="https://alaskan.ai/badge.svg" alt="Use it in Alaskan" width="180" height="48"></a>Replace 1234 with your bot's code. Your bot's page also shows how many people use it.