CI-first spec publishing

Keep writing markdown.
We'll handle the rest.

Drop a mapping file in your repo, add one line to GitHub Actions, and every markdown file lands exactly where your team needs it — published as clean docs or agent-transformed into release notes, task summaries, and more.

Get started free How it works

Notion

ClickUp

Confluence

Notion, ClickUp & S3 available now — Confluence coming soon

How it works

Connect an integration

Place your .mdspecmap

Drop a .mdspecmap into any folder you want to sync — its location defines its scope.

Add the CI step

One line in your GitHub Actions workflow. Every push to main syncs changed specs.

Two files. Done.

Drop a .mdspecmap into any folder you want to sync — its location defines its scope and mappings apply to all subfolders automatically. Optionally assign agent templates per file to transform specs before they publish.

# docs/specs/.mdspecmap

version: 1

mappings:

- integration: s3

parent: eng-bucket

# .github/workflows/mdspec.yml

- name: Publish specs

run: npx mdspeci publish --project $${PROJECT_ID}

env:

MDSPEC_TOKEN: $${{ secrets.MDSPEC_TOKEN }}

Features

Git-native

Change detection via git diff. Only modified specs are published. Distribution files live in the repo — version-controlled and easy to manage.

Skip patterns

Exclude files with glob patterns in .mdspecmap.

One repo, any number of integrations

Map different folders to different tools — one team's specs go to ClickUp, another's to S3, all from the same repo.

Agent layer

Transform specs post-publish with built-in templates like task summaries and release notes.

Docs backup

Remove a file from the repo and it stays in the target tool. Published docs are never deleted automatically.

Team-friendly

Different teams can manage their own .mdspecmap files — separately or in a monorepo — and sync to the same destination.

Security & compliance

mdspec runs on Vercel — SOC 2 Type II certified and ISO 27001 compliant infrastructure.

SOC 2 Type II

Hosted on Vercel, which holds SOC 2 Type II certification covering security, availability, and confidentiality.

ISO 27001

Vercel's infrastructure is ISO 27001 certified, meeting the international standard for information security management.

Encrypted credentials

Integration credentials are encrypted at rest with authenticated encryption (XChaCha20-Poly1305) and keys held outside the application database — aligned with the cryptographic controls expected under SOC 2 and ISO 27001.

No content storage

Spec content is never stored outside your compliant sources. It flows directly from CI to your target tool — only metadata is retained.

Powered by Claude Haiku

Agent template transformations run on Anthropic's Claude Haiku 4.5 — fast, cost-efficient, and built on Anthropic's enterprise-grade infrastructure.

Simple pricing

Free to start. $9/mo or $100/yr for unlimited everything.

Free

1 project, 15 documents

Pro

$9/mo

Unlimited everything

Pro Annual

$100/yr

2 months free

Get started free

Keep writing markdown.We'll handle the rest.