MCP and agents
How REM Vibe Coder works with the Model Context Protocol - your own MCP servers in builds, building and deploying MCP servers, and the REM CloudHub tools builds use.
REM Vibe Coder's builder is an AI agent. It can use tools from MCP servers, and it can build MCP servers for you.
Your own MCP servers in builds
Add an MCP server once in REM CloudHub (any sign-in it needs: none, a bearer token, a header, or OAuth; and which of its tools are read-only). From then on:
it is listed in Vibe Coder under Settings > MCP servers;
every build can call its tools as you, through REM CloudHub's gateway, so its credentials never enter the build's sandbox;
a tool that changes something shows a permission card first (Allow once, Always allow (this chat), No); read-only tools do not ask.
Example: with your ticket system's MCP server added, "build a dashboard of our open tickets by priority" lets the builder read real ticket fields while designing the app.
Your own skills
Skills are instructions written in REM CloudHub (Markdown with a SKILL.md). Each build mounts your skills read-only and reads the ones that apply, for example your naming rules or your API conventions.
Build an MCP server
Ask for one in plain words:
Build an MCP server with two tools:
convert_currency(amount, from, to)using the ECB daily rates, andlist_currencies().
Vibe Coder builds a Python server with FastMCP, tests it, and deploys it to REM CloudHub as an MCP app:
Transport | Streamable HTTP |
Endpoint |
|
Health |
|
Port inside the container | 8000 |
Connect it to any MCP client (an AI assistant, an IDE) with that URL. Who may call it is set on its page in REM CloudHub (sign-in required, allowed addresses, rate limit).
The REM CloudHub tools a build uses
Builds act in REM CloudHub only through its tools, and only with your REM CloudHub permissions; a tool your role does not allow is never offered.
Area | What a build can do |
|---|---|
Databases | Create the app's database, read its schema, run read-only queries |
Files and storage | Read your chat uploads, give the app its own storage folder |
Jobs | Register scheduled jobs (one confirm card for the whole list) |
Docs | Save documents, convert them to Word / PDF / Excel, publish on request |
Solutions | Create a solution, attach and arrange apps |
Git | Push the app's code to its repository and branches |
Status | Read what was done and the state of your apps |
Writes other than the everyday parts of a build (database, the app's own branch, your own solution) show a card first. A confirmation REM CloudHub itself asks for is never given by the agent: only your Allow sends it.
Calling Vibe Coder from your agent
Vibe Coder does not expose an MCP server of its own today. An agent can drive it through the HTTP API: create a chat with a prompt, follow the run's events, answer question cards, and read the deployed URL from the deploy event. See API reference and Run events.