Skip to main content

​
GenieForge Builder MCP

GenieForge Builder MCP lets you connect an MCP client (Claude, ChatGPT, Perplexity, and other clients that support remote MCP with sign-in) to apps you can edit. You can inspect the app and apply changes without using in-app Build chat for every step. This is an optional add-on on your GenieForge subscription. When Billing offers it, you can add it there. If you do not see it, contact support@genieforge.ai. This page does not quote prices. Editors on apps owned by someone who has the add-on can also connect. They can work on those apps; they cannot create new apps from this connection unless they have the add-on on their own subscription. Apps with an accepted BAA (HIPAA enabled) cannot use Builder MCP. You can still connect, then use it on your other apps. If you personally have the add-on, you can create a non-HIPAA app from the client. Apps where GenieForge has turned on HIPAA technical safeguards but the BAA is not yet accepted can be operated over MCP with two extra conditions: the sign-in you use to authorize the connection must include your authenticator app, and the connection must be re-authorized every 12 hours. This is the same 12-hour limit that applies to builder sessions on HIPAA apps. If the client reports that a HIPAA app needs a recent multi-factor MCP login, re-authorize the connection from the client. For regulated health data, see HIPAA and regulated health data and contact support@genieforge.ai.

​
Connect

  1. In your MCP client, add a custom remote MCP server.
  2. Paste this URL: https://builder-mcp.genieforge.ai
  3. Sign in with your GenieForge account when the client opens the authorization page. If you are signed out, GenieForge asks you to sign in, then returns you to this same page so you can finish authorizing.
  4. Choose which apps this connection can see. Scroll the page if you are on a phone. For each app, turn on Blueprint if the client should change the unpublished app, and Data if it should change customer records. Or choose Allow all apps I can edit, then use the same two columns for every current and future app.
The connection only lists the apps you granted. Blueprint write and data write are separate, and both start off. Existing connections that you authorized before this choice still see every app you can edit. Those older connections can apply blueprint changes if you allowed write then. They cannot write customer data until you turn Data on. You can change or revoke a connection later in Billing, under Builder MCP connections. Use Manage to open the same app table. If the client needs a write it does not have, it will give you a short-lived link to that page. That link highlights the app and offers a one-click Allow for the requested write.

​
What it can do

  • List the apps you granted this connection
  • Create a non-HIPAA app (only if the add-on is on your own subscription, and this connection has blueprint write)
  • List the apps you granted, each with its projects, so the client can ask which project to use
  • Add another project (workspace) on an app you already have, if you are an Admin on that app and this connection can write. Creating a new app still requires the add-on on your own subscription
  • Load authoring guides (the same manuals Build chat uses), grouped by area: pages, data, forms, and so on
  • Load argument lists for each building action before applying a change
  • Load page layout contracts and UI type catalogs
  • Inspect pages, files, components, libraries, roles, agents, tools, forms, and data structure
  • Inspect conversations, tasks, and usage signals on those apps
  • Apply blueprint changes (when you allow Blueprint write), including one-off code checks
  • Change customer data or send notifications (when you allow Data write)
  • Ask you to upload project files (PDF, Word, images, audio) through a short-lived upload page, or an in-chat picker when the client supports it. This needs Data write. Clients that can read files on your computer can still use the existing disk upload path.
  • Declare environment variable names (set the values yourself in App Settings)
  • Check that a page or capability works
Each building action that touches an app needs both the app and the project. The client should pick both from the app list and ask which project to use when the app has more than one. Do not assume the first project. Publishing the app still happens in the GenieForge sidebar. Environment variable values are not sent through this connection. In-app Build chat loads manuals for you. An MCP client does not have that helper, so this connection includes those authoring guides and argument lists as inspect tools the client can call first.

​
Transcripts

Each connection keeps one in-app MCP transcript per app and project while you are actively using it (about 30 minutes of idle time). Open the app in GenieForge to read the log, rename it, or toggle whether that transcript may write customer data (it starts read-only). Ask the client to start a new conversation when you want a fresh thread, or to set a title so you can find it in the list. Successful writes show a credit amount on that tool row. Apps with an accepted BAA still cannot be operated over this connection, and they do not get a transcript.

​
Credits

Successful applies show as MCP apply in Credit Usage and count toward the app’s Build total, not Chat. Failed applies do not charge. The add-on price is separate (this page does not quote it). The apply fee is the yellow number on that MCP transcript. If the apply also ran a model (an eval set, a capability check that called the app’s AI, or a sub-agent), that usage is a separate purple number. The two do not merge. If the app is out of credits, writes and checks stop. Lookups still work.

​
Clients that work

Paste the HTTPS URL in:
  • Claude (web, desktop, mobile, Cowork)
  • ChatGPT (custom connector on a paid plan, Developer Mode)
  • Perplexity (Pro, Max, or Enterprise)
These clients run on your machine and complete sign-in locally:
  • Claude Code, VS Code / GitHub Copilot in the editor, Gemini CLI, Zed, Amazon Q / Kiro, OpenCode, and similar MCP clients

​
Clients that do not support this path

  • Consumer Gemini on the web does not offer custom remote MCP. Use Gemini CLI instead.
  • GitHub Copilot cloud agent cannot sign in with this flow.
  • ChatGPT Free cannot add custom connectors.
If your client has its own connection steps, follow those. The GenieForge URL to paste is still https://builder-mcp.genieforge.ai.

​
If ChatGPT shows the connection as disabled

ChatGPT refreshes the GenieForge sign-in on almost every action. When that refresh fails, ChatGPT hides the GenieForge tools instead of showing an error, so a later apply (or even a simple list) looks like the connection died. Claude keeps the same sign-in for the chat and does not do this. GenieForge now keeps that refresh working through a long ChatGPT session. If you still see the tools disabled:
  1. In ChatGPT, open Settings, then Connectors (or Plugins), then GenieForge MCP, and use Refresh.
  2. Start a new ChatGPT chat and attach the connector again.
  3. Retry the change.
If Refresh still fails, sign in again from that same ChatGPT connector page. You do not need to change anything in GenieForge Billing unless you revoked the connection.