> For the complete documentation index, see [llms.txt](https://membershipcommittee.docs.intersectmbo.org/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://membershipcommittee.docs.intersectmbo.org/about/readme.md).

# Membership and Community Committee (MCC)

## What is the Membership and Community Committee?

The Membership & Community Committee (MCC) is an Intersect-facing Committee focused on reviewing and improving membership experience at Intersect, inclusive of: membership offerings, growing the membership, and encouraging/supporting participation in the Intersect community. MCC ensures that members are actively engaged by creating pathways for people and organizations to join.

MCC connects Intersect to the real world. This includes supporting regional onboarding of contributors, improving member visibility, coordinating community programs and ensuring that Intersect membership translates into activity and impact.

This committee collaborates closely with the Intersect Steering Committee, as both Committees have an Intersect facing focus.

## How to contact us

Discord - [Chat with MCC](https://discord.com/channels/1136727663583698984/1234457365835943999)

Email - <membership-and-community-committee@intersectmbo.org>


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://membershipcommittee.docs.intersectmbo.org/about/readme.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.