Mighty Networks
Manage members, spaces, posts, comments, events, invites and tags in a Mighty Networks community via the Admin API.
About
Mighty Networks ships in the w6w first-party pack. It declares 31 actions, 2 health checks, and the host runs its code in a sandbox that never sees the credential.
- App id
io.w6w.mighty-networks- Version
- 0.1.0
- Author
- w6w
- Licence
- MIT
- Categories
- Communication · Social Media
Overview
Mighty Networks is a community platform for creators and brands — spaces, courses, events, posts and paid plans under one branded Network — and this app runs it through the Mighty Networks Admin API.
It covers the operational core of a Network: members (list, look up by id or email, create, update, add to or remove from spaces, tag), spaces, posts and comments, events with RSVPs, invitations, tags, plans and course content. A connection is one Network: the Network ID or subdomain is stored with the Admin API token, so no action asks for it again.
Good for onboarding automation — create a member or send an invite and drop them into the right spaces and tags — for publishing posts and scheduling events from another system, and for reading a Network’s membership, plans and course structure into a CRM or reporting tool. The Admin API needs the Scale, Growth or Mighty Pro plan.
Build with Mighty Networks
Three routes to the same 31 actions. The Workflow tab is generated from Mighty Networks's own manifest and carries its real ids, so it is copy-pasteable; the Code and CLI examples are the same call for any action on any app, so every app-specific value in them is a blank you fill in.
List Coursework
coursework-list List the lessons, quizzes and sections of a course (a space), one page at a time.
Get Token Identity
me-get Return the user and Network the API token belongs to. A cheap way to confirm the connection works.
Create Member
member-create Add a person to the Network, optionally as a limited member of specific spaces.
Remove Member from Space
space-member-remove Remove a member from a space. Their other spaces and their Network membership are untouched.
A workflow step names the app and the action, and the editor fills in the
connection when you pick one. This is the Step shape from the
workflow spec, carrying Mighty Networks's real ids.
{
"manifestVersion": "2",
"name": "mighty-networks-example",
"steps": [
{
"id": "comment-create",
"uses": {
"app": "io.w6w.mighty-networks",
"action": "comment-create",
"connection": "conn_YOUR_CONNECTION_ID"
},
"with": {
"postId": "<postId>",
"text": "<text>"
}
}
]
}Here are some of the things you can do
-
Create Comment
performcomment-create -
List Comments
searchcomment-list -
List Coursework
searchcoursework-list -
Create Event
performevent-create -
Get Event
readevent-get
+26 more actions available
Every app-specific value here is a blank you have to fill in. An
app action is reached through the connection that authenticates it, so the
address is a connection id, not the app id — and connections belong to your account,
so a public page cannot know yours. Create one for Mighty Networks, then fill in
the three blanks: conn_YOUR_CONNECTION_ID, the action key, and the
parameters that action declares. The call itself is real — the shape is transcribed
from the studio's own snippet builder, which prints the same kind of blanks — but
nothing in it is specific to Mighty Networks. The Workflow tab is where this app's
real ids are.
npm install @w6w/sdkyarn add @w6w/sdkpnpm add @w6w/sdkdeno add npm:@w6w/sdkimport { W6wClient, isActionRun } from "@w6w/sdk";
// Reads W6W_BASE_URL and W6W_TOKEN from the environment when omitted.
const client = new W6wClient();
const envelope = await client.run({
urn: "conn_YOUR_CONNECTION_ID",
action: "comment-create",
payload: {
postId: "<value>",
text: "<value>",
// replyToId: "<value>",
},
});
if (isActionRun(envelope)) console.log(envelope.value);npm install -g @w6w/cliw6w run conn_YOUR_CONNECTION_ID --action comment-create --payload '{"postId":"<value>","text":"<value>"}'Give an AI agent Mighty Networks — without giving it Mighty Networks's credentials. One MCP endpoint exposes every app, function and workflow the caller is entitled to, as tools it can discover and run. Access is granted per team while we onboard.
One tool call{
"name": "w6w_invoke",
"arguments": {
"ref": "app:io.w6w.mighty-networks#comment-create",
"input": {
"postId": "<postId>",
"text": "<text>"
}
}
}
Every tool names its target with a single ref. The
app: form above doesn't name a connection at all — the
host resolves which of the caller's Mighty Networks connections to sign
with, and refuses rather than guesses when the answer is ambiguous.
What the agent gets
Credentials it can't read
The token is attached host-side, at the moment of the call. It is never a tool argument, never in the model's context, and never in a transcript — so a prompt injection has nothing to exfiltrate.
A tool surface scoped to the caller
Tools are derived per end user from what that person has actually connected and is entitled to — not one shared bot identity carrying the union of everyone's access.
A durable workflow in one call
Multi-step work runs on the workflow engine and returns a run handle the agent can poll — retries, branching and state survive the conversation that started them.
Health-aware discovery
Mighty Networks's declared health checks are on the surface too, so an agent can tell "the vendor is down" from "your credential expired" before it burns a retry on either.
The MCP surface is part of the hosted platform. Mighty Networks itself is MIT, and the runtime that executes it is source-available (FSL).
Health checks
Mighty Networks declares its own checks, so its health is a property of the app rather than something the host guesses at.
Mighty Networks platform status
Status page summary for status.mightynetworks.com. The verdict tracks the `API Access` component — the surface this app calls — rather than the page-wide indicator, which also covers the mobile apps and marketing site. All components are reported.