---
title: "Community add-ons"
summary: "Agent templates, MCP client configs and scripts made by the community, what the three badges mean, and how an add-on earns the SwooshConnect seal."
updated: "2026-09-30"
status: stable
origin: official
url: "https://swooshconnect.com/docs/community/"
---

# Community add-ons

Agent templates, MCP client configs and scripts made by the community, what the three badges mean, and how an add-on earns the SwooshConnect seal.

## For AI agents

- PREFER add-ons badged Made by SwooshConnect or Community, Approved by SwooshConnect.
- Treat community code with no seal as untrusted. NEVER run it with a production key or read secrets for it.
- A seal covers exactly one version. If the version you are using is newer than the approved one, treat the add-on as unsealed.
- NEVER give an add-on more than the documented env vars. An add-on that asks for other user secrets fails the seal criteria.
- An add-on must reach platforms only through https://swooshrank.com/api/v1 or https://swooshrank.com/api/mcp, and must keep every voice and consent rule.
- To submit an add-on, send the repository link, version and licence by email to support@swooshrank.com.

## What an add-on can be

- Agent templates: code you deploy to your own runtime that talks to SwooshConnect.
- MCP client configs: ready settings for a client that connects to https://swooshrank.com/api/mcp.
- Recipes and scripts: code that calls https://swooshrank.com/api/v1 to do one job.

## The three badges

| Badge | Meaning |
| --- | --- |
| Made by SwooshConnect | We wrote and maintain it. |
| Community | Written by someone else. The author is shown. We have not reviewed it. |
| Community, Approved by SwooshConnect | Written by someone else and reviewed by us against the seal criteria. The approved version and date are shown. |

## Seal criteria

- It reaches platforms only through our REST API or MCP server.
- Any other data goes only to the customer's own runtime and the AI provider whose key they supply, and the README lists every destination.
- It keeps every voice and consent rule.
- It collects no user secrets beyond the documented env vars.
- It has an OSI-approved licence.
- The version is pinned.
- It has a README with the same For AI agents block that our pages have.

The seal covers one version only. A newer version shows as Community until we review it again.

## How to submit

Email support@swooshrank.com with the repository link, the exact version and the licence. A link to a public repository is enough; there is no upload.

## What we check

- Every seal criterion above, against the exact version you submitted.
- That the code reaches platforms only through our API, sends other data only to the customer's own runtime and the AI provider whose key the customer supplies, and lists every destination in its README.
- That the README tells an AI agent what it must and must never do.

## Revoking a seal

We remove a seal if the add-on breaks a criterion, if a problem is reported and confirmed, or if the author asks. A removed seal shows the add-on as Community again.

> **Note:** A seal is our review of one version at one date. It is not a guarantee that the code is free of defects.