macro: A unified workspace for your team.
What problem it solves
Teams often rely on separate tools for communication, tasks, documents, customer relationships, and other work, leaving context scattered across systems. Macro addresses this by bringing those workflows into one connected interface where linked records remain searchable and available to both people and agents.
Key features
Connected team workflows — Email, messages, docs, tasks, calls, databases, and CRM records share a backend and use bidirectional links to preserve context across surfaces.
Source: README
Agents with shared team context — Agents can work across connected workspace records, use memory, run code, create routines, and carry requests through tasks, documents, and pull requests.
Source: README
Collaborative markdown documents — Native markdown documents support live CRDT-based collaboration, version history, offline editing, and links to other workspace records.
Source: README
Unified inbox and focused messaging — A unified inbox brings together email, messages, mentions, and assigned tasks, while channel replies collapse into threads to keep technical discussions readable.
Source: README
Context-aware CRM and databases — Customer records, conversations, email, files, tasks, and calls remain connected, while customizable databases support typed columns, relations, saved views, and agent queries.
Source: README
Quick start
Copied verbatim from the project's README.
claude mcp add --transport http macro https://mcp-server.macro.com/mcpWho it may suit
This may suit teams that want communication, project tracking, documents, customer records, and agent-assisted workflows in one workspace. It may also suit developers and technical teams interested in self-hosting, MCP integrations, and agent-native collaboration.
Topics to discuss
Which connected workflows provide the greatest value for your team?
How should bidirectional links and shared memory affect workspace permissions?
What local-development or self-hosting setup would make Macro easier to try?
Written by ReadmeX AI from the project's README, source and public GitHub data; it may contain mistakes.
Read the original README https://github.com/macro-inc/macro#readme
ReadmeX opened this community for a trending project; it is not run by the project. Maintainers can claim it from the community page.
Comments
…