Exports & integrations

Marca turns review feedback into work items your team already tracks. Select comments or tasks in the project's items panel, then choose how to send them.

Markdown export

Available on every plan. Produces a structured markdown brief — one section per task with the page route, CSS selector, element text, screenshot reference, and the requested change. Download it or copy it. There's also a compact Slack-style checklist format for pasting into a thread.

GitHub Issues

Available on every plan. Files a real GitHub issue per selected task.

1. In your project, open the Integrations tab and connect GitHub.
2. Provide a fine-grained personal access token with Issues: write on the target repo, plus the repo owner and repo name.
3. Marca verifies the token immediately, then Send to → GitHub Issues creates issues with the full markdown brief as the body and returns a link to each one.

Tasks already sent to GitHub are skipped on a re-send, so a double-click won't file duplicates.

Linear

Studio plan and above. Files an issue in a Linear team.

1. Open the Integrations tab and connect Linear.
2. Provide a Linear API key and the target team id (the optional team key is used as a label).
3. Send to → Linear creates issues and links back to them.

Cursor & Claude Code

Studio plan and above. These are clipboard handoffs, not API connections — there's nothing to connect.

Send to → Cursor or Send to → Claude Code copies a ready-to-paste brief: the same task detail as the markdown export, prefixed with an instruction the coding agent can act on. Paste it into Cursor's chat or the Claude Code CLI and it works through the changes.

Security

Integration tokens are encrypted at rest (AES-256-GCM) and are never returned by the API — the dashboard only shows whether a provider is connected and a non-secret label. Only workspace owners and admins can connect, rotate, or disconnect an integration.