MCP Servers

• 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 either 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 SSE or stdio transport support.

☁️ Using a remote/hosted MCP Server (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 SSE 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 (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

1. Install & launch server via mcp-proxy (if needed) – 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

1. Expose your local SSE 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.app.

# Install & authenticate ngrok
brew install --cask ngrok

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

1. Form the Glue-compatible URL

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

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

1. Open the Glue app.

2. Click your profile image → Preferences.

3. Navigate to the Labs tab → 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.

   Reminder the format is either https://<remote-host>/sse or https://<username>:<password>@<random>.ngrok-free.app/sse

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).

1. To navigate to the server rules, click on the ellipsis next to the server name under the MCP Servers tab.

2. Select configure rules from the dropdown menu.

3. Input your individual preferences for how Glue AI should interact with the server. Examples include storing IDs, naming conventions, and templates.

4. Click save.

Most MCP-exposed tools will document their parameters. Look for:

• Required fields (e.g., project_id, repo_name, board_id)

• Defaultable fields (i.e., things you can prefill with a rule)

• Example payloads

Try manually triggering the tool from a thread. If Glue prompts you for a value, that’s a strong hint you can set it ahead of time.

Example: If you’re asked “Which Linear project should this go into?”, that means you could write a rule that injects "project_id": "proj_abc123".