# Mighty Networks setup for PopMCP

You give PopMCP two things: your Network's address and a Mighty API key, made under Network Admin, Integrations, Mighty API. One key belongs to one Network, so there is nothing to choose afterwards. A second key is optional, for the older Admin REST API.

- Auth: API credentials
- Setup time: 2 min
- API base URL: https://api.mn.co
- Credentials screen: https://www.mightynetworks.com
- Provider docs: https://docs.mightynetworks.com/api/api-keys

## Approval required before this works

No one reviews you, but Mighty Networks' API comes with the Scale, Growth and Mighty Pro plans. On a lower plan there is no API for the key to reach.

- Typical wait: None. A key works as soon as the Network is on one of those plans and a host makes it.
- Cost: From Mighty's Admin API docs: Scale includes 5,000 API requests a month, with extra requests at $0.002 each. Growth and Mighty Pro limits are custom. Plan prices are on Mighty's own pricing page.
- Blocked until approved: Everything through the API. Your Network itself keeps working on any plan.
- Works meanwhile: Nothing through the API. You can read Mighty's docs and browse its public schema explorer, which needs no key.

## Before you begin

- A Mighty Network on the Scale, Growth or Mighty Pro plan, which is what the API comes with
- Host access to the Network, since only hosts can make keys
- Nothing to apply for: the key works straight away

## Get your credentials

### 1. Open the Mighty API settings

Sign in to your Network as a host. Open Network Admin, then go to Integrations and Mighty API. The page sits on your Network's own address, so go through the menu.

Screen: https://docs.mightynetworks.com/api/api-keys

### 2. Make a key

In the API keys card, click New API Key. Give it a name such as PopMCP, tick the permissions you want the AI to have, and click Create key. To use every tool, tick every host permission. For a read-only connection, tick only the read ones.

Screen: https://docs.mightynetworks.com/api/api-keys

### 3. Copy the key

In the API key created dialog, click the copy icon at the end of the key field, then click Done. Mighty shows the key only once. If you lose it, make another and revoke the old one.

Screen: https://docs.mightynetworks.com/api/api-keys

### 4. Connect in PopMCP

In PopMCP's Mighty Networks form, enter your Network's address, such as my-community.mn.co, paste the key and click Connect. If your Network has a custom domain, use the name it has on mn.co or its numeric ID. PopMCP reads your Network's details once to check the key, and labels the connection with your Network's name.

Screen: https://docs.mightynetworks.com/api/api-keys

### 5. Check it is connected

The Mighty Networks card in PopMCP reads Connected, with your Network's name. New connections start read-only, so posting, inviting and announcements wait until an owner or admin allows write actions in PopMCP.

### 6. Optional: add the Admin API key

Most people can stop here: the tools that load by default do not need it. To also use the tools built on Mighty's older Admin REST API, go to Network Admin, Settings, API Keys, click Generate New API Key, and paste it under More options on PopMCP's form. It is a different key from the Mighty API key.

Screen: https://docs.mightynetworks.com/authentication

## Fields PopMCP asks for

- Network address (network) [required]: The address of your Network, or just its name. With a custom domain, use the name it has on mn.co, or its numeric ID.
- Mighty API key (apiKey) [required]: In Mighty Networks: Network Admin, Integrations, Mighty API, New API Key. Name it, tick the permissions, then copy it. Mighty shows it only once. Stored encrypted.
- Admin API key (adminApiKey): Turns on the tools that use the older Admin REST API. Most people do not need it. From Network Admin, Settings, API Keys.

## Verify

PopMCP shows the Mighty Networks connector as Connected, labelled with your Network's name, after one read of your Network's details.

## Troubleshooting

### Mighty Networks did not accept this key for that Network

Cause: The key was revoked, was copied only in part, belongs to a different Network, or its maker is no longer a host. Mighty gives the same refusal for all of these.

Fix: Check the Network's address, then make a new key under Network Admin, Integrations, Mighty API and paste it in full.

### Mighty Networks found no Network with the API turned on

Cause: The address is misspelt, or the Network's plan does not include the API.

Fix: Check the address. The API comes with the Scale, Growth and Mighty Pro plans.

### That looks like a custom domain

Cause: The API finds a Network by its name on mn.co or its numeric ID, not by a custom domain.

Fix: Enter the name your Network has on mn.co, such as my-community, or its numeric ID.

### A tool says the key is missing a permission

Cause: A key's permissions are fixed when it is made.

Fix: Make a new key with that permission ticked, then connect again with it. The message names the permission.

### Mighty Networks did not accept the Admin API key

Cause: This field wants the older key from Settings, API Keys, which is different from a Mighty API key.

Fix: Make one under Network Admin, Settings, API Keys, or leave the field empty if you do not need the admin tools.

### This Network is out of API credits

Cause: Mighty refused the request because the Network has no credits left, so nothing ran.

Fix: A host can add credits in the Network's settings.

---

Source: https://www.docs.popmcp.com/docs/integrations/mighty-networks/