CommunitycliQ Agent (Preview)

CommunitycliQ Agent lets employees whose organization uses CommunitycliQ manage their workplace communities from Microsoft Copilot. Acting as the signed-in user, they can discover and join Employee Resource Groups (ERGs/BRGs) and affinity groups, browse community leaders and chapters, keep up with events, complete CommunityLab worksheets, and track their participation, achievements, and rewards. Requires a CommunitycliQ account; users only see what their permissions allow.

This connector is available in the following products and regions:

CommunitycliQ MCP Server

A remote Model Context Protocol (MCP) server that connects AI assistants — such as Claude.ai, Claude Desktop, and Microsoft Copilot/Teams — to the CommunitycliQ enterprise community platform.

Overview

CommunitycliQ is an enterprise community and Employee Resource Group (ERG) platform. The CommunitycliQ MCP server lets employees interact with their communities through natural language in an AI assistant: discover ERGs, browse community and home feeds, find and RSVP to events, read shared resources, and manage their own memberships.

• What it does: Exposes CommunitycliQ communities, feeds, events, resources, and the user's own profile/activity to an AI assistant as a set of MCP tools.
• Who it's for: Employees and community participants who already use CommunitycliQ and want to reach it from the AI assistant they work in every day.
• Value in one line: Bring your ERGs, events, and community feeds into your AI assistant — every action runs as you, scoped to your own permissions.

The server is read-mostly: most tools retrieve information, and the handful of write tools perform only reversible actions on the signed-in user's own account (joining/leaving a community, reacting to a post, RSVP'ing to an event). There are no administrative or destructive operations.

Data model

A few CommunitycliQ concepts appear throughout the tools:

• Networks / Communities — A "community" (also called a network) is an ERG or interest group. Each is identified by a UUID. Communities form a hierarchy: top-level communities can have child chapters (for example, regional or site-specific chapters of a global ERG).
• Posts — Entries on a community feed or on the user's aggregated home feed. Posts carry reactions of types LIKE, LOVE, CELEBRATE, SUPPORT, LAUGH, and INTEREST.
• Events — Community events with hosts, descriptions, time zones, and RSVP/registration (including waitlists when an event is full). Events can be viewed per community, across all of a user's communities, or as a calendar feed over a date range.
• Memberships — A user's membership in a community. Users can join and leave communities themselves.
• Resources — Documents and links shared in a community, organized into folders and subfolders.

Tools

All tools run as the authenticated user. Read tools are marked (read); write tools are marked (WRITE) and are described below. Every write tool is reversible and self-scoped — it only affects the signed-in user's own account.

Profile & permissions

• whoami (read) — Get the authenticated user's identity (personId, legacyUserId, superUser). Call this first for any "me / my / I" question.
• get_my_profile (read) — Get the user's profile: name, display name, pronouns, biography, email, profile picture.
• get_my_user_record (read) — Get the user's full record (profile plus created/last-modified dates, employee ID, notification email).
• get_my_platform_permissions (read) — List the user's platform-wide permissions (e.g. MANAGE_USERS, MANAGE_COMMUNITIES).
• get_my_network_permissions (read) — List the user's permissions within a community, or aggregated across all communities.
• get_my_notification_settings (read) — Get the user's notification settings / preferences.
• get_my_m365_integration (read) — Get the user's Microsoft 365 (Outlook) integration status.

Communities

• list_top_level_communities (read) — List the top-level communities (ERGs) on the platform.
• get_network_hierarchy (read) — Get the full community hierarchy (top-levels plus chapters).
• get_community (read) — Get core details for a specific community.
• get_community_branding (read) — Get a community's branding (logo, banner, theme colors).
• list_community_leaders (read) — List a community's public leaders.
• list_community_sponsors (read) — List a community's executive/business sponsors.
• get_community_chapter_information (read) — Get chapter info for a community (parent or children).
• join_community (WRITE) — Join the user to a community. Reversible via leave_community.
• leave_community (WRITE) — Remove the user from a community. Idempotent (succeeds even if not a member); reversible via join_community.

Feed & posts

• list_home_feed_posts (read) — List posts on the user's home feed (aggregated across their communities).
• list_community_feed_posts (read) — List posts within a specific community's feed.
• get_post_reaction_summary (read) — Get reaction counts for a post, by reaction type.
• get_post_reactions (read) — List the users who reacted to a post, with their reaction type.
• react_to_post (WRITE) — React to a post as the user. Reversible by changing or clearing the reaction.

Events

• list_my_events (read) — List upcoming events across all communities the user belongs to (searchable, paginated).
• list_upcoming_events (read) — Compact list of upcoming events across the user's communities.
• list_community_events (read) — List a community's events in the most detailed view (host, description, time zone, RSVP info).
• list_community_upcoming_events (read) — List the next few upcoming events for a community (compact widget).
• get_community_calendar (read) — Get a community's events as a lightweight calendar feed for a date range.
• register_for_event (WRITE) — RSVP the user to an event. Idempotent; joins the waitlist if the event is full. Reversible via unregister_from_event.
• unregister_from_event (WRITE) — Cancel the user's RSVP. Idempotent (succeeds even if not registered); reversible via register_for_event.

Activity

• list_my_activities (read) — List the user's recent activities / notifications.
• get_my_unread_activity_count (read) — Get the count of the user's unread activities/notifications.
• list_my_leaderships (read) — List the communities where the user is a leader (empty list if none).

Resources

• list_community_resources (read) — List the resources (documents and links) shared in a community.
• list_folder_resources (read) — List the resources directly inside a resource folder.
• list_folder_subfolders (read) — List the subfolders inside a resource folder.

Reports & engagement

• get_my_stats (read) — The user's lifetime usage stats (logins, posts, comments, events registered/attended, recordings viewed).
• get_my_events_participation (read) — The events the user has participated in (attended / viewed recording).
• get_my_engagement_report (read) — Per-community engagement over a monthly timeline (event registrations, invested hours, points earned); optional date-range filter.

CommunityLab (requires the CommunityLab module)

• list_communitylab_resources (read) — The CommunityLab learning resources (categories → sessions, videos, worksheets, progress) available to the user.
• get_communitylab_session (read) — A single CommunityLab session's detail, including its video URL.
• get_worksheet_fields (read) — A worksheet's field/question definitions (field types + options; the question text itself is UI-only and not returned by the API).
• get_my_worksheet_answers (read) — The user's currently-saved answers for a worksheet.
• save_worksheet_answers_draft (WRITE) — Save the user's own worksheet answers as a draft ("Save and Review Later"). Reversible; accepts partial answers.
• submit_worksheet_answers (WRITE) — Finalize/submit the user's own worksheet answers ("Save"). Validates that all fields are filled; reversible by re-saving.

Achievements & rewards (requires the Gamification module)

• get_my_achievements (read) — The achievements (badges) the user has earned.
• list_rewards (read) — The platform's rewards catalog (paginated).

Tool count: 45 tools — 38 read, 7 write. The 7 write tools (join_community, leave_community, react_to_post, register_for_event, unregister_from_event, save_worksheet_answers_draft, submit_worksheet_answers) are all reversible and act only on the signed-in user's own account (memberships, reactions, RSVPs, and the user's own worksheet answers).

Setup / connection

The server is reached through a single shared URL. When you connect for the first time, you are taken to a /login site-picker where you choose your CommunitycliQ site and sign in — either via your organization's SSO or with your username and password. After sign-in, the assistant connects as you, and every tool call runs with your identity and permissions.

Claude.ai / Claude Desktop

1. Open Settings → Connectors (or Add custom connector).
2. Add the CommunitycliQ MCP server URL.
3. When prompted, complete sign-in: pick your site at the /login page, then authenticate with SSO or username/password.
4. The CommunitycliQ tools become available in your conversations.

Microsoft Copilot / Copilot Studio / Teams

1. Add the CommunitycliQ connector using the same shared server URL.
2. Complete the sign-in flow: pick your site at the /login page, then authenticate with SSO or username/password.
3. The connector is then available to Copilot and within Teams.

Platform-specific OAuth registration details (client IDs, redirect URIs, etc.) are configured during connector setup and are documented separately; the same single URL and site-picker flow applies to every platform.

Example prompts

Once connected, try:

• "Who am I in CommunityCliQ?"
• "What communities can I join?"
• "What events are coming up in my communities this week?"
• "Show me the latest posts in the Women's Network."
• "Join me to the Pride community." (a reversible, self-scoped action)

Authentication & security

• Per-user OAuth 2.1. The server is its own OAuth 2.1 authorization server. Authentication uses the PKCE (Proof Key for Code Exchange) flow.
• Sign-in options. Users authenticate via their organization's SSO or with a username and password, after selecting their site at the /login page.
• Identity isolation. Identity is strictly per-user. Each connection is bound to one signed-in user, and every tool call executes as that user — there is no shared service account and no cross-user access.
• Permission scoping. Tools operate within the user's existing CommunitycliQ permissions. A user can only see and do through the MCP server what they could do in CommunitycliQ directly.
• Data minimization. No data is collected beyond what each tool needs to fulfill the request. Write tools touch only the user's own memberships, reactions, and event registrations.

Known limitations

• Participant-level surface only (in this connector). The certified connector exposes participant-facing capabilities — there are no administrative tools (no user management, community management, content moderation, or bulk operations). The server can optionally expose community-leader tools (event authoring, post/feed moderation), but they are disabled by default, gated by the user's CommunitycliQ permissions, and are not part of this connector pending separate review.
• Read-mostly. The large majority of tools are read-only. The only writes are the seven reversible, self-scoped actions listed above (memberships, reactions, RSVPs, and the user's own CommunityLab worksheet answers); there are no destructive operations in the participant surface.
• Site must be selected at connect time. Because the URL is shared across sites, you must pick your CommunitycliQ site at sign-in. To switch sites you reconnect and choose a different site.
• Reaction types are fixed. Post reactions are limited to LIKE, LOVE, CELEBRATE, SUPPORT, LAUGH, and INTEREST.

Support

Contact: support@communitycliq.com. If a tool doesn't behave as documented, include the prompt and the tool name so we can reproduce it.

Actions

Manage CommunitycliQ communities events and CommunityLab