Markdown transcript
Human-readable meeting records for skimming, quoting, review, and knowledge-base workflows.
Developer workflows
Meeting history should be inspectable, scriptable, and local.
Most developer tools work from files and clear interfaces. Meeting tools usually do not. Transcripted fixes that by saving the meeting as readable Markdown with structured frontmatter and a capture-folder layout you can search, validate, and automate against.
Why developers care
If meeting output is trapped in a cloud UI, it is hard to grep, hard to validate, and hard to build tooling around. Transcripted keeps the raw material in files you own, which makes the meeting corpus behave more like source data than like a closed SaaS artifact.
The important shift is not just local transcription. It is that the data model is useful to both humans and machines from day one.
The developer surface area
YAML frontmatter
Dates, speakers, engines, and source fields that are easier to query than a wall of prose.
Capture folders
A predictable local layout so tools can work across meetings without scanning a vendor dashboard first.
Persistent speaker identity
Cross-meeting person continuity that makes people-aware queries and scripts much more useful.
How developers plug it in
Files first
Point Claude, Cursor, Obsidian, or any file-reading tool at your local Transcripted folder.
Starter prompt
Transcripted can generate a simple prompt that tells your agent where the files live.
Read-only MCP
On supported agents, the local MCP server lets you search, recap, and read meetings or dictations.
CLI and automation
Developers can use the standalone CLI context commands or script against the same local Markdown files.
Typical developer uses
Search for every discussion of a feature flag or migration across the corpus.
Feed local meeting context into Cursor next to the codebase it relates to.
Validate artifacts and automate follow-up workflows with local CLI tooling.
Build internal scripts on top of YAML frontmatter instead of scraping vendor UIs.
FAQ
Is Transcripted open source?
Yes. Transcripted is MIT licensed and available on GitHub.
What makes Transcripted useful for developers?
It stores meetings as local artifacts developers can inspect and script against: a Markdown transcript, YAML frontmatter, and a capture-folder layout.
Can I build on top of Transcripted?
Yes. Developers can work directly from the local files, connect supported agents through the read-only MCP server, or script against the same corpus with CLI tooling.
Does Transcripted work with Claude Desktop or Cursor?
Yes. File-reading tools can use the local corpus directly, and supported agents can connect through the local read-only MCP server.
Put meeting data on the same side of the wall as the rest of your tooling.
Keep the corpus local, script against it however you want, and let agents use the same source of truth.