io.github.Okam-ASPublished by GitHub account Okam-ASv1.0.0Updated Oct 30, 2026
Build a Norwegian restaurant's own ordering site on Okam. Call kit_learn first. No sign-in to build.
Okam's remote MCP server lets an assistant build a Norwegian restaurant's own ordering site and run guest ordering flows: menus, carts, delivery and checkout.
Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.
Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.
Read https://sourceweft.com/mcp/io.github.Okam-AS%2Fokam/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.Add this to your client's mcpServers config.
{
"mcpServers": {
"okam": {
"type": "http",
"url": "https://api.okam.no/mcp"
}
}
}Update cart line
Update quantity, notes, or selected options on an existing cart line item. Quantity <= 0 removes the item.
notesstoreIdrequiredquantityrequiredlineItemIdrequiredselectedOptionIdsList stores
List stores available to the current user. Optional longitude and latitude improve distance sorting.
latitudelongitudeRead a verify run: what passed, what to fix
Store key: call after running the verify command, with the runId of that latest run. Pass or fail per check, and whether the server saw the run's sandbox order paid; when green, the go-live list. The CLI's PASS/WAIT/FAIL lines are authoritative: checks that only WAITed (sandbox guest sign-in) are missing here, so a run with no FAIL in the CLI has nothing to fix. While the store is closed the payment checks FAIL; rerun while it is open. If every check FAILed with locator.waitFor: Timeout, no menu item appeared: the server stopped or the origin differs from storefront_connect's; fix it and rerun. The record changes only when verify runs again.
runIdstorefrontKeyConnect a running site and get its verify command
Store key: call when the site is served from a process that keeps running (background, fixed port) and menu items show at that origin. Use http://localhost:<port>, not 127.0.0.1: the sandbox key allows only localhost. Returns whether the origin is allowed, a runId and the exact verify command; run it as returned while the site runs. Sign-in and every check after it WAIT until the sandbox guest exists: report them, never stub sign-in. If originAllowed is false, read kit_docs_get topic onboarding. Each call starts a new run; use the latest runId. Example: {"storefrontKey":"pk_test_…","origin":"http://localhost:5173"}.
pathoriginstorefrontKeyList menu
List categories and products, with each product's allergens, for a store after delivery type has been selected. Delivery type affects product availability and prices. Results come in pages of whole categories; when nextPage is set, call again with that page for more.
pagestoreIdrequireddeliveryTyperequiredAdd to cart
Add a configured product to the cart. Use product_configure first for required variant option ids.
notesstoreIdrequiredquantityproductIdrequiredselectedOptionIdsVerify payment
Verify an external payment after the user has completed the returned payment URL. Provider is vipps or dintero.
providerrequiredpaymentReferencerequiredRead one Storefront Kit topic or reference block
Public: with topic, that topic as Markdown; read assemble-a-shop, world-class-ordering-ux, verify-contract and the-return-page before building, the others when the steps name them. With block: where to read that reference block's source; read it, never install it. Without arguments: the topic and block lists. Read each topic once. Example: {"topic":"world-class-ordering-ux"}.
blocktopicServer info
Public: basic information about the Okam MCP server.
Takes no parameters.
Start here: learn the Okam Storefront Kit
Public: call first whenever you build or change a restaurant's own ordering website on Okam. Returns the must-nots (the server owns every price, payment is the guest's own act), the build steps, the sandbox key, the topics and, with framework, the scaffold plan. The kit gives logic and outcomes, never a look: design the site from the restaurant's brief. Not for ordering food as a guest or for restaurant admin. Example: {"framework":"vite-react"}. Next: kit_docs_get for the topics the steps name.
frameworkkitVersionList payment methods
List payment methods available for the current cart/user. Saved Stripe cards have ids; Dintero and Vipps are returned as payment types.
storeIdrequiredValidate cart
Validate the current cart before checkout.
storeIdrequiredGet store
Get store details, including supported delivery types. Choose a delivery type before listing menu prices.
storeIdrequiredGet cart
Get the current cart for a store.
storeIdrequiredSet delivery
Set cart delivery type and delivery details. This must be called before listing product prices or adding products to cart.
citycommentstoreIdrequiredzipCodetableNametipAmountuseRewardtipPercentfullAddressdeliveryTyperequireddeliveryInstructionsCheck delivery address
Check whether Wolt delivery can deliver to an address and return the delivery price if available.
cityrequiredstoreIdrequiredzipCoderequiredfullAddressrequiredConfigure product
Get all variants, option ids and allergens for configuring a product before adding it to cart.
productIdrequireddeliveryTyperequiredStart checkout
Start checkout with Dintero or DinteroVipps. Returns a Dintero payment URL and reference; the guest approves the payment on Dintero's page. A zero-amount cart completes immediately. An unchanged cart gets the same payment link back.
storeIdrequiredpaymentTyperequiredRemove cart line
Remove a cart line item.
storeIdrequiredlineItemIdrequired83% of the applicable checks met
How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.
Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.
A hosted service is used under its provider's terms, so no license is expected here. This check is left out of the percentage.