GlideOS now connects to Model Context Protocol (MCP) clients, including Claude and Cursor. Once connected, the client signs into GlideOS as you and works with your projects the same way GlideOS does, with the same access your account already has.
Connecting a client changes where the AI work happens.
When you drive GlideOS from Claude or Cursor, the agent’s reasoning runs on your own plan with that provider, and any tokens used are managed directly with them. Glide credits still apply to the work GlideOS runs itself, including Runtime AI in your apps, workflows, and integrations. But when using the MCP, Glide Credits will not be used to build.
To connect, click your organization’s name in the sidebar, then click MCP Server to get your server URL. Each connection belongs to one organization. If you leave that organization, the connection stops working for the rest of your team too.
Before approving a connection, review the permissions your client is requesting. Unexpected credit usage through MCP isn’t refundable.
Full setup steps for Claude and Cursor are in the docs: Connect with MCP | Glide Docs