Integration

IndieFunnels integration

IndieFunnels is a website, shop and fan-marketing builder for independent musicians; every IndieFunnels website exposes its own Website API. List, find by email, create, update and delete contacts (the CRM) and members (the members area), manage member groups and email subscriber lists, list, create, update and delete store products and list categories, list orders and update their status, fulfillment and notes, list form submissions and bookings, read website traffic stats, and register or remove webhooks. Contacts, members, orders, bookings and form submissions are personal data. Left out: the single sign-on route that mints a member login link. Authentication is the API key shown in your website under Website Settings, Applications, API Key, sent as a bearer token, with your website's domain.

Connect IndieFunnels How integrations work

Ask it in chat

Say what should happen.
The workflow builds itself.

When this happens, do that in IndieFunnels.Built from the 37 IndieFunnels tools below, on the connection you add once.

What you can do with IndieFunnels

Each of these is one operation on one endpoint, available both as a workflow step and as a tool an AI agent can call on its own. Nothing bundles several operations into one action, so what a run did stays readable afterwards.

Most endpoints run on the free plan. A few, mainly the ones that publish on your behalf, need a paid plan.

Contact, 5 operations

create_contactCreate contactPOSTCreates a CRM contact, or updates the contact that already has this email: only the fields sent are set. email is required; tags, custom properties and subscriber list ids can be set too.
delete_contactDelete contactDELETEDeletes a CRM contact by id, with all data associated with it.
get_contactGet contactGETReturns one CRM contact by id: name, email, phone, address, company, private note, tags, custom properties, member id and subscriber lists. Personal data.
list_contactsList contactsGETLists the website's CRM contacts, 1 to 50 per page (limit, default 30; skip as offset), optionally only those created between created_at_min and created_at_max (Unix seconds). Contacts are personal data.
update_contactUpdate contactPUTUpdates a CRM contact by id. Only non-empty fields are set, so fields left out keep their value; email is required on every call.

Member, 5 operations

create_memberCreate memberPOSTCreates a member of the members area. With a password the member can log in with it; without one a random password is set and the member is emailed a password-reset link.
delete_memberDelete memberDELETEDeletes a member of the members area by id.
get_memberGet memberGETReturns one member by id: name, email, groups, approval, registration time, contact id and billing and shipping addresses. Personal data.
list_membersList membersGETLists the members of the website's members area (name, email, groups, approval, addresses), 1 to 50 per page, optionally only one member group (groupId). Personal data.
update_memberUpdate memberPUTUpdates a member by id. Only non-empty fields are set and the password is never changed; name and email are required on every call.

Member group, 5 operations

create_member_groupCreate member groupPOSTCreates a member group for the members area, with a name and an optional default page members are sent to after login.
delete_member_groupDelete member groupDELETEDeletes a member group by id.
get_member_groupGet member groupGETReturns one member group by id: name and the default page its members land on after login.
list_member_groupsList member groupsGETLists the member groups of the website's members area: id, name and the page members land on after login.
update_member_groupUpdate member groupPUTUpdates a member group by id. name is required on every call; the docs do not say whether a link left out is cleared, so send the current link too to keep it.

Product, 5 operations

create_productCreate productPOSTCreates a store product (physical, digital, service or membership) with title, URL handle, images, categories, options and priced variants. update_existing_product_by_url=true updates the product with the same URL instead.
delete_productDelete productDELETEDeletes a store product by id.
get_productGet productGETReturns one store product by id: type, title, description, URL handle, visibility, images, categories, options, variants (price, sale price, stock, SKU), subscription terms and digital file URL.
list_productsList productsGETLists store products (type, title, URL handle, images, categories, options, variants with price and stock), 1 to 50 per page, optionally in one category (subcategories included) or with a word in the title.
update_productUpdate productPUTUpdates a store product by id. Only non-empty fields or provided variants are set; type and title are required on every call.

Subscriber list, 5 operations

create_subscriber_listCreate subscriber listPOSTCreates an email-marketing subscriber list. Add contacts to it with create_contact or update_contact (subscriberLists).
delete_subscriber_listDelete subscriber listDELETEDeletes an email-marketing subscriber list by id.
get_subscriber_listGet subscriber listGETReturns one email-marketing subscriber list by id: name, creation time, subscriber count and open and click rates.
list_subscriber_listsList subscriber listsGETLists the email-marketing subscriber lists: id, name, creation time, subscriber count and open and click rates.
update_subscriber_listUpdate subscriber listPUTRenames an email-marketing subscriber list.

Order, 3 operations

get_orderGet orderGETReturns one store order by id: customer name and email, addresses, line items, taxes, discount, shipping, totals, payment, status, tags, extra fields and private notes. Personal data.
list_ordersList ordersGETLists store orders (customer, addresses, items, totals, payment, status), 1 to 50 per page, optionally only those created between created_at_min and created_at_max (Unix seconds). Personal data.
update_orderUpdate orderPUTUpdates a store order: status, paid flag, payment, customer and addresses, fulfillment (courier, tracking). Only non-empty fields are set. COMPLETED emails digital or membership access to the customer.

Webhook, 3 operations

create_webhookCreate webhookPOSTRegisters a webhook: the website POSTs the chosen events (orders, products, form submissions, contact updates, bookings) to the target URL, signed with the optional secret. Payloads carry personal data to that URL.
delete_webhookDelete webhookDELETEDeletes a webhook by id; the website stops sending events to its target URL.
list_webhooksList webhooksGETLists the webhooks registered on the website: id, target URL and the events each one sends. Signing secrets are not returned.

Search by email, 2 operations

search_contact_by_emailSearch contact by emailGETLooks up the CRM contact with the given email address and returns it (name, phone, address, company, tags, custom properties, subscriber lists); 404 when none. Personal data.
search_member_by_emailSearch member by emailGETLooks up the member with the given email address: id, name, groups, approval, registration time, contact id and addresses; 404 when none. Personal data.

Booking, 1 operation

list_bookingsList bookingsGETLists booked sessions of the website's booking calendar, 1 to 50 per page (limit, skip), optionally only those starting between from and to (Unix seconds) or for one eventId. Returns attendee names, emails and answers: personal data.

Category, 1 operation

list_categoriesList categoriesGETLists the store's product categories (id, name, URL handle, parent id), optionally only the direct sub-categories of one parent category.

Form submission, 1 operation

list_form_submissionsList form submissionsGETLists messages sent through the website's forms (form name, time received, submitted field values), 1 to 50 per page, optionally received between from and to (Unix seconds). Submissions usually hold personal data.

Stat, 1 operation

get_statsGet statsGETReturns website stats in data, by type: hourly (the day in from), daily, referrers, devices or browsers (from to to, yyyy-mm-dd), or usage (storage, bandwidth). Days or hours without traffic are left out.

Use IndieFunnels from Claude Code, Cursor or Codex

Connect IndieFunnels in LiveContext, create an API key in Settings, then add the LiveContext MCP server to your client. Its IndieFunnels operations become tools the client can call, next to every other integration you connected.

Claude Code

claude mcp add --transport http livecontext https://livecontext.ai/mcp --header "X-API-Key: YOUR_API_KEY"

Codex (~/.codex/config.toml)

[mcp_servers.livecontext]
url = "https://livecontext.ai/mcp"

[mcp_servers.livecontext.http_headers]
"X-API-Key" = "YOUR_API_KEY"

Cursor, Claude Desktop and other JSON configs

{
  "mcpServers": {
    "livecontext": {
      "type": "http",
      "url": "https://livecontext.ai/mcp",
      "headers": {
        "X-API-Key": "YOUR_API_KEY"
      }
    }
  }
}

Set up the MCP server step by step

How to connect IndieFunnels

Create your workspace
Sign up free. Nothing to install.
Connect IndieFunnels once
Add your IndieFunnels connection in Settings. Every tool from this integration reuses it, and secrets are encrypted at rest and visible only to you.
Describe the job in chat
The workflow builds itself in front of you and picks the endpoints it needs. Drag the steps yourself on the canvas whenever you would rather be explicit.