Storyblok MCP Server

Storyblok's own experimental server was archived, which leaves the community implementations carrying the workload. This one is organised as one module per Storyblok resource: stories, components and component folders, assets and asset folders, datasources, tags, releases, pipelines, presets, workflows and workflow stages, collaborators and space roles. A meta tool returns the full tool list at runtime, so a client discovers what is available rather than depending on a hardcoded map that drifts as modules are added. Bulk operations exist for the cases that matter in practice, publishing or deleting many stories at once. Built on FastMCP and httpx, configured through a space identifier and management token.