lfx-mcp

LFX MCP Server

A Model Context Protocol (MCP) server that connects AI assistants to the Linux Foundation's LFX platform.

What You Can Do

• Explore projects — Search and retrieve details for any LFX project
• Manage committees — Search, create, update, and delete committees and their members across projects
• Work with mailing lists — Search mailing lists and their subscribers
• Query members — Search memberships by tier, status, organization, and more; get key contacts
• Track meetings — Find upcoming meetings, registrants, past participants, transcripts, and AI-generated summaries

Connecting to the LFX MCP Server

The LFX MCP Server is available as a hosted, production service at:

https://mcp.lfx.dev/mcp

This endpoint uses the Streamable HTTP transport with OAuth 2.0 authentication. You will be prompted to log in with your Linux Foundation account the first time you connect.

Note: Running the LFX MCP Server locally (e.g. in stdio mode) is not a supported end-user configuration. The full tool set requires OAuth authentication flows that are only available through the hosted service.

Linux Foundation SSO does not support Dynamic Client Registration (DCR) or Client ID Metadata Documents (CIMD) at this time. Please file an issue to request additional client support.

OpenCode

Add the following to your ~/.config/opencode/opencode.json:

{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "lfx-mcp-server": {
      "type": "remote",
      "url": "https://mcp.lfx.dev/mcp",
      "enabled": true,
      "oauth": {
        "clientId": "LnBd9qGpwjXNs26aZxeXSkTCs0ac4zgM"
      }
    }
  }
}

See the OpenCode MCP documentation for more details.

Claude

Add the LFX MCP Server in Settings → Integrations → Add Integration:

• URL: https://mcp.lfx.dev/mcp
• Client ID: Ef9tuU5wcJJIXmNGvZyGUkZFfD8CZWar

Cursor

Add the following to your ~/.cursor/mcp.json:

{
  "mcpServers": {
    "lfx": {
      "url": "https://mcp.lfx.dev/mcp",
      "auth": {
        "CLIENT_ID": "HwGWwUy4uvqVQYDsuXb9IVamzcUhdZj5"
      }
    }
  }
}

Additional clients (via mcp-remote)

If your MCP client does not support OAuth 2.0 with Streamable HTTP, you can use mcp-remote as a local proxy. It handles the OAuth flow in your browser and serves a stdio transport to your MCP client.

The port 3334 is required so that the OAuth callback URL matches the registered client. Please refer to your client's documentation for the exact configuration syntax. For example, in Zed (~/.config/zed/settings.json):

{
  "context_servers": {
    "lfx": {
      "command": "npx",
      "args": [
        "mcp-remote",
        "https://mcp.lfx.dev/mcp",
        "3334",
        "--static-oauth-client-info",
        "{\"client_id\":\"tjrXD5ZJORf6rpngMSRqqPmf3W1bnHEV\"}"
      ]
    }
  }
}

A browser window will open for authentication on first use. To clear cached credentials (e.g. to re-authenticate):

rm -rf ~/.mcp-auth

MCP Inspector (developer testing)

MCP Inspector is a browser-based tool for exploring and testing MCP servers. To connect it to the LFX MCP Server:

npx @modelcontextprotocol/inspector

Then in the Inspector UI:

• Transport: Streamable HTTP
• URL: https://mcp.lfx.dev/mcp
• Authentication → OAuth 2.0 Flow → Client ID: 4ibLLbnz9kwMEcE3RUCUH51F0RS3Hx3O

Before hitting Connect, follow the Open Auth Settings button, then select Quick OAuth Flow.

Available Tools

Projects

Committees

Mailing Lists

Members

Meetings

Past Meeting Data

Utility

License

Copyright The Linux Foundation and each contributor to LFX.

This project's source code is licensed under the MIT License. A copy of the license is available in LICENSE.

This project's documentation is licensed under the Creative Commons Attribution 4.0 International License (CC-BY-4.0). A copy of the license is available in LICENSE-docs.