Drry

What you can ask

• Search the real documentation before answering, so the answer is what the product does rather than what it probably does.Copy

  Example path search_help_articles→read_help_article

• The Studio: wordmark, colours, the words on every member page, the welcome flow, the home rails and the paywall.
• The loop for writing a landing page: draft it, read back what was actually stored, refine, and only then publish.
• The one link in a coach's Instagram or TikTok bio: a look, a header, what they offer in order, and publishing it.
• The coach's own multi-page site: a template, its pages, its look, its menu and footer, search and sharing, a check of each page, publishing, the home page and a launch check of the whole site.
• The whole chain: a form, the audience a signup joins, the email they get, and the journey that mails them afterwards.
• Read what members have posted and your own unread messages, draft replies, and send only what the coach approves.
• How to bring a coach's courses and contact list across from Kajabi, Skool, Teachable or similar, and what does NOT come with them.
• Bring a Squarespace, Wix or Webflow site over as real Drry pages: read the old site, rebuild each page, set the menu and footer, and send every old address on to its new page so links and search ranking survive the move.
• The audio library and its chapters and transcripts, plus how to put any content behind a membership rung.
• How to control the ORDER a member meets a course in: release schedules, lessons that unlock others, and a quiz gate.
• A reminder email, optionally with a discount code, to somebody who gave their email at a shop checkout and did not pay within 30 minutes.
• Create and price a product, run a membership offer, price or archive a membership tier, and set the free trial, confirming every amount with the coach before it goes live.
• The order to build a coach's community in: read what exists, name the surfaces, then create a course and its first lessons as drafts.
• How to compose a one-time or installment payment link for a single client, and what it deliberately cannot do.
• Events members can come to, and the session types a client can book time in.
• What needs the coach, what is coming up, and how the community is going, in one short report with a console link for each thing only the coach can do.
• The loop for a standalone written piece: a collection to hold it, the guide, its steps, and only then publishing.

MCP connector

Server URL

https://drry.com/api/mcpCopy

Login

OAuth

Protocol

MCP 2026-07-28

Instructions

Drry runs a coach's community: courses, a member feed, events, email, funnel pages, a website, a store and payments. Start with list_communities; every other tool needs the communityId it returns, and a coach may run more than one. Each family tool takes an act; read the act list in its description before calling. For "what needs me" or "how are things going", call community_insight/attention first. For a community still getting started, community_insight/next_step says what to build next. For how the business is doing, community_insight/revenue, community_insight/engagement and community_insight/content_performance give the analytics page's numbers. To build the coach's website: manage_site/read first, then a template or pages, the look, the menu, footer and header, search and sharing, manage_page/preview and manage_page/score on each page, publishing, and the home page (manage_site/set_home). New courses, lessons, guides, pages, forms and emails are drafts; publishing is always a separate act, and several acts email members or go public, so confirm those with the coach in the same turn. A draft nobody has seen can be deleted (never anything published, sent or switched on), and so can a page that is unpublished now and is not the home page; a deleted draft or page cannot be brought back, so confirm with the coach first. Posting and replying in the feed (manage_community) and replying in the coach's own direct messages (manage_messages) speak as the coach and reach members at once, so show the coach the words first. Product, offer, discount code, event ticket, paid session and membership-tier prices (manage_product, manage_offer, manage_event/update and manage_event/set_price_changes, manage_booking/update with a product, manage_tier) are live the moment they save (or the moment their window opens) and are charged to strangers' cards, so confirm every amount, code and date with the coach first; people who already paid keep what they pay. Refunds, the community's own single membership price, member removal and role changes, rulings on held or reported posts, and starting a new direct message are the coach's to do in the console. When an answer includes a console link, give it to the coach rather than describing where to click.

Tools

Skills

None in the store listings or on the server