# Use EchoDrop Social with Claude and other AI assistants

## Claude plugin directory listing

ECHOdrop Social is now listed in Claude's plugin directory:
https://claude.ai/plugins/all?q=echodrop

Find ECHOdrop in the directory, open the listing and follow Connect, then sign
in to ECHOdrop Social and approve the requested access. Enable the connection
for the conversation. A custom server address is not the default Claude setup.
The listing is a discovery and connection option, not a Claude endorsement,
independent audit or the site's separate AI-generated Claude assessment.

## Creator checkout and sale reports

### Continue the conversation after the sale

An optional confirmed-purchaser return step can provide another download,
uploaded or embedded video, or survey. Read `get_drop_post_purchase`, configure
with `update_drop_post_purchase` (`step:null` disables it), and prepare private
file uploads with `upload_post_purchase_asset`. PUT the actual bytes to the
returned upload URL before attaching its assetId. Human approval and tool
grants apply. `get_drop` also includes the follow-up setup.

Give the owner the campaign's returnUrl to use as a supported post-sale redirect
or a button on their thank-you/fulfillment page. Returning is never payment
proof. Only a matched authenticated native-provider paid event unlocks the
continuation; custom creator reports do not. Protected bonuses require
`{{leadId}}` to reach the provider and
return as the native event's lead reference; email-only activity matches cannot
unlock them. This prevents unrelated account-wide sales with the same email
from granting access. Identity must be verified again
when its session expires. Delayed confirmations show a waiting screen with no
protected content. Access is revisitable by default while payment evidence and
campaign rules permit it. Known refund/dispute evidence blocks access.

Uploaded videos can reveal a direct external button after linkAtSeconds of
playback (for example 10 seconds). Embedded-video links appear immediately.
Upsell clicks and purchases are not tracked. Surveys keep the original question
snapshot and one submission per verified lead per revision.

Owners can use the Tests tab's sandbox-only journey simulator to skip or jump
stages, simulate a successful purchase, skip video timers and restart. Its
SIMULATED JOURNEY badge is persistent. It creates no real recipient, purchase,
opt-in or outbound notification. Simulation is not payment-integration evidence.

### External checkout links and activity

Use `purchaseUrl` and `purchaseLabel` with `create_drop` or `update_drop` to offer
the creator's existing checkout after a successful pickup. Supported query-value
placeholders are `{{email}}`, `{{campaignId}}` and `{{leadId}}`; use parameter names
your checkout supports. Forwarding email shares it with that checkout.
Set `purchaseUrl:null` to remove the button.

`get_drop_purchase_events` accepts `{code, leadId?}` and reads unique checkout
clickers, total clicks, connected processor names and up to 100 recent events.
Clicks are not purchases; missing events mean unconfirmed, not unpaid. Native
events use provider-specific authentication; custom events are creator reports.
An event does not prove product delivery or a payment's reconciled current state.

### Supported ecommerce integrations

Human-only campaign settings offer preset connections for ThriveCart, Gumroad
signed Ping, Lemon Squeezy, Stripe, Shopify, PayPal, Square, Razorpay, Adyen
Standard, Braintree, Paddle Billing, Mollie classic payment callbacks, Polar and
Chargebee. The owner selects the provider, enables its supported notifications
and saves its verification details. No manual event-field mapping is required.
Supported events and verification methods vary. Secrets are encrypted and
unavailable through MCP; never ask the owner to paste credentials into chat.
Creators remain responsible for payment, delivery and refunds. Agents must not
open checkout, claim drops, charge money or manufacture sale reports. Social
sandboxes do not open real checkouts or record live conversions.

## Public campaign artwork

The `upload_campaign_image` tool hosts cover and social-preview images in
EchoDrop. Request a temporary upload URL with `action:"initiate_upload"`, filename
`name`, `mime_type` and exact byte `size`; PUT the original binary file to that
URL with its returned headers; then call `action:"complete_upload"` with the
returned `uploadId` in the same workspace. Only completion returns a permanent
public image URL. Use it in a new campaign, or request the usual owner-reviewed
`update_drop` diff for an existing campaign. Uploading alone edits no campaign.
PNG/JPEG/WebP, up to 5 MB or a lower workspace file limit, up to 25 million
pixels. The workspace image-library budget and limits are advertised by the tool.
Images are public marketing artwork, not gated rewards. Original bytes are
preserved; keep text readable rather than needlessly shrinking the image.

## Campaign questions

EchoDrop already collects and verifies each recipient's email address. Agents
must not ask for it again in required or optional questions, custom claim fields,
or capture-flow questions. Use the verified email already collected by EchoDrop.

Do not add a separate email-consent question or checkbox; EchoDrop does not
require it. Leave owner-authored offer terms unchanged. Verified email alone
does not establish unrestricted marketing permission.

> Markdown companion to https://echodrop.social/mcp. Last updated November 14, 2026.

The EchoDrop Social MCP connector lets an AI assistant work in your EchoDrop
account for you: create and edit lead-capture campaigns, prepare free sandboxes
for you to test, and read the activity, receipts and referral counts of the verified
contacts your audience shares with you. You stay in control of launching
campaigns, purchases and access settings.

## Add the connector

Server address: `https://echodrop.social/api/mcp`

This address is for your AI app's connector settings; opening it in a browser
does not connect anything.

### Claude (web, desktop and mobile)

1. Find **ECHOdrop** in Claude's plugin directory:
   https://claude.ai/plugins/all?q=echodrop. Open the listing to connect without
   entering a server address.
2. Choose **Connect**. A browser window opens on echodrop.social.
3. Sign in or create an account, review the access request and choose **Approve**.
4. Back in Claude, enable the connector for your conversation and ask it to list
   your workspaces.

### Other MCP clients

Add a remote (Streamable HTTP) MCP server with the address above. The client
discovers sign-in through `/.well-known/oauth-protected-resource`; it uses
OAuth 2.1 with PKCE and dynamic client registration, so no API key is needed.

## Sign-in and permissions

- You sign in on echodrop.social and approve the connection yourself. The
  assistant never sees your password.
- An approved connection lasts 90 days. After that, reconnect from your AI app.
- Social sign-in must stay on **echodrop.social**. If Claude shows the
  professional ECHOdrop connector, stop and remove/re-add the incorrect
  connector; that is a separate product, not a Social login.
- Claiming a Social drop is for people only. Assistants cannot pick up drops.
- In your EchoDrop dashboard you can switch agent access off for the whole
  account (the red **Stop MCP access** button), for a workspace or for a single
  campaign; turn off individual tools; and set a monthly limit on campaigns
  agents create.
- Agents cannot buy campaign packs, change access settings or accept agent-guide
  edits. Launching, revoking, pausing and resuming require your per-campaign grants.
  By default, campaigns an agent creates are paused for your review.

## Agent campaign controls

Drop Owners cannot remove, hide or disable the ECHOdrop marketing checkbox on Social drops. It is optional and unchecked by default for recipients; leaving it unchecked never blocks a pickup. Any configured offer terms remain a separate, required agreement with the Drop Owner.

At the top of each campaign's Agent tab, **Human approval** starts on. When on,
permitted edits and lifecycle actions need independent owner website approval.
Turn it off to let the agent perform permitted actions autonomously.
**Pause and resume** (orange, off by default) controls delivery, not testing.
**Go live and revoke** (red, off by default) permits first launch with one
shared account credit and reversible revocation. Relaunch preserves the current paid
365-day deadline and uses no further credit. Expired and revoked campaigns can
be duplicated into fresh sandboxes with new links and independent paid lifetimes.
To keep the same link instead, the signed-in owner can choose **Renew campaign**
in the website dashboard for one shared campaign credit. Renewal adds 365 days
to the later of the current end date and renewal time, before or after expiry.
It preserves the campaign and leads but does not resume paused, revoked or testing
campaigns. Previously deleted reward assets cannot be restored; campaigns whose
expiry cleanup started stay paused for content review. Renewal is human-only,
not an MCP tool or a permission granted by the go-live/revoke control.
The orange and red switches do not bypass Human approval while it is on.

Paid renewal is the one exception to the unchanged deadline for pause, revocation,
testing and free relaunch. The signed-in owner can renew repeatedly in advance,
one credit at a time, adding 365 days per confirmed renewal. The red grant does
not authorize renewal, and there is no automatic renewal or recurring charge.
While expired, the original link is unavailable for new pickups. Leads and
waitlist records stay with the saved campaign and account unless the owner
deletes them; renewal keeps those records and the same link. Deleted reward
assets cannot be restored.

Read `get_drop.agentControls` for the current grants. New and copied campaigns
always start with safe defaults. Agents cannot change the controls or buy credits.
A person must purchase credits first. Campaign credits are shared across all
the owner's Social workspaces, including Personal; no allocation, transfer or
campaign rebuild is needed to use them in another workspace.
With Human approval off and the desired grants on, an agent with its own social
account and posting access can run that campaign autonomously. EchoDrop manages
campaigns, not social accounts or posting access. Account stops, workspace/tool
restrictions, read-only tokens, saved guides and human-only pickups still apply.

## Tools

Tool availability follows your connection's permissions and scope. Start with
`get_echodrop_social_guide` and the current tool schemas; the website's ECHO chat
is a public product guide, not an agent signed in to your campaign account.

### Read-only

| Tool | What it does |
| --- | --- |
| `get_echodrop_social_guide` | Current operating guide and product rules. Read this and the available tool schemas before creating or reviewing campaigns. |
| `list_workspaces` | Your workspaces and which one the connection uses by default. |
| `list_sandbox_campaigns` | Free sandbox slots, sandbox campaigns by workspace, test-pickup counts and deletion dates. |
| `list_drops` | Campaigns in a workspace, with status. |
| `get_drop` | One campaign's full settings, files and links, code pool, video and your agent guide. |
| `get_drop_events` | A campaign's activity timeline. |
| `get_drop_receipts` | Signed download receipts for a campaign. |
| `get_drop_referrals` | Referral starts and completions per verified email, as JSON or CSV. |
| `get_drop_test_results` | Masked, campaign-scoped sandbox evidence after a person tests. Kept for seven days; agents cannot perform pickups or clear test history. Webhook dry runs are not sent. |

### Make changes

| Tool | What it does | Removes data |
| --- | --- | --- |
| `upload_campaign_image` | Host public cover and social-preview artwork in EchoDrop. PNG, JPEG or WebP; original quality preserved. Attachment follows Human approval. | No |
| `create_drop` | Create a campaign with uploaded files, links, questions, styling and terms. It starts as a free sandbox. | No |
| `duplicate_drop` | Copy a campaign's setup into a new sandbox. Leads, counts and codes are not copied. | No |
| `update_drop` | Edit campaign text, styling, questions, limits, sharing and notifications. Requires review when Human approval is on; otherwise permitted edits apply autonomously. | Yes (clearing fields, removing questions, replacing the capture flow) |
| `set_campaign_paused` | Pause or resume a sandbox or live campaign with the orange permission. | No |
| `go_live_drop` | Launch a sandbox with the red permission using one existing credit from the owner's shared account balance, never purchasing credits. | Uses a credit on first launch |
| `set_campaign_sandbox` | Turn testing on/off separately using enabled. Pause or revoke a live campaign first. Sandbox off never publishes or resumes delivery. | No |
| `suggest_agent_guide_edit` | Propose changes to a campaign's agent guide. Nothing changes until you accept. | No |
| `notify_owner` | Email you (and your optional webhook) when the assistant needs a decision. Five per day. | No |
| `update_drop_links` | Replace a campaign's link list; can permanently remove uploaded files when you confirm. | Yes |
| `update_drop_code_pool` | Add, prune or delete single-use code inventory. | Yes |
| `update_drop_video` | Upload, replace or delete an interactive video and its checkpoints. | Yes |
| `revoke_drop` | Withdraw a Social campaign reversibly. With the required grant, relaunch before its current paid end date without another credit. | No |

## When Human approval is on

- When your assistant edits a campaign with `update_drop`, nothing is saved at
  first. EchoDrop returns a diff of the proposed changes, grouped by section and
  listed field by field with the current and new value.
- Lines that clear a value, remove a question or replace the capture flow are
  marked REMOVES DATA.
- Your assistant must show you that diff and provide its review link. Sign in
  on EchoDrop Social to approve or reject. A yes in chat alone cannot authorize
  the change. Only then can the assistant save those exact changes, once.
  Links, code pools, uploaded video, revocation and sandbox on/off also
  require a website approval. If the campaign changes in the
  meantime, or the assistant tries different changes, it shows you a new diff.

## Sandbox and live campaigns

- Every new campaign, including a copy, starts as a free sandbox. You can hold
  four sandboxes at a time across your account.
- Sandboxes allow unlimited test pickups with a visible test code. Test sign-ups
  are never saved as leads.
- A sandbox is deleted seven days after it was created unless you take it live.
  Editing or testing does not extend that date.
- You, or an agent with Go live and revoke permission, take a campaign live using
  one campaign credit from your shared account balance across all your Social
  workspaces. Live campaigns stay live for 365 days from first launch unless
  revoked earlier. Pausing, testing, revoking and relaunching never extend that deadline.

## Limits

- Uploaded files are limited by your workspace's file-size and file-count
  settings; the `create_drop` tool description shows the current numbers.
- `notify_owner` sends at most five messages per account per UTC day.
- `get_drop_referrals` returns up to 500 rows per page; `list_drops` up to 200.

## Example prompts

- "Show my EchoDrop workspaces and how many free sandbox slots I have left."
- "Create a sandbox campaign in my Personal workspace that gives away my launch
  checklist at https://example.com/checklist.pdf, asks which platform people
  follow me on, and caps claims at 200."
- "Change the headline on campaign ABC123 to 'Your checklist is ready' and show
  a live claim counter."
- "Export the referral counts for campaign ABC123 as CSV and tell me who brought
  in the most leads."

## Troubleshooting

- **"Authentication required" or the tools disappear:** the connection expired
  or was removed. Reconnect from your AI app's connector settings.
- **`account_agent_access_off`:** MCP access is stopped for your account. Use
  **Start MCP access** in the dashboard.
- **`agent_access_off` or `tool_disabled`:** access is switched off for that
  workspace, campaign or tool. Change it on the Your drops page or in workspace
  settings.
- **`sandbox_limit_reached`:** all four sandbox slots are in use. Take one live
  or delete one; buying a pack alone doesn't free a slot.
- **`monthly_creation_limit_reached`:** your monthly limit for agent-created
  campaigns is reached. Raise it in workspace settings or wait for next month.
- **A campaign shows only its name:** agent access is off for that campaign.

## Privacy and support

The connector uses EchoDrop's own API and only reaches data in your account.
Lead data is handled as described in the Privacy Policy
(https://echodrop.social/privacy), Terms (https://echodrop.social/terms) and
DPA (https://echodrop.social/dpa).

Questions or problems: privacy@echodrop.social
