Last updated: 2026-07-16 Status: EXPERIMENTAL / PRE-ALPHA
-
No MCP transport. The package does not start or communicate with the TypeScript MCP server (
@webflow-agent-kit/mcp). Themcpdependency was removed in the pre-alpha cleanup. -
No tool registry. There is no list of tools, groups, or schemas available in Python. The TypeScript packages (
@webflow-agent-kit/core) are the source of truth for tool definitions. -
No framework adapters. All three adapter methods (
to_openai_sdk,to_langchain,to_crewai) raiseNotImplementedError. No real conversion to any Python AI framework exists. -
No automated tests for adapter behavior. Tests only verify that unimplemented methods fail loudly and that basic auth validation works.
| Version | Status |
|---|---|
| 3.10 | Supported |
| 3.11 | Supported |
| 3.12 | Supported |
| 3.13 | Not tested |
The TypeScript MCP server starts as a subprocess. Python communicates via stdio using the MCP JSON-RPC protocol.
Pros: Reuses all 62 existing tools, single source of truth. Cons: Requires Node.js runtime, adds subprocess management complexity.
Python calls the Webflow REST API directly, duplicating tool logic.
Pros: No TypeScript dependency. Cons: Duplicates 62 tool implementations, two codebases to maintain.
The MCP server runs as a standalone HTTP server. Python calls it via requests/httpx.
Pros: Clean separation, works across machines. Cons: Requires server management, additional deployment step.
Do not install this package in production environments. All methods that would perform real work raise NotImplementedError. The only working behavior is WebflowAgentKit.from_env() which validates that a WEBFLOW_TOKEN environment variable is set.
For production use of webflow-agent-kit, install the TypeScript packages:
npm install @webflow-agent-kit/core @webflow-agent-kit/vercel-aiSee the main README for production setup instructions.