
Chasa
io.github.docracy1Published by GitHub account docracy1v1.0.0Updated Oct 24, 2026
AI invoice follow-up emails for freelancers. Draft-only, never sends for you.
Overview
Drafts AI follow-up emails for overdue freelance invoices, with tone escalating by days late; it never sends anything for you.
- What you can do
- Draft chase emails for unpaid invoices, with tone escalating from friendly to firm to direct as days overdue grow
- List and reuse copy-paste email templates
- Draft follow-ups only — the assistant produces text you copy into Gmail, Outlook or Apple Mail
- Read-only tools are public; drafting requires a session or API key
- When to use it
- Useful for freelancers and small studios who want help wording payment reminders for late invoices without handing over sending rights. Best when you want a draft in the right tone for how overdue an invoice is.
- Requirements
- Remote MCP endpoint at api.chasa.io (legacy host redirects to docstoc). Read-only tools are public; the draft tool needs a signed-in session or an API key. Free plan allows 5 AI drafts per month; paid plans are billed monthly.
Installation
In SourceWeft
- Open Chasa in the dashboard and add it to a workspace.
- Enable the server for the chats that should use its tools.
Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.
Use with an agent
Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.
Read https://sourceweft.com/mcp/io.github.docracy1%2Fchasa/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.Other MCP clients
Add this to your client's mcpServers config.
{
"mcpServers": {
"chasa": {
"type": "http",
"url": "https://api.chasa.io/mcp"
}
}
}README
docstoc
Paste your unpaid invoices. Get the follow-up email already written, in the right tone for how late it is.
docstoc never emails your clients for you — it drafts follow-ups you copy into Gmail, Outlook, or Apple Mail. Tone escalates with days overdue (friendly → firm → direct).
Live URLs
Worker PUBLIC_APP_URL is https://docstoc.io (magic links, OAuth callbacks, Stripe return URLs, digest links).
Legacy chasa.io / api.chasa.io 301 to docstoc (Pages _middleware.ts + worker redirect). See scripts/oauth-redirect-uris.md for provider console URIs.
Go-live checklist
- Attach
docstoc.ioon Cloudflare Pages projectchasaand wait for Active. www.docstoc.io→ apex: handled byapps/web/functions/_middleware.ts(redeploy web).chasa.io/www.chasa.io→docstoc.io: same middleware.api.chasa.io→api.docstoc.io: worker middleware inapps/worker/src/lib/legacyHostRedirect.ts.- Register OAuth redirect URIs on
api.docstoc.io— seescripts/oauth-redirect-uris.md. - Optional DMARC:
./scripts/dmarc-remove-rua.sh(removesrua=from_dmarc.docstoc.io). - Run
./scripts/go-live-verify.sh.
The order does not matter: browser-facing links are built from the origin the request came in on (see “App origin resolution” below), so pages.dev and chasa.io both keep working whichever is deployed first.
App origin resolution
Magic links, post-login redirects, Stripe return URLs and team invites use the origin the user is actually on, not PUBLIC_APP_URL. The Pages /api proxy forwards it as X-Docstoc-App-Origin, and the worker honours it only if it matches lib/appUrl.ts's allowlist (PUBLIC_APP_URL, docstoc.io, www.docstoc.io, legacy chasa.io hosts, *.pages.dev project/preview hosts, localhost). This keeps preview deploys self-contained and makes the domain cutover zero-downtime.
Requests that arrive without a trusted origin — provider OAuth callbacks hitting api.docstoc.io directly, and the digest cron — still fall back to PUBLIC_APP_URL.
Product specs
Plans & pricing
Stripe price IDs live in apps/worker/wrangler.toml as STRIPE_PRICE_SOLO (maps to Pro), STRIPE_PRICE_PRO / STRIPE_PRICE_ENTERPRISE (map to Business; non-secret). Billing portal and webhooks update accounts.plan and is_paid.
Feature matrix (by plan)
Workspace roles: owner is always admin. Invited members can use Pro+ features; admin-only actions: branding, webhooks, connector OAuth connect/import, API key CRUD, team invites.
App routes (/app/*)
All app routes except /login and /admin require a session. Unauthenticated users redirect to /login. SPA analytics require cookie consent (GDPR).
i18n (EN + ES)
Same path as Docracy: lightweight catalogs in apps/web/app/src/lib/i18n/ (no i18next). LocaleProvider + EN|ES switcher on login, sidebar, and More sheet. P1 covers login / shell / welcome; expand catalogs for the rest of the app next. Preference stored as chasa_locale. Marketing HTML stays English until a later pass.
Marketing & SEO (static HTML in apps/web/public/)
- Homepage with pricing, FAQ JSON-LD, competitor comparison
- SEO landing pages:
/invoice-follow-up,/payment-reminder,/overdue-invoice,/chase-invoices,/freelancer-invoice-follow-up /features/(index, AI tone, templates),/docs/,/ai,/about/blog/(3 articles + dynamicpost.html)/free-templates/— 15 generated template pages + index- Legal:
/privacy,/terms,/imprint sitemap.xml,robots.txt,404.html, cookie consent, scroll-depth analytics- Self-hosted fonts (no Google Fonts); enforcing CSP via
_headers
Regenerate free templates after editing apps/web/scripts/generate-free-templates.mjs:
Architecture
Monorepo (npm workspaces):
Data: Cloudflare D1 (chasa-db). OAuth tokens encrypted at rest (AES-GCM, TOKEN_SECRET). Sessions in sessions table; magic links single-use (atomic consume).
AI: Cloudflare Workers AI (@cf/meta/llama-3.1-8b-instruct-fp8). Prompts wrap user content in delimiters to reduce injection.
API surface (worker)
Security & compliance (implemented)
- Free-tier quota: 5 AI drafts/month enforced in D1 (
ai_usage), not client-side - Rate limits: AI drafts, MCP, analytics, admin login (D1 buckets)
- Turnstile: fail-closed in production HTTPS when secret is set; 60s magic-link cooldown per email
- HKDF token purposes: separate keys for session, magic-link, API key, admin, invite, OAuth state, webhook signing (legacy hash fallback on lookup)
- Session rotation: prior sessions invalidated on magic-link login; admin sessions cleared on admin login
- Session cleanup: daily cron purges expired sessions, magic links, rate-limit buckets
- RBAC: workspace admin for branding, webhooks, connector OAuth, API keys, team invites
- Input validation: Zod schemas on all JSON API routes (auth, emails, clients, team, webhooks, billing, admin, MCP draft args)
- Stripe webhooks: event-id deduplication (
stripe_events) - Outbound webhooks:
X-Chasa-Signature: sha256=…HMAC - Click tracking: redirects only to URLs stored when the tracked email was created
- Webhook URLs: SSRF checks (no localhost / private IPs)
- OAuth state: timing-safe HMAC compare
- CSP: enforcing policy on Pages with a nonce per page instead of
'unsafe-inline'(apps/web/functions/lib/csp.ts, applied infunctions/_middleware.ts);report-uri→/api/csp-report. The API worker sends the same header set (apps/worker/src/lib/securityHeaders.ts). - GDPR: cookie consent gates SPA analytics; no visitor IDs on page views (aggregate only)
- Secrets: never committed —
wrangler secret put …
Local development
Without RESEND_API_KEY, magic links log to the worker console — copy the URL into your browser.
Quality checks
CI (.github/workflows/ci.yml) runs lint → test → static HTML validation → typecheck on every PR; auto-deploys worker + web on push to main when CLOUDFLARE_API_TOKEN is set.
Deploy manually
The Google step (apps/web/scripts/gsc-sitemap.mjs) needs the service account key at
~/.config/docstoc/gsc-service-account.json (never in the repo) and the service account as a Full user of the
docstoc.io Search Console property. Without the key it prints a note and exits 0.
After schema changes:
Migrations 0001–0011 include plans, admin/analytics, branding, webhooks, API keys, cloud connectors, clients/aging, parity features, and security hardening (rate limits, AI usage, Stripe idempotency, tracking link allowlist).
Cloudflare Turnstile (bot protection)
Protects /api/auth/request and admin login.
- Cloudflare Dashboard → Turnstile → Add widget
- Hostnames:
chasa-71s.pages.dev,chasa.io,localhost - Site key →
TURNSTILE_SITE_KEYinwrangler.toml[vars] - Secret →
wrangler secret put TURNSTILE_SECRET_KEY - Redeploy worker. Login UI reads config from
GET /api/auth/config.
Local / without keys: verification bypassed with console warning. Test keys:
One-time cloud setup
-
cd apps/worker && wrangler d1 create chasa-db— pastedatabase_idintowrangler.toml -
wrangler d1 migrations apply chasa-db --remote -
Stripe (test mode first): create two recurring Prices (Pro $14.99, Business $39.99). Copy
price_…IDs intowrangler.toml:STRIPE_PRICE_SOLO,STRIPE_PRICE_PRO,STRIPE_PRICE_ENTERPRISE
-
wrangler secret put TOKEN_SECRET—openssl rand -hex 32 -
wrangler secret put STRIPE_SECRET_KEY(test key first) -
Stripe webhook →
https://api.chasa.io/api/billing/webhook— events:checkout.session.completed,customer.subscription.deleted→wrangler secret put STRIPE_WEBHOOK_SECRET -
wrangler secret put RESEND_API_KEY— verify sending domain in Resend -
Turnstile — see above
-
wrangler secret put ADMIN_PASSWORD— for/app/admin9a. AI Document Generator (optional, public marketing tool): Google AI Studio → create a free API key →wrangler secret put GEMINI_API_KEY. Free tier is rate-limited; the worker also enforces its own per-IP limit + Turnstile. Seeapps/worker/src/lib/geminiDocGen.ts. -
Cloud storage OAuth (optional, Pro+):
Google Sign-In redirect:
https://api.docstoc.io/api/auth/google/callbackStep-by-step for each provider:
scripts/connectors-docstoc-setup.md -
QuickBooks Online + Xero (optional, Pro+):
See
scripts/connectors-docstoc-setup.mdfor console steps. -
Cloudflare Pages project
chasa+ custom domainchasa.io; Worker custom domainapi.chasa.io -
Switch to Stripe live keys/prices/webhook only after end-to-end test-mode smoke test
Local secrets (apps/worker/.dev.vars, gitignored)
Stripe CLI for local webhooks:
Staging environment
Uses separate D1 (chasa-db-staging) — create and paste ID in wrangler.toml [env.staging].
SEO launch checklist
Automated (build)
generate-seo.mjs runs on every npm run build and writes:
sitemap.xml— all public pages (marketing, templates, blog)robots.txt— crawl rules + sitemap URLblog/feed.xml— RSS for blog posts{indexnow-key}.txt— IndexNow key file for Bing/Yandex- Verification meta on
index.html/ai.htmlwhen env vars are set (see below)
Press kit at /press — logos, boilerplate, suggested anchor text for backlinks.
Google Search Console (one-time)
-
Add property
https://chasa.ioat Search Console -
Choose HTML tag verification → copy the
content="…"value -
Rebuild with the token:
Or use DNS TXT in Cloudflare (no rebuild needed).
-
Submit sitemap:
https://chasa.io/sitemap.xml -
URL Inspection on
/,/app/,/payment-reminder,/free-templates/
Optional Bing: BING_SITE_VERIFICATION=… same as Google.
After deploy, ping IndexNow (Bing):
Backlinks (founder — use /press)
Site-side done: social links + sameAs schema on all pages, internal links from blog → landing pages, RSS + llms.txt.
Still manual (copy from press kit):
- LinkedIn company page — website field + launch post linking to
/app/or a blog article - X @DocstocHQ — pin launch post
- Product Hunt / Indie Hackers when ready
- RELACON GmbH website cross-link to
chasa.io - 3–5 freelancer communities — link to
/blog/articles or/free-templates/, not just homepage - Email signature with
chasa.io
Entity
docstoc is a product of RELACON GmbH, Vienna, Austria. See /imprint and /privacy.
Contact: [email protected]
Source: README.md at commit 5325584
Tools
0Version history
1- v1.0.0LatestSep 16, 2026
Score
40% of the applicable checks met
How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.
- Reached in the last 30 daysRequired25 pts
Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.
- Auth declaredRequired10 pts
Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.
- Tools listed15 pts
Answer tools/list without a credential, or ship a package that starts in a sandbox without one.
- DescriptionRequired15 pts
- Logo10 pts
- Documentation15 pts
- License10 pts
Declare a license in the repository or the registry entry.