MCP Tool Catalog
These are the tools the MCP server exposes to AI clients. Access reflects workspace RBAC: WS member means any role in the workspace, WS editor+ means editor or owner, and Admin only means a platform admin.
| Tool | Parameters | Access | Description |
|---|---|---|---|
list_workspaces | — | All users | List workspaces the user belongs to |
list_ideas | workspace_id, status?, priority? | WS member | List ideas in a workspace |
create_idea | workspace_id, title, description?, tags? | WS member | Create a new idea |
update_idea | idea_id, status?, priority?, tags? | WS member | Update idea fields |
list_posts | workspace_id, status? | WS member | List posts with pipeline status |
get_post | post_id | WS member | Get post content and metadata |
generate_post | idea_id, prompt_id? | WS editor+ | Generate a post draft from an idea |
iterate_post | post_id, instruction | WS editor+ | AI iteration on post content |
get_pipeline_status | workspace_id | WS member | Post counts by status |
get_schedule | workspace_id, weeks? | WS member | Upcoming scheduled posts |
list_actions | workspace_id, status? | WS member | List action requests |
create_action | workspace_id, title, assignee_id, post_id? | WS editor+ | Create an action request |
list_prompts | workspace_id | WS member | List prompt templates |
list_examples | workspace_id | WS member | List example posts |
admin_list_users | status? | Admin only | List platform users |
admin_approve_user | user_id | Admin only | Approve a pending user |
Implementation
Tools are grouped by domain under mcp/src/lkwiz_mcp/tools/ (workspaces.py, ideas.py,
posts.py, genai.py, schedule.py, actions.py, prompts.py, examples.py,
admin.py). Each tool delegates to the same business logic as its REST counterpart, so
behavior stays in sync across the web app and MCP. See the project's MCP ↔ API parity
check (scripts/check_mcp_parity.py).