Qaema Menu

ai.qaemaPublished by qaema.aiOfficial publisherv1.0.0Updated Nov 5, 2026

Build and update Arabic & English QR menus for cafés and restaurants: items, prices, allergens.

VerifiedStreamable HTTPWeb executableBusiness & Commerce

Overview

AI-generated overview

Remote MCP server that lets an assistant build and update Arabic and English QR menus for cafés and restaurants, including items, prices and allergens.

What you can do
  • Create and update bilingual (Arabic and English) QR menus for cafés and restaurants.
  • Manage menu items with their prices.
  • Record allergen information on menu entries.
  • No individual tools are listed in the manifest, so the exact operations are not documented here.
When to use it
Useful when you run a café or restaurant and want an assistant to draft, translate or maintain a QR-code menu in Arabic and English, for example keeping prices and allergen notes current.
Requirements
A remote MCP endpoint at mcp.qaema.ai over streamable HTTP. OAuth authentication is required, so a Qaema account and an OAuth sign-in flow are needed. No environment variables or headers are declared.
Before you install
The server requires OAuth sign-in, granting it access to your Qaema account. It writes and changes menu content such as items, prices and allergens, so edits should be reviewed before publishing. Menu data is stored with the third-party provider.

Installation

In SourceWeft

  1. Open Qaema Menu in the dashboard and add it to a workspace.
  2. Connect the required credentials. They are stored privately and never shown on public pages.
  3. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

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/ai.qaema%2Fmenu/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.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config. The client completes OAuth sign-in on first connect.

{
  "mcpServers": {
    "qaema-menu": {
      "type": "http",
      "url": "https://mcp.qaema.ai/"
    }
  }
}

Tools

0
This server asks you to sign in, so SourceWeft could not read its tools without an account and has not indexed them. What a connected account sees can depend on that account and its permissions.

Version history

1
  1. v1.0.0LatestNov 5, 2026

Score

67% 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.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • LicenseNot applicable

    A hosted service is used under its provider's terms, so no license is expected here. This check is left out of the percentage.