Connect with MCP

Beta
Connect an MCP client to work with your Glide projects.

The Glide MCP server is available on Pro and Enterprise plans.

Connect a Model Context Protocol (MCP) client, like Claude or Cursor, to your Glide organization, and it can work with your projects the same way GlideOS does. The client signs in as you, so it will have the same features available that you do. Access depends on your organization’s plan.

MCP changes where the AI work happens, which affects your credit consumption. When you drive GlideOS from a connected client, you move the agent’s work and reasoning to your own plan with that provider. Any tokens used by the MCP connection are managed directly with the provider. GlideOS receives the result of that finished work. Credits still apply to the work GlideOS runs itself, including Runtime AI in the apps you create, workflows, and integrations.

A connected client works with your projects and organization: the same work GlideOS does when you ask directly. When you connect an MCP client, it should ask you for permissions to perform actions on your behalf in GlideOS.

MCP Permissions

Review permissions carefully in your client provider settings. Unexpected credit usage via MCP is not refundable.

Connect a Client

You need an MCP client that supports remote servers over HTTP. Each connection you set up belongs to one organization. If you leave that organization, the connection stops working for all team members.

To connect, you’ll need Glide’s remote MCP server URL. It’s the same for every organization, and users authenticate when connecting. Copy it to your agent, or pick your client under Open in to get connected.

https://mcp.glideapps.dev/mcp

Most agentic tools will be able to set up the connection to Glide’s MCP if you provide the URL and ask the agent to connect. Below are setup instructions for some common tools if you want to create a custom connection.

Claude

In a Claude Team or Enterprise organization, only an owner can add a custom connector, from Organization settings > Connectors. Everyone else opens Customize > Connectors and clicks Connect on the connector the owner added.

1

In GlideOS, click your organization’s name at the top of the sidebar, then click Settings.

2

Select Agents. The URL is under Give this URL to your agent.

3

Click Copy URL. Always copy the URL rather than typing it.

4

Open Customize in Claude, then click Connectors.

5

Click Add, then click Add custom connector.

6

Paste the URL into the remote MCP server URL field.

7

Click Continue to save the connector.

8

Sign in to Glide when Claude sends you there, and approve the connection. If you belong to more than one organization, choose the one to connect. The list shows only organizations where you’re an admin or editor.

Cursor

1

In GlideOS, click your organization’s name at the top of the sidebar, then click Settings.

2

Select Agents. The URL is under Give this URL to your agent.

3

Click Copy URL.

4

Open Settings in Cursor and add a new MCP server.

5

Paste the URL into the server’s url field. Cursor saves it to .cursor/mcp.json for a single project, or to ~/.cursor/mcp.json for every project.

6

Click Needs login next to the server, then sign in to Glide and approve the connection.

ChatGPT

ChatGPT treats an MCP server as a custom connector, and connectors sit behind developer mode. Turn that on first.

1

In GlideOS, click your organization’s name at the top of the sidebar, then click Settings.

2

Select Agents. The URL is under Give this URL to your agent.

3

Click Copy URL.

4

Open Settings in ChatGPT and click Connectors.

5

Turn on Developer mode under Advanced settings.

6

Click Create on the Connectors tab.

7

Enter a name for the connector.

8

Paste the URL into MCP server URL.

9

Select OAuth as the authentication method.

10

Click Create, then sign in to Glide and approve the connection.

Frequently Asked Questions

Some clients ask you to pick a transport when you add a server. Choose HTTP, which some clients label Streamable HTTP. Skip the local or stdio option, which is for servers that run as a program on your own machine, and skip SSE, an older option some clients still list. Many clients never ask, and instead select it for you.

The organization picker shows only organizations where you’re an admin or editor. If you’re a viewer, or your invite is still pending, ask an organization admin to grant editor access, then connect again.