Apper MCP Connector
Model Context Protocol · Streamable HTTP
Build Apper apps from ChatGPT or Claude
Connect Apper to ChatGPT or Claude and build complete applications through simple chat.
Describe the app you want in plain English. Your AI assistant uses Apper to create it, show you a working preview, add features, connect a database when needed, and make changes to your app directly from the conversation.
You do not need to understand MCP or write code to get started.
| Server | https://mcp.apper.io/v1/connect |
| Transport | Streamable HTTP |
| Authentication | OAuth 2.0 |
How it works
Apper connects to ChatGPT, Claude, or other AI/LLM models through the Model Context Protocol (MCP).
Once connected, your AI assistant can use Apper to create and update apps inside your Apper account. You can keep giving instructions in plain English while Apper handles the app infrastructure behind the scenes.
-
Describe your app — Tell your AI assistant what you want to build.
create_app
Apper creates the first version of your app, using sample data when needed. -
Preview it — Once the app is built, open a working preview and try it yourself.
get_build_status→preview_app -
Make changes — Ask for new pages, features, design changes, or fixes.
Apper updates the app and gives you a new preview. -
Connect a database when needed — If your app needs real users, saved records, or persistent data, you can connect it to a real database.
connect_database -
Keep building — Once connected, you can continue changing your app, database structure, permissions, features, and design through the conversation.
update_databaseand other Apper tools are used as needed.
Switching from sample data to a connected database is a one-time change and cannot be reversed.
Available tools
Your AI assistant automatically selects the right Apper tools based on what you ask.
- Read-only tools can view information but cannot change anything.
- Write tools can create, update, or delete something in your app.
Apps and project files
| Tool | Type | What it does |
|---|---|---|
search_apps | Read-only | Find an existing app or list your apps. |
create_app | Write | Start a new app from your description. |
get_create_app_instructions | Read-only | Provides instructions for creating an Apper app correctly. |
get_edit_app_instructions | Read-only | Provides instructions for editing an existing app. |
get_design_directives | Read-only | Provides product and design guidance for building your app. |
get_project_tree | Read-only | View the files and folders in an existing app. |
read_files | Read-only | Read app files before making changes. |
write_files | Write | Create or update files in your app. Replaces a file's full contents. |
patch_files | Write | Make small edits to part of an existing file, without rewriting the whole thing. |
delete_files | Write | Remove files from your app. |
Build and preview
| Tool | Type | What it does |
|---|---|---|
get_build_status | Read-only | Check whether your latest app changes have finished building. |
preview_app | Read-only | Open a live preview of your app. |
Database
| Tool | Type | What it does |
|---|---|---|
get_backend_schema | Read-only | View your app's current database structure. |
get_backend_schema_filtered | Read-only | View specific parts of your database structure. |
connect_database | Write | Switch your app from sample data to a connected database. This is a one-time change and cannot be reversed. |
update_database | Write | Add, change, or remove database tables, fields, permissions, and access rules. |
get_rls_policy_instructions | Read-only | Provides instructions for setting up database access rules correctly. |
Server-side functions
Server-side functions let your app securely handle tasks such as sending emails, processing payments, or calling external APIs.
| Tool | Type | What it does |
|---|---|---|
create_edge_function | Write | Create new server-side functionality. |
get_edge_function | Read-only | View an existing server-side function. |
update_edge_function | Write | Change an existing server-side function. |
delete_edge_function | Write | Remove a server-side function. |
list_edge_functions | Read-only | List the server-side functions in your app. |
Secrets and configuration
| Tool | Type | What it does |
|---|---|---|
create_secrets | Write | Register a secret such as an API key. You enter the actual value securely in Apper. |
list_secrets | Read-only | See which secrets have been added without revealing their values. |
delete_secret | Write | Remove a secret from your app. |
get_env_keys | Read-only | View your app's public configuration keys. |
set_env_key | Write | Add or change a public configuration value. |
Connector
| Tool | Type | What it does |
|---|---|---|
check_mcp_version | Read-only | Check whether the Apper MCP connector is up to date. |
Data and Security
Your secret values stay private
No need to worry — sharing an API key can feel risky, so here's exactly how we keep yours secure.
Secret values such as API keys are entered directly in Apper — never shared in chat with your AI assistant.
How it works:
- When you want to enter your secret API key, open Apper's Secrets page and add it there — it's safely stored in an encrypted vault, never in a chat window.
- Your AI assistant only ever sees the key's name (like
OPENAI_API_KEY), never the actual value. - The real key is used securely behind the scenes only when your app runs.
For example, you can create a secret called:
OPENAI_API_KEY
Your AI assistant can then build functionality that uses it — without ever seeing the key itself.
Simple rule: Add your keys in Apper's Secrets page, not in the chat.
Database connection is permanent
Connecting an app to a real database is a one-time change.
Once connected, the app cannot be switched back to sample data.
Make sure you are happy with the basic app before approving the database connection.
Support
Questions, issues, or feedback: support@integrately.com
Privacy policy: https://integrately.com/home/privacy