lfx-mcp

LFX MCP Server

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

Features

• Explore projects — Search and retrieve details for Linux Foundation projects
• Manage committees — Search, create, update, and delete project committees and their members
• Work with mailing lists — Search project mailing lists and their subscribers
• Track project meetings — Find upcoming meetings, registrants, past participants, and AI-generated summaries
• Query membership — Search project memberships by tier, status, organization, and more; get and manage key contacts
• Analyze data with LFX Lens — Compare and report on project activities and contributions over time
• ... and more!

Connecting to the LFX MCP Server

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

https://mcp.lfx.dev/mcp

You will be prompted to log in with your Linux Foundation account (LFID) the first time you connect. All MCP permissions correspond to LFX platform permissions granted to your LFID.

The following clients are set up to work with the LFX MCP Server. Please file an issue to request additional client support. Running the LFX MCP Server as a local (stdio) MCP server is not supported at this time.

Goose

GUI (one-click install)

Copy-paste into your browser location bar:

goose://extension?url=https%3A%2F%2Fmcp.lfx.dev%2Fmcp&type=streamable_http&id=lfx&name=LFX&description=LFX%20MCP%20Server

Start a new chat and Goose will open a browser window for LFID login.

CLI

1. Run goose configure.
2. Select Add Extension → Remote Extension (Streamable HTTP).
3. Enter LFX as the name.
4. Enter https://mcp.lfx.dev/mcp as the URI.
5. Enter 300 for the timeout.
6. Enter LFX MCP Server as the description.
7. Select No for adding custom headers.

After it acknowledges that your configuration was saved, running goose will open a browser window for LFID login.

OpenCode

OpenCode requires a client ID. The following client ID only works with 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 (LF enterprise)

If you use the Linux Foundation's enterprise Claude.ai organization, the LFX MCP Server is already provisioned as a connector in both Claude Desktop and Claude Code.

Claude Desktop

1. From the sidebar, select Customize → Connectors.
2. Find LFX in the list.
3. Click Connect and sign in with your LFID.

Claude Code

Run /mcp inside Claude Code and select claude.ai LFX → Authenticate. Claude Code will open a browser window for LFID login.

Claude Desktop (personal account)

1. From the sidebar, select Customize → Connectors.
2. Use the + button and select Add Custom Connector.
3. Enter LFX and the URL https://mcp.lfx.dev/mcp.
4. Press Add, then Connect and sign in with your LFID.

Claude Code (personal account)

claude mcp add --transport http lfx https://mcp.lfx.dev/mcp

Run /mcp inside Claude Code and select lfx → Authenticate. Claude Code will open a browser for LFID login.

Visual Studio Code

Run MCP: Open User Configuration to open the mcp.json file to add the LFX MCP server in your user-level config:

{
  "servers": {
    "lfx": {
      "type": "http",
      "url": "https://mcp.lfx.dev/mcp"
    }
  }
}

VS Code will prompt you to trust the server, then open a browser window for Linux Foundation SSO.

Cursor

Cursor requires a client ID. The following client ID only works with 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 is not listed here, you may try using mcp-remote as a local proxy.

The client ID shown here is only for embedding mcp-remote as a proxy and does not support direct MCP client use.

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 re-authenticate, clear cached credentials with:

rm -rf ~/.mcp-auth

MCP Inspector (developer testing)

MCP Inspector requires a client ID. The following client ID only works with MCP Inspector.

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

npx @modelcontextprotocol/inspector --transport http --server-url https://mcp.lfx.dev/mcp

From the MCP Inspector sidebar, find Authentication → OAuth 2.0 Flow → Client ID and enter 4ibLLbnz9kwMEcE3RUCUH51F0RS3Hx3O.

Hitting Connect will open a browser window for LFID login.

Available Tools

Projects

Committees

Mailing Lists

Members

Meetings

Past Meeting Data

Discord

Email

LFX Lens

B2B Organizations

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.