← All Docs

Integrations

MCP Server Connections

MCP (Model Context Protocol) connections let your Webase apps interact with external services and data sources. By connecting to MCP servers, your AI-generated apps can access tools, databases, and APIs beyond what is built into Webase.

What Are MCP Servers?

MCP servers are standardized services that expose tools and data sources to AI applications. Think of them as plugins that extend what your app can do. An MCP server might provide:

  • External data access — Connect to databases, APIs, or data feeds that your app needs to display or process.
  • Tool capabilities — Add functionality like sending emails, processing payments, generating PDFs, or running calculations.
  • Service integrations — Bridge your app with popular services like Slack, Google Sheets, Notion, or custom internal systems.

No coding required. You do not need to write any integration code. Once an MCP server is connected, the AI knows about its tools and can use them when building or updating your app based on your chat instructions.

Browsing the Catalog

Webase provides a catalog of available MCP servers that you can browse and connect to. The catalog is organized by category and includes descriptions of what each server provides, the tools it exposes, and any credentials it requires.

To browse the catalog, open the MCP Connections section in your Application Editor. You will see available servers listed with their names, descriptions, and connection status.

Connecting to an MCP Server

1

Select a Server

Click on an MCP server in the catalog to see its full details, including available tools, required configuration, and usage examples.

2

Enter Credentials

If the MCP server requires authentication, enter your credentials in the secure form. This might be an API key, an OAuth token, or other service-specific credentials. Not all servers require credentials.

3

Activate the Connection

Click Connect to enable the server. Webase verifies the connection is working, and the MCP server's tools become available to your app immediately.

Security: Credentials for MCP connections are stored encrypted and are never included in your app's generated source files. They are only used server-side when your app makes requests to the connected service.

Managing Your Connections

Once connected, you can manage your MCP server connections from the same panel:

  • View active connections — See all MCP servers currently connected to your app and their status.
  • Update credentials — Change API keys or tokens when they rotate or expire.
  • Disable connections — Temporarily disable a connection without deleting the configuration. Re-enable it anytime.
  • Remove connections — Permanently disconnect an MCP server and delete its stored credentials.

Using MCP Tools in Your App

Once an MCP server is connected, you can ask the AI to use its tools through chat. The AI knows which servers are connected and what tools they provide. Here are some examples:

  • "Send a confirmation email when a new order is created." — Uses an email MCP server.
  • "Pull data from the Google Sheets connection and display it in a dashboard." — Uses a Google Sheets MCP server.
  • "Add a button that generates a PDF report from the current data." — Uses a document generation MCP server.

The AI integrates MCP tools into your app's logic automatically based on your instructions. You do not need to know the technical details of how the tools work.

Best Practices

  • Only connect MCP servers that your app actually needs to minimize complexity.
  • Keep credentials up to date — expired keys will cause connection failures.
  • Test MCP-powered features in the preview panel before sharing your app.
  • If a connection is no longer needed, remove it to keep your app's configuration clean.
  • Review the tools an MCP server provides before connecting to ensure it matches your needs.