> ## Documentation Index
> Fetch the complete documentation index at: https://docs.famulor.io/llms.txt
> Use this file to discover all available pages before exploring further.

# Request or build a missing app

> Ask for an app that's missing from Agent Connectors or the App Catalog, or publish your own connector or automation template on GitHub

When the app you need isn't in [Agent Connectors](https://docs.famulor.io/assistants/agent-tools.md#agent-connectors) or the [App Catalog](https://docs.famulor.io/automations/app-catalog.md), you can request it, or build it yourself and submit it to the [Famulor Marketplace](https://github.com/Famulor-SI/famulor-marketplace) on GitHub. The Famulor team reviews every submission before it appears in the app.

## Request an app

1. Open **Agent Tools → Agent Connectors** and scroll to the card **Couldn't find the tool you want?**
2. Select **Request on GitHub** and fill in the **Request an app** form: the app, its website and one real situation, for example "When a caller asks about an open invoice, the assistant reads the amount and due date."
3. Without a GitHub account, select **Send feedback** instead.

In the Automation builder, **Request on GitHub** appears below **No apps match your search.**

## What you can build

| Submission | What your workspace gets |
| - | - |
| **MCP server** | A card in **Agent Connectors**. Assistants call its tools in calls, chats, messages and emails; automations can use it as an MCP connection. |
| **API tool** | A card in **Agent Connectors** that installs one HTTPS request, for example "look up an order". |
| **Automation template** | A ready-made workflow under **Automation → New → Start from template**. |

Each submission is one folder in the repository. App vendors list their own app; developers can build one for an app they're allowed to publish.

## Submit a connector

1. Fork [famulor-marketplace](https://github.com/Famulor-SI/famulor-marketplace) and copy an example from `examples/connectors/` to `connectors/<your-app>/`.
2. Fill in `connector.json`: name, description, category, the install form and the tool Famulor creates on install. Add a square logo and a README with **What it does**, **Setup** and **Data and privacy**.
3. Test it in your workspace. Add an MCP server with **Add custom MCP connector**, or rebuild the request as a **Custom Agent Tool**, and try it in a test call or chat.
4. Run `node scripts/validate.mjs` and `node scripts/build-catalog.mjs`, then open a pull request.

The [contribution guide](https://github.com/Famulor-SI/famulor-marketplace/blob/main/CONTRIBUTING.md) explains every field.

## Submit an automation template

1. Build and test the automation, then choose **⋯ → Export** to download it.
2. Save the file as `automation.famulor-automation.json` in `automations/<your-template>/`, next to a `listing.json` and a README.
3. Open a pull request.

The export removes keys, connections, webhook addresses and assistants. Text you typed into steps stays, so replace names, phone numbers and email addresses with placeholders before you submit. See [Export and import](https://docs.famulor.io/automations/overview.md#export-and-import).

## Review and release

* **Checks:** every pull request runs the same checks as `node scripts/validate.mjs`. They reject keys in files, `http://` addresses, hosts that aren't declared and instructions hidden in tool descriptions.
* **Review:** the Famulor team checks that the publisher owns the app, that the connector asks for no more access than it needs, and that write actions such as booking or sending ask the customer first.
* **Release:** after the merge, we add the entry to the app with the next release and comment on your pull request when it's live.

> [!NOTE]
>
> Report security problems in a connector privately to [support@famulor.io](mailto:support@famulor.io), never in a public issue.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.