Maia MCP Client

Last modified: February 25, 2026

Introduction

This feature is released as part of Make Make capabilities in Studio Pro 11.8.

To use Maia MCP Client, an internet connection and signing in to Studio Pro are required.

Maia MCP Client, available from Studio Pro 11.8, helps you connect Maia to external Model Context Protocol (MCP) servers. Once connected, Maia can call tools provided by these servers during chat — for example, querying an external API, looking up design assets, or interacting with third-party services. You can find available MCP servers on the MCP servers directory.

For information on the current limitations, see the Limitations section below.

Using MCP Client

To open the MCP Client panel, click the Configure MCP Connections ( ) icon under the Maia Chat tab.

Adding an MCP Server

To add a server, fill in the following fields and click Add:

Server Name — A display name. Must be unique among your configured servers.
URL — The server endpoint. Must use https:// or http://.
Connection type — HTTP (Streamable) for most servers, or SSE (Legacy) for older servers that use Server-Sent Events instead of Streamable HTTP.
Authentication — See the Authentication section below.

Authentication

Choose how Studio Pro authenticates with the MCP server:

No Auth — select this for servers that do not require credentials.
Bearer Token — paste an API token or personal access token. The token is stored securely and is not exposed after entry.
OAuth 2.1 — a browser window opens so you can authorize Studio Pro with the server's provider. Two optional fields appear:
- Client ID — required if the server does not support automatic client registration.
- Client Secret — required by some providers (for example, GitHub).

Most major providers — including GitHub and Figma — do not support automatic client registration. For these, you must first create an OAuth application in the provider's developer portal and then enter the Client ID (and Client Secret if required).

Example: Connecting to GitHub Copilot MCP

Go to GitHub Developer Settings and click New OAuth App.
Fill in the following information:
- Application name — for example, Mendix Studio Pro
- Homepage URL — for example, https://mendix.com
- Authorization callback URL — http://localhost:{port}/mcp/oauth/callback (see the Callback URL section below)
Click Register application, then copy the Client ID.
Click Generate a new client secret and copy it — GitHub shows it only once.
In Studio Pro, add a server with the following details:
- URL — https://api.githubcopilot.com/mcp/
- Authentication — OAuth 2.1
- Client ID and Client Secret — from the steps above
Click Add, authorize in the browser, and the connection completes.

For Figma MCP, the simplest option is to generate a personal access token in Figma and use Bearer Token authentication. If you need OAuth, register an app at Figma Developers, add the callback URL, and request the mcp:connect scope.

Callback URL

The OAuth callback URL format is http://localhost:{port}/mcp/oauth/callback. The port is assigned by Studio Pro's built-in web server. You can find the actual port within the callback URL that Studio Pro generates when you add the server.

If your OAuth app requires a fixed callback URL, you can start Studio Pro with the --web-server-port=45678 command-line flag to use a specific port.

Managing Connections

Each server appears as a card in the MCP Client panel:

Enable or disable a server using the checkbox. Disabling a server disconnects it and removes its tools from Maia.
Expand the card to see its tools.
Remove a server from the expanded view.

Connection Status

Color	Meaning
Green	Connected, tools available.
Orange	Connecting, authenticating, or disconnecting.
Blue	Loading tools from the server.
Red	Error. Check the error message for details.
Grey	Disconnected or disabled.

If a connection drops, Studio Pro reconnects automatically. During reconnection, the status shows the retry progress (for example, Retrying (2/5)...). If all retries fail, disable and re-enable the server to try again.

Managing Tools

After connecting, the server's tools appear in the expanded card. Each tool shows a name and description from the server.

Tools from a new server are disabled by default. Select a tool's checkbox to enable it. Use the select all checkbox to enable or disable all tools at once. Only enabled tools are available to Maia.

How Maia Uses MCP Tools

During chat, Maia considers all enabled MCP tools alongside its built-in capabilities. When Maia calls a tool:

The chat shows Executing {tool} from {server}... with a spinner.
The tool runs on the MCP server and returns a result.
Maia uses the result to formulate its answer.

You see the answer from Maia, not the raw tool output.

Troubleshooting

Problem	Solution
"This server requires manual OAuth client registration"	Register an OAuth app with the provider and enter the Client ID. See the GitHub example given above.
"Token exchange failed" or "incorrect_client_credentials"	Verify your Client ID and Client Secret. Check that the callback URL matches.
Authentication stuck in "Authenticating..."	Check that no firewall blocks localhost. Remove the server and add it again to restart the flow.
Connection fails immediately	Verify the URL. Try switching between HTTP (Streamable) and SSE (Legacy).

Limitations

Maia MCP Client has the following limitations:

Only MCP tools are supported. Other MCP capabilities, such as resources and prompts, are not available.
Only remote servers (HTTP or SSE) are supported. Local stdio servers are not supported.
Tools from new servers are disabled by default.
OAuth requires localhost access for the callback URL.
Server configurations are stored per project and are not shared across projects.