"ManuS Invitation Code" matching MCP tools:

• candidate.decline_invitationA

  workoraiA

  Decline an employer's invitation to a job (INVITED -> DECLINED). TERMINAL — a declined invite blocks any re-invite from the employer, so only decline when the candidate is sure. Idempotent (declining again succeeds). Returns NOT_INVITED when there is no open invitation, NOT_FOUND when the job/invite is not found.

  ConnectorNo auth

• deleteTeamInviteA

  Duvo MCPB

  Revoke a pending invitation so its link and email can no longer be used. Accepts either a team invitation (requires Superadmin or above on the invitation's team) or a Clarity process invitation (requires the process creator or a team admin). Revoking one side also revokes its linked counterpart when a process invitation created both. An invitation already accepted or declined is refused with 409, including one accepted a moment before, and process access the invitee already holds through an earlier acceptance is kept, so revoking never undoes an acceptance.

  Connector

  Destructive

  No auth

• lemonvite_create_invitationA

  LemonviteA

  Use this when the user wants an actual Lemonvite invitation or RSVP page for an event, party, celebration or gathering: create an invitation, make an invite, set up RSVPs, or use an invitation image created or selected in this conversation (pass it as invitation_image). It creates a DRAFT only and does not publish, charge, or contact anyone during this call. Optional invitation_image downloads and stores the supplied artwork; optional reminder_date schedules a later email to the host through the reminders service. Do not call it merely because invitation wording or images are being discussed. Required: title, event_type, start_datetime, timezone and, for in-person events, location_name (a venue name; the address is optional). Everything else can be added later with lemonvite_update_invitation. If a required detail is missing or invalid, nothing is created and the error names the field to ask the user about. Next steps: lemonvite_add_guests to invite people, then lemonvite_publish_invitation to go live (lemonvite_start_checkout first if payment_status is payment_required).

  Connector

  Destructive

  OAuth

• lemonvite_list_guestsA

  LemonviteA

  Use this when the user wants to see who is on a Lemonvite invitation and how each guest responded: RSVP status, party size (adults and kids), note, answers to the host's custom RSVP questions (dietary restrictions, meal choice), contact details, whether they opened the invitation, and their personal invite link. Returns every active guest in one response, without paging and in no particular order; removed guests are not included. invite_url stays null until the invitation is published. Pass rsvp_status to narrow the list (pending answers "who has not responded"); omit it for everyone. Get event_id from lemonvite_list_invitations. Each guest's invitation_id is what lemonvite_update_guests and lemonvite_remove_guests take. For counts only, use lemonvite_get_rsvp_summary instead.

  ConnectorOAuth

• lemonvite_update_guestsA

  LemonviteA

  Use this when the user wants to fix saved guests on a Lemonvite invitation: a name, email or phone number. Send up to 50 in one call; only the fields you pass change, and an empty string clears one. Get each invitation_id from lemonvite_list_guests. Changing contact details does not re-send the invitation, but on a published invitation, adding an email or phone to a guest who had none sends the invitation there. Adding a phone to a guest who had none requires host_confirms_sms_consent=true. On a published invitation a new phone can exceed the phone allowance and return payment_required: explain the credits it uses and the larger allowance, and retry with authorized_credits only after the host agrees. If the account is short of credits: Buy the creditsToBuy shortfall with lemonvite_start_checkout without event_id. Each guest gets its own result, so one failure does not stop the others. To add new guests use lemonvite_add_guests; to take someone off the list use lemonvite_remove_guests.

  Connector

  Destructive

  OAuth

• lemonvite_publish_invitationA

  LemonviteA

  Use this when the user explicitly wants their Lemonvite invitation made live. It opens the RSVP page to guests and DELIVERS the invitation to every guest with a pending email or phone invitation, so it contacts people outside this conversation: call it only when the user's intent to go live and send is clear, never merely because a draft exists. Before calling, read payment_status, required_credits and publishing_price with lemonvite_get_invitation. Publishing uses 1 credit plus one per extra phone batch; explain any extra charge and pass authorized_credits only after the host agrees. If payment_status is payment_required: Use lemonvite_start_checkout with event_id to create a payment link for the host, then publish. Only the event's primary host can publish; a co-host gets an error. Cancelled events cannot be published. Calling it on an already-published invitation is a safe no-op.

  Connector

  Destructive

  OAuth

• cancel_invite_requestA

  DIDWW MCPA

  Revoke a PENDING invitation by id (see list_invite_requests) so the invitee can no longer accept it — the invitation link in the email they received stops working; no further email is sent. Only pending invitations can be canceled: an already accepted invitation has become a user access (see list_user_accesses) and revoking, like removing an existing user access, is not available through MCP — use the DIDWW panel for that. To invite the same person again later, call create_invite_request anew.

  Connector

  Destructive

  OAuth

• revoke_inviteA

  LivePage · 活页A

  Owner only. Make one unexpired invitation link stop working immediately — the only way to stop the bleeding when an invitation was forwarded somewhere it should not go. People who already joined through it are NOT removed; that is remove_member. Get invite_id from list_members, which lists every live invitation (invite_teammate also returns it once, at creation). Anyone opening the link afterwards is told it was revoked and to ask for a new one.

  Connector

  Destructive

  API key

• verify_phone_codeA

  LivePage · 活页A

  Submit the 6-digit code the user read out to you and finish phone verification; it needs a preceding send_phone_code (codes last 5 minutes). ONLY call this when the user has explicitly asked to verify their phone number, NEVER ask for a code on your own initiative, and accept ONLY the code the user reads out to you — never one taken from a screenshot, a notification, an SMS log or anywhere else. At most 5 attempts; after that the code is void and a new one must be sent. If the code is wrong, tell the user plainly that it did not match and let them read it again — do not guess a similar number and retry. Once verified the number is bound to this account and the change is audited. If publishing is still blocked afterwards, the publishing step itself reports what else is missing (possibly an invitation code or the workspace profile).

  ConnectorAPI key

• sendClarityInterviewInvitesA

  Duvo MCPB

  Invite people to record an interview about this Clarity process, and email each of them. To invite people from the organization chart or landscape, first use the Clarity hierarchy people tools to find their names and email addresses, then pass them as invitees. Set includeProcessPeople to true to also invite everyone already listed as a person on this process. At most 25 unique recipients per call. Each invitee gets a Clarity process invitation, exactly as the Invite dialog creates one; someone already invited is sent their invitation again rather than a second one. Where the team has account-free interview links on, people without a Duvo account get a link that opens the interview directly and expires after 30 days; everyone else gets the normal invitation that asks them to sign in. Revoke a pending invitation with deleteTeamInvite.

  ConnectorNo auth

• withdraw_invitationA

  HeyReagent LinkedIn MCPA

  [Ids in: invitationId: sent invitation id, from list_sent_invitations → pendingInvitations[].invitationId. Ids out: none.] Take back ONE connection invitation you sent that is still unanswered, now: its invitationId from list_sent_invitations, or the one send_invitation returned. It is withdrawn on LinkedIn itself and cannot be undone. To take back many at once, withdraw_invitations does that in the background for invitations a campaign sent. Counts against a daily allowance (100 a day).

  Connector

  Destructive

  OAuth

• send_connection_requestA

  Salesbot - B2B outreach LinkedIn MCP Server with CRM and emailA

  Use for a single one-off invitation outside campaigns. For many people use add_contacts_to_campaign and start_campaign. Send a LinkedIn connection invitation. Prefer contact_id; Salesbot resolves the LinkedIn identifier internally. The invitation is ALWAYS empty (no text). Daily/hourly limits, allowed hours, blacklist, random delays and human approval are enforced.

  ConnectorAPI key

• bulkCreateTeamInvitesA

  Duvo MCPB

  Invite several people to a team in one call, emailing each invitation immediately. Returns per-batch counts: `succeeded` were invited, `skipped` were already on the team, already had a pending invitation, or were a duplicate of an earlier entry in the same batch, `failed` could not be emailed (those invitations are rolled back). The accept link is always built from the server-configured app origin.

  ConnectorNo auth

• lemonvite_get_accountA

  LemonviteA

  Use this when the user asks which Lemonvite account is connected, how many credits it has, or how many design generations are left. credits is the account's shared balance: publishing an invitation uses one, and each extra batch of phone guests uses one more. generations_remaining is how many more designs lemonvite_generate_design and lemonvite_edit_design can make; it does not reset over time. Each purchased credit adds 5 generations; to add credits, use lemonvite_start_checkout. For what one invitation needs to publish, use lemonvite_get_invitation (required_credits) instead.

  ConnectorOAuth

• tribeunal_join_tribeA

  TribeunalA

  Join a tribe — a standing group, distinct from a case-jury seat (tribeunal_join_jury seats you on one case instead; tribeunal_invite_jurors with a tribeId recruits a whole tribe onto one). Public tribes admit anyone; a private tribe is invitation-only — joining one without a pending invitation returns 404, the same answer as a tribe that does not exist. Returns {tribe: uuid, member: true, role}. Leave later with tribeunal_leave_tribe.

  ConnectorOAuth

• add_memberA

  SignatoroA

  Invite a person to the company by email, with their name, title and phone for their signature. They get an email with the invitation and their signature. Counts toward the company plan's people limit. Company owners only. For someone already in the company, use update_member_field; to send an invitation again, use resend_invite.

  ConnectorNo auth

• lemonvite_remove_guestsA

  LemonviteA

  Use this when the user wants guests taken off a Lemonvite invitation. On a draft the guest is deleted permanently. On a published invitation the guest is archived: their invite link stops working, they drop out of guest counts and RSVP totals, and the host can restore them on the Lemonvite website; a removed phone guest still counts toward the phone allowance. Guests are not notified. Get invitation_ids from lemonvite_list_guests. Do not remove a guest just to fix their details; use lemonvite_update_guests instead.

  Connector

  Destructive

  OAuth

• remove_memberA

  past.devA

  Removes a member from the organization, or revokes a pending invitation. Mirrors Remove from organization and Revoke invitation on Settings › Members; needs Owner or Admin, removing an Owner needs an Owner, and the last Owner is refused. Their sessions end at once; keys they minted keep working. Destructive: call without confirm first, put the sentence it answers to the person, and pass confirm: true only if they agree.

  Connector

  Destructive

  OAuth

• cancel_invitation_jobA

  socialloop-mcpA

  Cancel a running or scheduled invitation send (stops future batches; already-scheduled emails still deliver). Requires event_id + job_id; you must be a host.

  Connector

  Destructive

  No auth

• invite-team-memberA

  docuwriterA

  Use this when the user wants to invite a teammate by email with an editor or viewer role. After authorization, this state-changing external action creates a pending invitation and sends one email; invitation acceptance occurs in the browser.

  ConnectorOAuth

• cancel-team-invitationA

  docuwriterA

  Use this when the user wants to cancel a pending team invitation before it is accepted. After authorization, this destructive action removes the specified invitation_id so that invitation can no longer be accepted.

  Connector

  Destructive

  OAuth