"A platform for team communication and collaboration" matching MCP tools:

• connect_domainA

  LayeroA

  Connect a custom domain to a site. IMPORTANT: between this call and a working domain stands A PERSON. You get DNS records — show them to the user and explain they go in at their domain registrar. Do not wait for readiness: DNS propagates in minutes to an hour, the platform re-checks on its own, and you check later via `check_domain`. Spinning here burns time and context for nothing. The address can be passed as-is: the platform reduces `https://shop.example.com/page` to `shop.example.com` itself.

  ConnectorOAuth

• connect_domainA

  LayeroA

  Connect a custom domain to a site. IMPORTANT: between this call and a working domain stands A PERSON. You get DNS records — show them to the user and explain they go in at their domain registrar. Do not wait for readiness: DNS propagates in minutes to an hour, the platform re-checks on its own, and you check later via `check_domain`. Spinning here burns time and context for nothing. The address can be passed as-is: the platform reduces `https://shop.example.com/page` to `shop.example.com` itself.

  ConnectorAPI key

• create_actionA

  noticedA

  Create a follow-up tied to a person — a to-do for the relationship (e.g. 'send the deck', 'intro to Ana'). In Team context, pass team_id and assigned_to to create it for any teammate against a Team-visible relationship. RECOMMENDED: include both assigned_to and remind_at whenever ownership and timing are known; neither is required. @mention a name in `content` to link someone in the relationship owner's network. Read open ones via get_person (relationship.actions); close them with complete_action or edit them with update_action.

  ConnectorNo auth

• upcoming_scheduleA

  Cito APIA

  Upcoming matches/events for one game, with game-specific filters. When to use: - "What's on this week?" - Calendar UI; team next matches Prefer over: live_matches for not-yet-started fixtures. Do not use when: only in-progress matches needed → live_matches. Filter support (unsupported params are ignored with meta.warnings — do not assume filtering worked): - lol: hours, team (slug), league (slug) - cs2: team, from, to (ISO); hours not applied upstream - cod: team, tournamentId - dota2: limit/cursor primarily; team may be client-filtered where data allows - ufc: hours / from / to applied client-side after bout expansion (API has no hours); event shells labeled by event name; bouts use fighters[] corners Parallel-safe: yes. Upstream cost: 1–2. Example: { "game": "lol", "hours": 72, "team": "t1", "limit": 20 }

  ConnectorOAuth

• team_profileA

  Cito APIA

  Team/org card: identity, roster, recent matches, and form/trends/radar when available. When to use: - Team page / "who is on this roster?" - Builder team screen sample Prefer over: separate roster + matches + detail via call_api. Do not use when: UFC fighters → player_profile; unknown name → resolve_entity first. Dota may return partial roster (API gap). Prefer slug for lol/cod; teamId for cs2. Parallel-safe: yes. Upstream cost: 2–4. Example: { "game": "lol", "slug": "t1", "recentLimit": 10 }

  ConnectorOAuth

• containers-permissionsA

  hjarniA

  Change access only for existing members of the same Hjarni team; this does not invite anyone or publish a folder. Set or clear a team member's role on a team container. Roles cascade to descendants unless a child has its own role. Caller must have admin role on the target container. Required: container_id (integer, must be a team container), user_id (integer, must be a member of the same team), role ('viewer' | 'editor' | 'admin' | 'inherit'). Use 'inherit' to delete an explicit role and fall back to the role inherited from an ancestor (or from team membership). Team owners are always admin and cannot be downgraded. Returns the user's resulting effective_role on that container.

  Connector

  Destructive

  OAuth

• get_directory_statisticsA

  Game Dev Outsourcing DirectoryA

  Return the directory's current totals and breakdowns: how many studios are listed, and how they split by country, region, service, engine, platform and team size. Use for any "how many studios..." or "which country has the most..." question, and quote these figures rather than counting search results yourself — they are recomputed from the live database and the counts move.

  ConnectorNo auth

• steam_batchA

  SteamGPTA

  Use when the user gives several Steam ids - a match roster, a team, a list of suspects - and wants profiles, FACEIT or ban status for all of them: up to 100 in ONE call, always instead of per-player calls. ids are STRINGS in any computable SteamID format (steamid64, STEAM_1:0:x, STEAM_0:0:x, [U:1:x], hex, steam:hex, a 32-bit account id, a /profiles/ link); never JSON numbers (a 17-digit number loses precision and points at another account); vanity names are not accepted - resolve them with steam_identity first. Players unknown to the platform come back in not_found - fetch those with steam_profile. include adds FACEIT (one query for the batch) and Steam bans (one upstream call) - the cheapest way to review a full roster. Do not use for one player (steam_summary).

  ConnectorNo auth

• team_open_rolesA

  ClusterHackA

  List the positions teams are looking to fill ("we need a designer"). Visibility is limited to what the signed-in account can already see: their own team's open roles, or — if they organise the event — every team's. It is not a public cross-team browse for a stranger looking for any team: that is `team_seeking_members`, which reads the find-a-team page's own list (pair it with `event_free_agents` and `team_matchmaking_teams`). Filter with `team_id` for one team, or `event_slug` to see everything the caller can see at that event. `team_id` is answered exactly. `event_slug` (and the unfiltered form) is not: the underlying endpoint narrows by one team at a time and has no event filter, so a very large event can return a `note` saying rows were left unscanned. Ask per team when that matters.

  ConnectorNo auth

• delete_creator_flow_projectA

  Cannon StudioA

  Preview deletion by default. Only the owner can permanently delete the project and its story/collaboration records. Keep dry_run=true until the user approves the stated impact; then set dry_run=false, confirmed=true, and expected_title from the preview. Preserves world/library assets.

  Connector

  Destructive

  No auth

• list_contactsA

  IgnixA

  List and filter the CRM contacts (people who have written to or interacted with the connected accounts), each with `id`, `name`, `email`, `tags`, `subscribed` and `platform`, plus `count` with the total that matched before the limit. Use it to find a person or a segment; for one person's channels, custom fields and notes use get_contact, and for their messages list_conversations. Returns 40 by default and at most 200: if `count` is higher, narrow with tag, search, platform or accountId. The `id` is what get_contact, update_contact, set_contact_field and enroll_in_sequence take.

  ConnectorOAuth

• membersA

  FlaskA

  List the people on the team: user_id, name, role (admin or member), avatar_url and a ready-made mention link; the result's team field names the team. Email addresses are never returned. Use it to mention someone in feedback_post / feedback_update content: [@Name](https://flask.do/members?user=USER_ID) notifies that person. query keeps names containing it; no match gives an empty list. It lists the whole team, not who can open an item: for an item's access settings, use permission_get.

  ConnectorOAuth

• list_appsA

  Review ExpertA

  Lists the App Store and Google Play apps connected to your Review Expert team (id, name, platform, store id, last sync). Call this first: other tools take the returned id as app_id. Example: {"platform": "google_play"} for Android apps only. setup_required means no store app is connected: tell the user to open the link in the error, and do not report zero reviews. syncing means the first sync is still running.

  ConnectorAPI key

• delete_teamA

  CalyB

  Delete a team with its event types and memberships. Owners only. A team with a running subscription must cancel it first (manage_subscription). Two steps: the first call returns CONFIRMATION_REQUIRED with a confirmToken; tell the user, then call again with the SAME arguments plus confirmToken.

  Connector

  Destructive

  OAuth

• instagram_collaboration_invites_listA

  PostproxyB

  List incoming Instagram collaboration invites: posts from other accounts that invited this profile as a collaborator. Each invite has media_id, media_owner_username, caption and media_url (omitted for videos with copyrighted or licensed audio). Paginate with after = next_cursor (null on the last page). Accept or decline with instagram_collaboration_invite_accept / _decline. To send invites, pass collaborators to post_publish. Only works for Instagram profiles connected through Facebook Login — Instagram Login profiles get 422.

  ConnectorOAuth

• follow_teamA

  beep.meA

  Sign the user up for an email reminder before EVERY upcoming match of a football team. Matches added or moved later are covered too, so the user never has to come back. Use it when the user says every match, all matches, whenever <team> plays, or follow <team>; for one match, use remind_me. Ask the user for their email address first (never guess it). A new address gets one confirmation email, and the reminders start once the user clicks the link in it. Every reminder has a link to stop following. Only for teams, never for personal appointments. When beep.me is connected with sign-in, leave email out: it is on at once, with no confirmation email.

  ConnectorNo auth

• find_pulore_case_studiesA

  Pulore App PlannerA

  Use this only when someone asks about Pulore's own work or experience, for example whether Pulore has built something like their idea. Finds published Pulore case studies related to a topic, matching industry, platform, services and technology tags, and returns each project's summary and link, with timeline, team size and results where the case study publishes them. Searches the case-study files bundled with this server; it does not browse or modify external sites. Returns nothing when no project matches. Don't use it to find examples of other companies' products.

  ConnectorNo auth

• instructions-getA

  hjarniA

  Get LLM instructions at the specified level. Call with level 'brain' early in conversations to learn user preferences. Optional: level ('brain'|'personal_root'|'container'|'team'), defaults to 'brain' if omitted or blank; the response echoes resolved_level and defaulted_level (true when the level was defaulted). Optional: id (integer, required for 'container' and 'team' levels). 'container' level takes a personal (or shared) container id and returns the full inheritance chain, outermost first; each entry carries a `level` field ('brain'|'personal_root'|'team'|'container'). Team container ids are not addressable here — read a team note's chain from notes-get, or the team's own instructions with level 'team'. For an agent token, level 'brain' also returns agent_instructions, written by its person for that agent alone; brain_instructions_off: true means its person kept their brain instructions from it.

  ConnectorOAuth

• fantasy_get_weekly_digestA

  League LoomA

  Weekly report for ONE league or ALL configured leagues: "what needs attention this week", "my weekly rundown/recap", or waiver review. For identified teams: prioritized roster checks, standings, matchups, position-matched waiver candidates, remaining FAAB where available, recent moves and explicit missing-data warnings. Without an identified team it returns a league overview (standings, matchups, recent activity); team selection is optional. Pass league_query when the user names one league; otherwise all matching leagues are included. Needs a connected profile. Candidates are options to review, not proven upgrades; preserve coverage warnings and verify injury freshness. For a simple single-team snapshot, fantasy_get_my_team.

  ConnectorOAuth

• get_account_metricsA

  SocialGPTA

  Get per-platform engagement (views / likes / comments / shares) as a time series over the trailing window_days (default 28, up to 365). Omit account_id to aggregate across all connected accounts, or pass one from list_accounts; optionally filter to a single platform. post_limit (≤100) fixes how many recent posts form the baseline. granularity buckets the series server-side ('daily' default, 'weekly', or 'raw' for every scrape). Read `series` (a clean per-platform list of typed points) — `metrics` is the legacy column/data matrix kept for back-compat. NB: follower counts here are latest-only; for audience growth over time use get_follower_history.

  ConnectorOAuth

• create_support_ticketA

  BorealHostB

  Open a support ticket with the BorealHost team. Use this to escalate platform-side problems you cannot fix with the available tools (billing issues, infrastructure faults, API bugs). A human answers every ticket — poll get_support_ticket for updates. Requires: API key with write scope. Args: subject: Short summary (max 200 chars) message: Full description (max 20000 chars) category: Optional (e.g. "technical", "billing") site: Optional site slug the ticket concerns Returns: {"id", "subject", "status", "message": "Ticket created..."}

  ConnectorNo auth