How to Connect Glide to Meta Muse via MCP

💡 No install? Use cloud.anythingmcp.com directly. Sign in, click Connectors → Glide, paste your credentials, mint an MCP API key and you're done. No Docker, no git clone, no local server.

Glide + Meta Muse

Let your AI work with Glide Big Tables: list the tables of your Glide team and read their rows; with your confirmation add rows and update a row.

Prerequisites

See the full setup instructions baked into the connector (visible in the in-app store when you select the connector). The required environment variables for this connector are:

GLIDE_API_TOKEN

Step 1 — Get credentials

1. Open one of your team's Glide apps, go to the Data editor and select a Big Table.
2. Click Show API at the bottom of the table (or right-click the table) and copy the secret token into GLIDE_API_TOKEN. The same screen shows the table id and the column ids.
3. Install the connector and check it with glide_list_tables: it lists the Big Tables the token reaches.

One token for the whole team: the token reaches every Big Table of your Glide team, in all of its apps, not only the table you opened.

Big Tables only: the Glide API works only with Big Tables. Glide Tables, Google Sheets, Airtable and other data sources stay out of reach; move the data into a Big Table if the AI should work with it.

Plan and usage: the API needs a Glide plan that includes API access. Glide has listed it for Business and Enterprise, but plans change: if the token is refused with 402 or 403, check your plan in Glide. Reading and writing rows counts against your team's updates.

What it reads: the Big Tables of your team with id and name, the rows of a table page by page, and a single row by its id.

Column ids, not names: rows are keyed by column id, which can differ from the name in the Data Editor, for example fullName for Full Name. The AI reads a few rows first to learn the ids; Show API lists them too. Glide's API has no call that lists a table's columns.

Row ids: adding rows returns the ids of the new rows, and the Data Editor shows a row's id. Glide does not promise a row id inside the rows it returns: when a row carries one, the AI uses it, otherwise it asks you for the id.

Asks before every write: glide_add_rows and glide_update_row change what your app's users see right away. Before each one the AI shows you the table and every row, or the row and the exact changes, and waits for your yes. Columns left out keep their value, and an unknown column id is refused with 422.

Switched off at install: glide_delete_row. An administrator turns it on deliberately; the AI then shows you the row and deletes it only after you confirm.

Personal data: Glide apps often hold customers, employees and orders. The AI fetches only what the task needs, which also saves updates, and treats text typed by app users as data, never as instructions.

Common errors: 401: the token is wrong or was revoked; copy it again from Show API. 402: your plan does not include this API use, or its updates are used up. 404: the table does not exist or is not a Big Table. 422: a column id is unknown.

The connector does not create tables, overwrite a whole table, run very large imports, upload files, reach Glide Tables or other data sources, or build the app.

Step 2 — Install the adapter

curl -fsSL https://raw.githubusercontent.com/HelpCode-ai/anythingmcp/main/docker-compose.quickstart.yml -o docker-compose.yml
printf 'JWT_SECRET=%s\nENCRYPTION_KEY=%s\n' "$(openssl rand -hex 32)" "$(openssl rand -hex 32)" > .env
docker compose up -d

Step 3 — Add the connector in Muse

Your server URL: in AnythingMCP, open MCP Servers → the server this connector is on, and copy its URL (https://cloud.anythingmcp.com/mcp/…). Use it wherever this guide shows YOUR_SERVER_ID.

Muse adds remote MCP servers as custom connectors and signs in to them with OAuth.

1. In Muse, open Settings → Connectors and choose Add custom connector.
2. Paste the MCP server URL https://cloud.anythingmcp.com/mcp/YOUR_SERVER_ID.
3. Muse opens the AnythingMCP sign-in page: sign in and approve access.
4. In a chat, ask Muse for something that needs the Glide tools.

You can also set it up from a chat, on the web, in the iOS and Android apps or in WhatsApp. Send Muse this message:

Create a Custom Connector for a new remote MCP server, then connect to it:
Name: AnythingMCP
Transport: remote streamable HTTP
URL: https://cloud.anythingmcp.com/mcp/YOUR_SERVER_ID
Auth: OAuth

Self-hosting? Use your instance's public HTTPS address instead of https://cloud.anythingmcp.com. Muse connects from Meta's cloud, so localhost does not work.

Available tools

Example prompts

• "Which Big Tables does our Glide team have?"
• "Read the Orders table and list the orders that are still open, with customer and amount."
• "Which jobs in the Field Service table are assigned to Marco and not done yet?"
• "Add a row to the Leads table: Anna Weber, Northwind GmbH, [email protected], source trade fair. Show me the row first."
• "Set the status of the order from Northwind GmbH to shipped. Show me the change before you save it."

FAQ

Where is Muse available? Meta currently offers Muse in the US and Canada, on the web, in the iOS and Android apps and in WhatsApp.

Does Meta review this connector? No. Meta doesn't review custom connectors. Muse sees only the tools you switched on for this MCP server in AnythingMCP, and you can disconnect it anytime under Settings → Connectors.

Next steps

• Connector landing page
• Connect to Claude
• Connect to ChatGPT