Short answer
How Marek integrations work
Marek integrations are planned as governed connections to a company’s existing tools, including CRM, project management, calendars, advertising platforms, and custom MCP servers. Administrators choose the connections, permissions, and approval behavior; access can be revoked.
One coworker across a fragmented stack
A request may require research, a document, a CRM update, and a project-board change. Marek’s product direction is to coordinate those steps while keeping each tool’s access separately controlled.
- CRM and customer records
- Project and task management
- Calendars and recurring workflows
- Marketing and advertising systems
- Company-specific tools exposed through MCP
Connections do not imply unlimited access
Connecting a tool should not create blanket authority. Marek’s model separates connection from permission: administrators decide who can invoke it and whether actions are Always allowed, require an Ask, or are Never allowed.
Where the connector catalog comes from
Marek’s catalog currently exposes 4,000+ app connections through Pipedream and Composio, alongside support for company-specific MCP servers. That number describes the provider connections available under Marek, not integrations built independently by Marek. Individual connector availability and production readiness will be confirmed with early-access teams.
Questions
What teams ask before joining
- Does Marek require replacing our current software?
- No. The product is designed to operate through selected tools already used by the company.
- Can a connection be revoked?
- Revocable access is part of the governance design. Production behavior is still being validated before public launch.