Connect an assistant that supports remote MCP and OAuth to manage 1:1 sessions and bookings, webinars, courses, locked content, lead magnets, digital products, payment pages, paid Telegram communities, and Instagram or Facebook Messenger Auto-DM automations. Available to every SuperProfile creator.
In Claude, add SuperProfile from the connector directory. In any other assistant, add https://mcp.superprofile.bio/mcp as a remote MCP server. Start its sign-in flow, choose the permissions you need, then approve in SuperProfile. Product-only access needs no Instagram account or Messenger Page. Select social accounts separately when using Auto-DM. Manage or revoke access in Connected agents.
Ask: “Create a draft payment page for my guide, upload this PDF, price it at ₹499, and show me the existing editor before publishing.” Start with get_product_context. Product tools cover digital offers, multi-item catalogs and eligible existing-product checkout pages.
List and read products; prepare and save drafts; edit, publish, unpublish, duplicate and delete eligible products. Configure supported prices and regional pricing, coupons, quantities, registration questions, content sections, policies, tracking IDs, themes and post-purchase behavior. Preserve the returned item IDs and read the current version before editing. Shared account credentials, payment onboarding and moderation decisions remain in their existing authorized setup flows.
Use list_product_assets to find verified uploads or attachments on an owned product. prepare_product_asset_upload returns a 24-hour transfer URL or browser file-selection link. Cover limit: 10 MiB; paid delivery: 100 MiB per item, subject to the shared quota of 512 MiB retained, 128 MiB per day and four pending uploads. Files upload outside MCP; size, SHA-256 and content type are checked before use. Paid files use private storage, and delivery videos wait for hosting/encoding. Poll the same operation after a timeout.
Create and edit bump offers, attach them to a page, and manage that page’s store placement separately. Product email tools manage purchase/cart rules, delays and templates with separate activation permission. Pause/delete change future matching; queued messages retain existing delivery behavior. Read sales, customers and analytics, or request a bounded private CSV export; customer contact data requires its own permission.
prepare_product validates a proposal without publishing. Commit its exact preview token with the matching draft/edit/publish tool and retain the same idempotency key after uncertainty. Money is expressed as decimal major-unit strings, such as "36.14" USD. Live or previously published edits require publication permission. A committed configuration may still be propagating or awaiting review: use get_operation and the returned state before calling it live. Existing buyers keep the existing download flow.
Start with get_course_context, get_locked_content_context or get_lead_magnet_context. Each family supports discovery, drafts, current-version edits, publishing, unpublishing, duplication, deletion, store placement and reports. Existing editors use the same authoring rules. Read each operation’s permissions and prerequisites; an older connection gains no new access automatically.
Courses include chapters and lessons, prerequisites and drip settings, supported live sessions and resources, quizzes and assignments, certificate settings, offers and email rules. Reading learner submissions and grading assignments require separate permissions. Locked content supports protected text and media. Lead magnets support registration questions, giveaway files, redirects, email rules and reusable template designs; sharing a template does not share private giveaway files or email configuration.
Use prepare_learning_asset_upload for course or locked-content media up to 5 GiB. Send file metadata and PUT bytes outside MCP, or open the returned browser upload link. The server verifies bytes and waits for video hosting before the asset becomes usable. Sessions last 24 hours; learning allowances are 20 GiB retained, 10 GiB selected uploads per UTC day and four pending sessions. Cover images and lead giveaway files use the product asset tools and their applicable limits. Consult the family context for smaller attachment limits.
Preparing a change does not publish it. Draft/edit, publication, deletion, customer information and email activation have separate permissions. Use get_operation until the requested generation finishes propagating. Reports name their source, coverage and uncertainty; CSV links expire and stop working when the grant is revoked. Buyer checkout, access and download flows remain in the existing product.
Start with get_webinar_context. Prepare and save drafts for virtual, Zoom or in-person events, including sessions, tickets, bundles, discounts, questions, media, page content and tracking. Preserve returned child IDs and the current version when editing. Review the draft, then publish separately. Your existing event editor works with the same configuration.
Connect Zoom through the returned browser consent link. Meeting creation and updates may remain pending: poll get_operation, and review uncertain provider results in the event editor before retrying. Store placement, inactive automated-email rules, customer records and check-in have separate permissions.
get_webinar_analytics reads existing ticket totals, daily registration quantities, session and attribution counts, and dashboard visit metrics. Registration ranges are limited to 93 days; visit metrics retain the dashboard’s own periods. An unavailable source is reported explicitly. Native earnings are not a reconciled payout. get_webinar_insights reads the existing Insights feedback configuration.
Webinars continue to use the existing buyer checkout and registration flows. Attendee broadcasts, guest-invitation sending and review moderation are not exposed in this release. Deletion and cancellation through these tools are limited to events without registrations or sales; unpublishing closes new availability without removing attendee records.
Ask: “Create a 45-minute portfolio review call for ₹999 on Google Meet using my default availability, and show it to me before publishing.” Start with get_booking_context. Prepare and save inactive sessions with every step of the session editor: details, pricing and regional prices, meeting location, availability schedule, booking rules, questions, policies, testimonials and tracking. Preserve returned question IDs and the current version when editing, then publish separately as public or link-only.
Coupons, the session-recording add-on, booking page theme and regional pricing have their own tools and versions; coupon redemption counts are kept when a coupon changes. Availability schedules are read-only here and stay editable in the dashboard, as do calendar and Zoom connections.
list_bookings follows the dashboard views (upcoming, important, recurring, completed, cancelled) within a slot-start range of up to 93 days, and never returns meeting passwords or host room links. list_booking_responses and get_booking_response_analytics read reviews with the dashboard filters. Approving, rescheduling and cancelling customer appointments remain in the SuperProfile dashboard in this release.
Ask: “Set up a paid Telegram community for my group at ₹499 a month and show it to me before publishing.” Start with get_telegram_community_context. Connect your Telegram account with begin_telegram_connection: sign-in happens on a SuperProfile page in your browser, and a phone code or password is never entered in chat.
List your Telegram groups and channels, prepare a community page over one, then publish, update its details and settings, unpublish, republish or delete eligible communities. Manage plans, registration questions, coupons, affiliate settings and store placement. Add, edit or remove members, resend an invite and cancel a member’s autopay. Read sales, members and analytics, or request a private CSV export; member contact data requires its own permission.
Paid Discord or WhatsApp communities, newsletters, and email or WhatsApp broadcasts are not available through these tools.
“Create a draft automation for my Instagram post that sends my guide when someone comments INFO. Show me the draft before publishing.”
To let your assistant make changes, choose draft/edit access when connecting. Publishing and deleting have separate permissions. Review the checked permissions before choosing Allow access. An assistant that explicitly requests only read access will show only those choices.
If your assistant says it cannot make changes, reconnect it and request the missing permissions. Refreshing a token does not add permissions. Some clients need you to remove and add the connection again to open fresh consent. Your existing automations and other connections are unchanged.
Your assistant can list posts, stories and automations, prepare and save drafts, edit, duplicate, publish, pause or delete supported automations, and report recorded runs and tracked clicks. Instagram account consent requires you in a browser.
Start from comments on a specific, next or any post/reel, story replies, incoming DMs, live comments, or a fan sending you one of your posts or reels in a DM. Match configured keywords or any event. Reply publicly with up to three rotating comment replies. Add a follow request, collect an email address, choose delays and follow-ups, and use text, buttons, images, video, audio, PDFs or cards.
Buttons can link to one of your published products (payment pages, courses, webinars, 1:1 sessions, Telegram communities, locked content, lead magnets), your store or your referral link; the link is built for you. Follow-ups can run after a delay, when the link was not clicked, when there is no reply, when the product was or was not bought, when a lead form was not submitted, or as a referral-link nudge.
Connect Kit, Mailchimp or Klaviyo in Settings, then let your assistant choose where captured contacts go. It uploads your media and shows the complete draft before publication. New upload and destination permissions need your consent.
Comment and live workflows with variables or follow-ups need an opening message the recipient responds to. Meta’s messaging windows still apply. Next-post automations select the first eligible future post whose matching comment arrives. Your assistant can edit automations you built in the dashboard: settings you saved there stay as they are unless you ask to change them. Follow-ups must run within 23 hours of the fan's message; automations with later follow-ups stay editable in the dashboard.
Ask your assistant to add a “Send a DM” button to a primary text or card message. The reply can contain text, an image, video, audio, a PDF or a card. The fan must tap the button before that reply is sent. This works on Instagram and Messenger and uses your existing plan permissions.
Button replies can include URL buttons; another Send-a-DM action inside that reply is not supported. Follow-ups keep URL buttons only. Ask the assistant to preserve returned button IDs when editing so previously sent buttons still point to the same reply.
Your assistant can find verified files with list_assets or start prepare_asset_upload. A local assistant uploads straight from disk. A browser-only assistant gives you a link to select your file. The session lasts 24 hours; file bytes never go through MCP. Poll get_operation until verification finishes, then use the asset in a draft. Cards need a verified image.
Image/PDF limit: 8 MiB; audio/video: 25 MiB. The allowance is 512 MiB retained, 128 MiB/day and four pending uploads. Older dashboard attachments may not appear in the verified library. New library access needs your consent.
Create automations for comments on a specific or any Page post, incoming DMs, referral links and QR codes. Share the returned Messenger link or download a black-and-white QR SVG. The recipient may need to tap Get Started.
Use text, buttons, verified media/cards, delays and after-delay follow-ups. Comment follow-ups require an opening message and recipient tap. Messenger follow gates, email capture, variables, public replies and conditional follow-ups are not supported.
Choose Messenger Pages explicitly when connecting your assistant. Existing Instagram permissions do not include Facebook Pages, and a Page connected only for ads still needs Messenger setup in Auto-DM. Custom-logo/color QR rules remain read-only.
Use MCP tool discovery and the backing tool schemas. Connect through the MCP URL; backing REST routes also require internal gateway authentication. OAuth supports S256 PKCE, rotating refresh tokens and revocation. Use the exact MCP resource URL during authorization and token exchange.
Read the saved version before editing. Every write takes an idempotency key: the current Unix time in milliseconds, a colon, then 16 or more new random letters or digits. Every get_*_context result returns serverTime to build it from, and a rejected key returns the server time and the clock difference. Reuse the same key and inputs after timeouts; get_operation retrieves the receipt. A version conflict requires rereading and reviewing the current configuration.
Tool discovery reflects your connection's permissions. get_product_context.operations and get_context.operations distinguish supported operations from currently authorized ones. Missing permissions return HTTP 403 with an insufficient_scope challenge and missingScopes/nextAction: reauthorize. Obtain fresh consent for the advertised scopes, then refresh tool discovery. Send one MCP request per HTTP POST.
Limits apply across your assistant connections. Respect retry guidance on 429/503 responses and keep the same idempotency key for uncertain writes. Invalid-input errors identify the fields to fix.
Drafts do not enable messages. Publishing needs explicit authority and the activation permission. Pausing prevents future automation evaluations; already selected or in-flight messages cannot be recalled.
Analytics uses explicit start-inclusive/end-exclusive windows and an IANA timezone, up to 90 days. Counts are events, not unique people or proof of delivery, reading, purchases or revenue. Freshness is unknown; recent events may still be processing.
A successful media upload or saved draft does not confirm delivery to the recipient. Meta may reject a file or message; verify your workflow with a test recipient before using it broadly.