The Storyblok MCP Server enables your AI assistants to directly interact with your Storyblok spaces. It exposes a modular set of tools to manage Storyblok resources such as stories, components, assets, data sources, tags, releases, workflows, and more, all via the MCP framework. At runtime, the server loads a meta tool that discovers available tools and their descriptions, and each resource is handled by its own dedicated tool module for consistent, extensible access. To get started, configure your Storyblok access by supplying a management token and your space ID (via the .env file or environment variables), then run the server. The available tools let you perform CRUD operations, bulk updates, asset handling, and workflow management across the full Storyblok surface.

Prerequisites:

• Python 3.8+ installed on your system
• Access to a Storyblok space and a management access token
• Network access to reach Storyblok APIs

Installation steps:

1. Clone the repository: git clone https://github.com/Kiran1689/kiran1689-storyblok-mcp-server.git cd kiran1689-storyblok-mcp-server

2. (Optional) Create and activate a virtual environment: python -m venv venv

   Windows

   venv\Scripts\activate

   macOS/Linux

   source venv/bin/activate

3. Install runtime dependencies. If a requirements.txt is not present, install core dependencies manually based on pyproject.toml (examples shown for common related libs): pip install httpx fastapi pip install uvicorn

   Add any other dependencies listed in pyproject.toml as needed

4. Configure environment variables. Create a .env file or export variables in your session: STORYBLOK_TOKEN=your-storyblok-management-access-token STORYBLOK_SPACE_ID=your-space-id

   Optional: set environment (development|production) if the app uses it

5. Start the server: python server.py

6. Verify the server is running by hitting the meta endpoint or the MCP discovery path as documented in the README.

Notes:

• If you prefer to run with a package manager or container, appropriate adjustments to the command may be needed (not provided in this repo).

Tips and common issues:

• Ensure STORYBLOK_TOKEN has the required permissions for the actions you intend to perform (read/write).
• The .env file should be secured and not committed to version control.
• If you encounter authentication errors, double-check the token scope and space ID against your Storyblok account.
• The server uses a modular tool architecture; if you add new Storyblok resources, follow the existing tool module pattern to extend capabilities.
• For production deployments, consider running behind a reverse proxy and enabling proper TLS termination. Monitor API rate limits for Storyblok to avoid throttling.
• If the runtime cannot discover tools, ensure the server.py imports the tools module correctly and that the PYTHONPATH includes the project root.