[bekservice]

Adds Famulor (third_party/famulor) to .cursor-plugin/marketplace.json and the README table.

Famulor builds AI assistants for phone calls, websites, and messaging. The plugin connects agents to Famulor's hosted Streamable HTTP MCP server so they can build and review voice assistants, start and analyze calls, run outbound campaigns, manage knowledge bases, and work with WhatsApp and webchat conversations in a Famulor workspace.

Components

• Hosted MCP server (third_party/famulor/mcp.json): https://app.famulor.io/mcp, auth Authorization: Bearer ${FAMULOR_API_KEY}. Same shape as brevo and github.
• Manifest (.cursor-plugin/plugin.json): Cursor 3.13.0, FAMULOR_API_KEY declared and required ("Famulor API key", created under Settings → API & MCP in app.famulor.io). Logo is 192×192, with MIT, CHANGELOG, and README like the other remote MCP integrations.
• Logo: Famulor's official cyan toggle mark, from https://www.famulor.io/images/famulor-fav.png.

Famulor documents the Bearer API key for manual and server-to-server MCP connections: https://docs.famulor.io/mcp/overview. The tool groups (assistants, calls, campaigns, messaging, telephony, knowledge, …) are described at https://docs.famulor.io/mcp/tools-and-scopes.

Testing

• node scripts/validate-plugins.mjs → All plugins validated successfully.
• node scripts/generate-pstack-harness-trees.mjs --check → up to date.
• Every ${VAR} in mcp.json is declared and required in plugin.json.
• Against the live server, using this mcp.json with a workspace key: initialize succeeds, tools/list returns 475 tools, and the read-only list_assistants call succeeds.

Notes

• The server can write, including starting outbound calls and campaigns. The README advises a narrowly scoped key and a test workspace.
• Famulor also supports MCP OAuth (DCR + PKCE). This listing uses the API key so it works in every Cursor client today. Switching to OAuth-only (like highlevel and vanta) is a follow-up once Famulor's registration endpoint accepts all three redirect URIs Cursor registers.
• The author block is set to Famulor (sales@famulor.io) since Famulor maintains this integration; the README table row matches. Happy to switch it to the usual Cursor / plugins@cursor.com block if you prefer that for third_party entries.

I maintain Famulor's integrations (BEK Service GmbH / Famulor) and can make any changes you want, such as the description wording or placement: "server".

---

Note

Low Risk
Additive third-party plugin listing and MCP config only; no changes to core marketplace or client code, with credential handling following the same Bearer-token pattern as other remote MCP plugins.

Overview
Adds Famulor as a new marketplace integration so Cursor agents can talk to Famulor’s hosted MCP at https://app.famulor.io/mcp.

The PR registers famulor in .cursor-plugin/marketplace.json and the root README plugin table, and introduces third_party/famulor/ with the usual bundle: plugin.json (Cursor 3.13.0, required write-only FAMULOR_API_KEY), mcp.json (Streamable HTTP + Authorization: Bearer ${FAMULOR_API_KEY}), plus README, CHANGELOG, LICENSE, and logo assets. Author is listed as Famulor rather than Cursor, matching the new README row.

The README documents broad toolsets (assistants, calls, campaigns, messaging, etc.) and notes that the remote server is not read-only—it can trigger real outbound calls and spend workspace balance, so users should use narrowly scoped keys.

^{Reviewed by Cursor Bugbot for commit 0fb1788. Bugbot is set up for automated code reviews on this repo. Configure here.}