Skip to main content
When Base44 builds a new app, it works from more than the prompt in front of it. It draws on knowledge about your platform, and reaches for tools that let it build on it. Teach Base44 about your platform and how to build on it using the following:
  • Skills: Saved instructions the agent reads while it builds. It includes things like your platform conventions and best practices.
  • MCP server: An external tool the agent can call while it builds, like a design tool or a data source.
The design system decides what an app looks like. Skills and MCP servers decide how it’s built.

​
Skills

A skill activates when Base44’s agent recognizes it as relevant to the current build, based on its description. A skill belongs to a workspace, so it applies to every app anyone builds there, no matter which account created it. You have two ways to shape that:
  • Write the description as a trigger, not a title. For example, “Use when building any form, table, or data-entry screen” works, but “Form and table conventions” does not.
  • Name the skill yourself in the app’s custom instructions. The custom instructions are injected into every interaction with the agent, so this is where you can say “apply the form-conventions skill” on your builders’ behalf. Custom instructions are set per app rather than per workspace, so your integration has to set them in the Create app call for each app.

Workspace skills

Write and manage workspace skills

Custom instructions

The one setting that is per app

​
MCP servers

For a white-label integration, the MCP servers you connect usually reach your platform’s own tools, APIs, or data sources, so Base44’s agent can build against your real data model. When building an app, the agent can call the MCP servers connected on the account of the builder running that build. That connection lives on the account, not the workspace, so it follows that account into every app and workspace it can access, not just the one where you set it up. Every build runs as the same account, so connect your servers once to that account and every build can use them. Sign in as that account to add them. A connection a workspace admin adds on their own account isn’t visible to builds that run as the integration account.
Two details that cost real integrations hours:
  • Base44 sends the headers you store on a connection exactly as entered. A bearer token’s value has to include the Bearer prefix. Base44 adds it only for connections that sign in with OAuth.
  • When a tool call fails during a build, the conversation records it with status set to error, and the reason isn’t part of the documented API response. Keep your MCP server’s own logs, and read them for the cause.
  • During a build the agent acts as the integration account, not as any end user. A connector connected per app user resolves only for that account’s own connection, and Base44 doesn’t fall back to another one. When the agent needs connector data while it builds, give the app an app-level or workspace connection and have the function use it when no per-user connection resolves.

MCP connections

Add and manage MCP connections

​
See also