4 guides
netweft is four Cloudflare Workers over one D1 database: static marketing and dashboard sites, a Hono API with Workflows and a cron, and an analytics relay. Six decisions shaped it: a provider port, reserve-then-settle credits, stored snapshots, one-statement D1 guards, a read-only MCP surface and no free tier.
Start with whoami for the workspace and plan, list_projects to find the domain, get_project_overview for counts and the latest audit, then get_rank_trend or get_keyword_rank_history for what moved. Read get_credit_balance before suggesting paid work. Every call reads stored rows and spends nothing.
Because every netweft MCP tool is read-only over rows already stored — none of them writes, crawls or spends a credit — a scope cannot withhold a capability, only a subject. The useful one is billing: it is how a key handed to an outside integration is stopped from reading the workspace's balance and plan.
netweft exposes MCP at POST /mcp under an API key, alongside an OpenAPI 3.1 document for the whole HTTP API. An agent reads a workspace's stored audits, keywords, rankings and project overview, and reading costs no credits because the credits were spent when the observation was made.
May we set cookies to see how netweft is used? Session recordings never capture what you type. Nothing is stored until you answer, and declining still counts the visit, without a cookie. Privacy