• Remote / hosted servers – if the app has an official remote MCP server, we recommend using that over a community server. Glue supports the SSE (Server-Sent Events) transport and streamable HTTP.
• Community servers – look for one that supports Streamable HTTP, SSE or stdio transport. You can use a proxy to translate stdio to SSE—see below.
• Helpful directories:
  • MCP Servers Repository - Complete collection of reference implementations and community servers
  • Awesome MCP Servers - Curated list of MCP servers

The setup steps differ based on the type of MCP server you're using — remote or locally hosted community servers with either Streamable HTTP, SSE or stdio transport support.

☁️ Using a remote/hosted MCP Server (Streamable HTTP or SSE)

These are hosted by the third party application itself. Setup is minimal.

1. Follow the provider's setup instructions.
2. Copy the server’s URL (e.g. https://mcp.linear.app/sse).
3. Skip to Step 3 · Connect the MCP Server to Glue.

🖥️ Using a local community MCP Server (Streamable HTTP, SSE or stdio)

Each community server will have an open source instructions list that needs to be followed and will vary based on the app. These are the general steps that will be required.

1. Install the MCP Server to your local machine

• Follow app-specific instructions (usually in their GitHub README).
• Prerequisites may include tools like Node.js, Homebrew, etc.

# Example: Linear MCP server delivered via npx
# replace with the command shown in the server’s README
npx @ibraheem4/linear-mcp

2. Install & launch server via mcp-proxy (stdio only) – converts stdio ⇄ SSE

brew install uv               # light Python runtime used by mcp-proxy
uv tool install git+https://github.com/sparfenyuk/mcp-proxy
# --pass-environment  → passes your shell’s env vars (API keys, etc.) to the server
# --sse-port 9000     → local port on which mcp-proxy will expose an SSE endpoint
# everything after that is the *command* to start the MCP server
mcp-proxy --pass-environment --sse-port=9000 \
  npx @ibraheem4/linear-mcp

3. Expose your local MCP endpoint to Glue (Glue cannot reach localhost)

• Install a proxy like ngrok if you have not already
• ngrok shows a forwarding URL like https://<random>.ngrok-free.app4

# Install & authenticate ngrok
brew install --cask ngrok

# Forward the SSE port (9000) with basic auth
ngrok http 9000 --basic-auth="YOURUSER:YOURPASS"

4. Form the Glue-compatible URL

• This URL will allow Glue to route requests securely to your MCP server.

example for SSE

<https://YOURUSER>:YOURPASS@<random>.ngrok-free.app/sse

1. Open the Glue app.
2. Click your profile image → click Preferences.
3. Find the Labs section → click MCP Servers.
4. Click the Add MCP server button.
5. Name your MCP server.
6. Paste the MCP server URL into the Server URL field.
   1. Reminder: If connecting to a local MCP server, use the ngrok URL
7. Click Add server or follow any additional instructions to sign in and authorize the third party app, as prompted.

✅ Glue AI is now connected to the app via its MCP server. You will be taken to a details screen where you can configure custom rules for the server (see step 4).

Configure Rules for your MCP Server for the best experience

Glue AI needs to know certain identifiers about the tool you are calling via MCP to be able to take the action appropriately, like your workspace or team ID. To make the interactions seamless, store this information in the Server's Rules so Glue AI always has access without having to request it each time.

1. To navigate back to the server rules later, go the Apps section of your inbox, search for the specific app and click on it.
2. Click on the MCP button (it will show a gear icon if it's already been installed).
3. You can set both workspace wide rules under "Shared AI rules" as well as personal ones just for you. These inform how Glue AI should interact with the server. Examples include storing IDs, naming conventions, and templates.
4. Click save.

Here is an example of the rules we have set on our workspace's Linear MCP Server.

- Web (WEB) team ID: ABC-123
- API (API) team ID: DEF-456
- Glue (GLU) team ID: GHI-789

When creating issues:
- Infer the teamId from context:
    - For issues relating to the API, glue-api, or Glue AI, use the API Team ID.
    - For issues relating to the native app, client, or glue-web, use the Web Team ID.
    - If you do not know, always default to the Glue (GLUE) Team ID.
- Add detailed description in the `description` param, using Markdown where helpful.
- Issue priority should be 3 (Normal) unless otherwise specified.

💬 What Can You Do With Glue + MCP?

Once connected, Glue AI can

• Make real-time queries to your connected app
• Trigger actions via natural language (e.g., “Create a new issue in Linear”)
• Use the rules you've set for the server to customize how the server is called

⚠️ Support & Limitations