Query our Communities in plain English — a read-only data MCP connector

Introducing a read-only connector for the OpenSSL Communities: point your AI assistant at our Loomio and just ask — about discussions, polls, decisions, and who's participating. No spreadsheets, no API, plain English. It speaks the Model Context Protocol (MCP), so any MCP-capable assistant can use it. It's open to everyone and it can only read — it never posts, votes, or changes anything.

Connect it in under a minute

You'll need an assistant that supports MCP connectors.

1. In your assistant, add a new remote MCP server / custom connector (usually under Settings → Connectors)

2. Name it anything (e.g. OpenSSL Communities)

3. URL: https://mcp.openssl-communities.org/mcp

4. Connect — that's it. No API key or password to enter.

Ask this → get this back

"What groups can you see in the OpenSSL Communities?"

I can see 10 groups in the OpenSSL Communities. There's a top-level "Communities" hub, and the rest are sub-groups nested under it:
Communities (hub, 10 members) — the parent group, with these sub-groups:

Academics — 43 members
Distributions — 44 members
Committers — 34 members
Individuals — 156 members
Small Businesses — 65 members
Large Businesses — 144 members
Corporation Business Advisory Committee (BAC) — 11 members
Corporation Technical Advisory Committee (TAC) — 12 members

"How active has <member> been across the committees this year?"

Across the two committees this year, <member>'s logged 7 actions total (the scan covered 51 discussions and 218 events, so this is complete for 2026):

4 comments — the bulk of your participation
1 vote (a stance you cast)
1 poll closed + outcome recorded — on a single TAC thread you wrapped up a poll and logged the decision, so you were acting as the administrator there

The split by committee is fairly even: TAC (4 actions) edges out the BAC (3).
Timing-wise it clusters into three bursts: three actions in January (Jan 5–26), a single comment in April (the 14th, around the advisory-call period), and three actions on May 28 — all on one TAC discussion, where <member> voted, closed the poll, and recorded the outcome in quick succession.

"Who's most engaged in Committers this quarter?"

Committers is the most active community this quarter, and its Q2 activity was concentrated almost entirely in one thread — "Topics for Brno F2F" (32 contributions). Tallying who drove that conversation, here's the most engaged member.

"How did the last big proposal in the Technical Advisory Committee go?"

This pulls up cleanly. The last substantive proposal in the Corporation TAC was the FIPS_mode() macro reinstatement — and it just closed yesterday. Let me lay it out as a card.

The last big one was the FIPS_mode() macro reinstatement, and it closed cleanly. After the TAC supported escalating it (13 Apr poll, 2–0) and the Distributions community poll came back positive, Dmitry brought it to the Board as a consent vote. It passed with unanimous director consent — 2 Consent, 0 Objection, no abstentions — and the Board accepted it, authorising the item onto the Corporation roadmap with R&D and the TAC to finalise the exact macro semantics (working ref: openssl#30339).

…and plenty more: open polls and where they stand, who took part in a thread, recent activity in a group, or comparing two groups side by side.

What it can and can't do

• Read-only. It can look things up but cannot post, comment, vote, or change membership — ever.

• Sees the public Communities groups above — it reads what's already visible there.

• Member names and participation, yes; email addresses, no.

• Shared, rate-limited access — scope a question to a group to keep it fast; you'll be told when a result is partial.

Tell us how it goes

Reply here with what worked, what was wrong, or questions you wish it answered better.