MCP offers an open contributor path through its Agents and Triggers & Events working groups: Tasks, multi-turn interaction, callbacks, and delivery semantics. Security is also discussed in an interest group. Their scope is protocol interoperability, not a general agent runtime.

The MCP community has distinct collaboration formats: Interest Groups identify problems and requirements; Working Groups produce proposals and implementations.

For ongoing personal agents, two groups are especially relevant:

• Agents WG: Tasks, durable asynchronous execution, lifecycle ambiguities, multi-turn agent interactions, and supervisor/sub-agent patterns. An Agents Extension is being evaluated; it is not an already settled solution. Memory, planning, and general-purpose runtimes are outside this group's scope.
• Triggers & Events WG: proactive callbacks, subscription lifecycle, event delivery and ordering, and task-completion notifications. Its incubation repository is a place to inspect proposed mechanisms and contribute experiments.

The Security IG also covers secrets, process isolation, runtime changes after approval, and auditability.

Start through the official communication guide: join the contributor Discord, find the relevant group, read its agenda, and bring a scoped use case or experiment to a public discussion. Meetings are open to community participants. GitHub Discussions provide the durable record for technical proposals.

Formal WG Member status is earned through sustained participation; it is not needed to start observing or contributing. See the participation rules.