Request an app
- Open Agent Tools → Agent Connectors and scroll to the card Couldn’t find the tool you want?
- 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.”
- Without a GitHub account, select Send feedback instead.
What you can build
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
- Fork famulor-marketplace and copy an example from
examples/connectors/toconnectors/<your-app>/. - 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. - 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.
- Run
node scripts/validate.mjsandnode scripts/build-catalog.mjs, then open a pull request.
Submit an automation template
- Build and test the automation, then choose ⋯ → Export to download it.
- Save the file as
automation.famulor-automation.jsoninautomations/<your-template>/, next to alisting.jsonand a README. - Open a pull request.
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.
Report security problems in a connector privately to support@famulor.io, never in a public issue.