Skip to Content
DocumentationDevelopersHeadless · Momen BaaS

Headless · Momen BaaS

Momen provides an integrated no-code experience for designing interfaces, modeling data, building business logic, and publishing applications. If you want to develop the frontend with your own technology stack or AI coding tools, Momen BaaS gives you access to the database, Actionflows, AI Agents, user permissions, media, and other backend capabilities in a Momen project. Whether you are vibe coding a new application or connecting an existing frontend, Momen provides a stable, robust backend with visual development tools.

Understand the headless architecture

In a headless architecture, the external frontend and Momen backend are developed and deployed separately, then connected through the Runtime API:

  • External frontend: Runs in your codebase and deployment environment and handles the interface, interactions, and client state.
  • Momen backend: Provides managed database, Actionflow, AI Agent, user and permission management, and file and media services.
  • Runtime API: Provides HTTP and WebSocket interfaces for the external frontend to call deployed backend services.

What services the Momen backend provides

Core services

Momen provides the following services through one managed backend:

ServiceWhat it provides
DatabasePostgreSQL tables with relations, constraints, indexes, aggregations, and computed fields
ActionflowsSynchronous or asynchronous server-side business logic composed from nodes
AI AgentsOne-off tasks and multi-turn conversations using knowledge bases, tools, and context
Third-party APIsExternal APIs imported and called through the Momen backend
PaymentsStripe and Airwallex payment capabilities
Users and authenticationUser accounts, sign-in, and sessions
PermissionsRole, data, and action permissions that control access to services and data
Files and mediaImage, video, and file upload and management
Real-time dataUpdates pushed to clients when data changes

How services are exposed

Momen generates a Runtime GraphQL API from the project configuration. The GraphQL schema describes the fields, arguments, and return types available in the current project.

HTTP endpoint for queries and mutations:

https://villa.momen.app/zero/{projectExId}/api/graphql-v2

WebSocket endpoint for subscriptions:

wss://villa.momen.app/zero/{projectExId}/api/graphql-subscription

projectExId is the unique identifier of the project. Copy the URLs from Developer access instead of constructing them manually.

The Runtime API applies project permissions according to the request identity:

  • A request without an Authorization header runs as a guest.
  • A request with Authorization: Bearer <jwt> runs with that user’s roles and permissions.
  • A request with Authorization: Bearer <admin_token> runs as a project administrator and is intended only for local development, scripts, or trusted servers.
⚠️

Never include an Admin Bearer Token in a website, mobile app, public repository, or any other code delivered to end users.

See the Runtime API Reference for complete request formats and API details.

Develop and connect the Momen backend

You can develop the frontend and Momen backend together in an AI coding tool. Alternatively, build the backend in the Momen editor, then connect an external frontend with the Skill or Runtime API.

Develop with an AI coding tool

After installing the Momen Plugin, tell the AI which Momen project the current codebase should use and what business feature you want to build. The AI can write frontend code, create or update the Momen backend, sync the backend changes, and complete the frontend calls.

Install the Plugin

The Momen Plugin works with Claude Code, Codex, and Cursor. opencode and other MCP-compatible tools connect to momen-mcp directly. Source and details: Momen no-code Plugin.

Pick your tool:

Claude Code

Terminal:

claude plugin marketplace add momen-tech-org/momen-nocode-plugin claude plugin install momen-nocode@momen

Claude Code CLI:

/plugin marketplace add momen-tech-org/momen-nocode-plugin /plugin install momen-nocode@momen /reload-plugins

Or run /plugin to open the plugin menu and add the marketplace interactively.

Claude client:

In the desktop app (Mac / Windows) or an IDE extension, just say:

Add the Git marketplace momen-tech-org/momen-nocode-plugin, then install momen-nocode@momen

Or type /plugin to open the plugin menu, same as the CLI.

Codex

Terminal:

codex plugin marketplace add momen-tech-org/momen-nocode-plugin codex plugin add momen-nocode@momen codex plugin list | grep momen # verify

Codex CLI:

Run /pluginsAdd Marketplace → enter momen-tech-org/momen-nocode-plugin → install momen-nocode.

Codex client:

Just say it in the chat box:

Add the Git marketplace momen-tech-org/momen-nocode-plugin, then install momen-nocode@momen

Or type /plugin creator, pick the system plugin, and ask it to install the repo.

Cursor

Requires Cursor 2.5+. You get the momen-platform skill and the momen MCP server.

Cursor client (team or organization):

An admin adds https://github.com/momen-tech-org/momen-nocode-plugin as a team marketplace in Cursor Teams / Enterprise. Members then install momen-nocode from the plugin list.

Terminal (local development):

git clone https://github.com/momen-tech-org/momen-nocode-plugin.git cd momen-nocode-plugin ln -s "$PWD/plugin" ~/.cursor/plugins/local/momen-nocode

Reload the Cursor window, then enable momen-nocode in the plugin settings.

opencode

In the chat box:

Just ask:

Install the Momen plugin from https://github.com/momen-tech-org/momen-nocode-plugin

Manual configuration:

opencode doesn’t read the Claude Code / Codex plugin marketplace, so wire up the MCP server and the skill yourself.

Add the MCP server to opencode.json in your project root, or merge it into your existing mcp block. Note the shape differs from the generic mcpServers below:

{ "$schema": "https://opencode.ai/config.json", "mcp": { "momen": { "type": "local", "command": ["npx", "-y", "momen-mcp@latest", "mcp"], "enabled": true } } }

opencode loads skills from <name>/SKILL.md, so symlink momen-platform out of the Plugin repo:

git clone https://github.com/momen-tech-org/momen-nocode-plugin.git cd momen-nocode-plugin mkdir -p ~/.config/opencode/skills ln -s "$PWD/plugin/skills/momen-platform" ~/.config/opencode/skills/momen-platform

For one project only, link it into .opencode/skills/momen-platform instead.

Other MCP-compatible tools (Windsurf, Cline, Trae, Claude Desktop, and more)

These don’t read the plugin marketplace, but they connect to momen-mcp directly. Add this to the tool’s MCP config:

{ "mcpServers": { "momen": { "command": "npx", "args": ["-y", "momen-mcp@latest", "mcp"] } } }

You get every Momen tool — data model, Actionflows, data bindings, logs. The guided momen-platform skill ships with the Plugin; you can also drop it into the tool’s skills directory, as shown for opencode.

Requires Node.js 18+. On first run you’ll be prompted to sign in to Momen and pick a project. To sign in ahead of time:

npx -y momen-mcp@latest login

Develop with the Plugin

After signing in, describe the complete business goal in natural language. For example:

Use the Momen project "Order Management" as the backend for the current project. Create the data structures, permissions, and server-side logic required for ordering, then sync the backend changes. In the current codebase, implement the order list, order details, and order submission.

The AI updates the Momen backend and the current codebase together. If it needs a decision about the data model, permissions, or business rules, it asks before making the change.

Build the backend in the Momen editor

You can also configure data models, permissions, Actionflows, AI Agents, and third-party APIs manually in the Momen editor or with its built-in AI assistant. When the backend is ready, run Sync changes and inspect the current Runtime Schema in Developer access.

Then choose one of the following ways to connect an external frontend.

Connect the frontend with the Skill

The Skill gives an AI the integration conventions for a Momen project’s backend Runtime API. It can guide the AI in connecting the current codebase to a deployed Momen backend, but it cannot create, modify, or sync the backend configuration.

Send the following instruction to your AI coding tool:

Carefully read and install the development skill from this repository: https://github.com/momen-tech-org/momen-baas-skill

Or install it from a terminal:

npx skills add https://github.com/momen-tech-org/momen-baas-skill -g

After installation, tell the AI which Momen project to connect and what frontend feature to implement. For example:

Connect the current frontend to the Momen project "Project name or project ID." Use the deployed Momen backend to implement the product list and product details.

Use the Runtime API manually

Open Developer access from the Momen top navigation to copy the project endpoints and Admin Bearer Token, then use the built-in GraphiQL panel to write and test requests against the current schema.

The following example reads records from a post table. Replace the table and field names with those in the current project schema.

query ListPosts { post(limit: 10, order_by: { created_at: desc }) { id title } }

Base subsequent queries and calls on the current GraphQL schema shown in Developer access.

Continue development

After the first connection, the frontend and Momen backend can evolve independently. With the Plugin, continue describing business requirements in natural language so the AI can update both the backend configuration and frontend code. When using the Momen editor, sync backend changes first, then update frontend calls against the latest GraphQL schema.

Momen also provides complete visual frontend development, preview, and publishing capabilities. You can design pages, bind data, and configure actions in the same project. To build both the frontend and backend in Momen, see the Editor Overview and Build Your First Page.

Last updated on