CorePHP Agentic
agentic
Work plans, agent sessions, and content generation
About
and generate content through an AI pipeline. Plans survive context limits
and enable collaboration between agents across sessions.
Use when
- • Working on a multi-phase project that needs structure
- • Need to preserve context across sessions
- • Handing off work to another agent
- • Want to track progress on a long-running task
- • Need to verify previous work before continuing
- • Storing shared state between sessions
Don't use when
- • Simple one-off tasks that fit in a single session
- • Quick questions that don't need tracking
Connection
Call tools on this server via HTTP:
curl -X POST https://mcp.lthn.ai/tools/call \
-H "Authorization: Bearer YOUR_API_KEY" \
-H "Content-Type: application/json" \
-d '{
"server": "agentic",
"tool": "plan_create",
"arguments": {}
}'
Tools (29)
plan_create
Create a new work plan with phases and tasks
Example prompts:
- "Create a plan for implementing user authentication"
- "Set up a refactoring plan with 3 phases"
- "Make a plan to migrate the database schema"
Parameters
Plan title
URL-friendly slug (auto-generated if not provided)
Brief description of the plan
Background context and goals
Array of phase objects with name, description, and tasks
Set plan status to active immediately (default false)
plan_get
Get a plan with all phases, progress, and state
Example prompts:
- "Show me the auth-migration plan"
- "What's the current state of the refactor?"
- "Get details on the database plan"
Parameters
Plan slug identifier
Include workspace state in response (default false)
plan_list
List all plans, optionally filtered by status
Example prompts:
- "What plans do we have?"
- "Show me all active plans"
- "List completed plans"
Parameters
Filter by status
Include archived plans (default false)
plan_update_status
Update plan status
Example prompts:
- "Mark the auth plan as completed"
- "Archive the old migration plan"
- "Activate the new feature plan"
Parameters
Plan slug identifier
New status
plan_archive
Archive a completed or abandoned plan
Parameters
Plan slug identifier
Reason for archiving
phase_get
Get details of a specific phase
Parameters
Plan slug identifier
Phase order number or name
phase_update_status
Update a phase status - start, complete, block, or skip
Example prompts:
- "Start phase 2 of the migration"
- "Mark the testing phase as complete"
- "Block phase 3, waiting on API access"
Parameters
Plan slug identifier
Phase order number or name
New status
Optional notes about the status change
phase_add_checkpoint
Add a checkpoint note to a phase
Parameters
Checkpoint note
Additional context data
task_toggle
Toggle a task completion status
Parameters
Phase order number or name
Task index (0-based)
task_update
Update task details (status, notes)
Parameters
Task notes
session_start
Start a new agent session, optionally linked to a plan
Example prompts:
- "Start a session for the auth-migration plan"
- "Begin working on the refactor"
Parameters
Plan slug to link session to (optional)
Agent type for tracking
Initial session context
session_log
Log an action to the current session
Parameters
Additional data to log
session_artifact
Log a file artifact (created, modified, or deleted)
Parameters
File path
What happened to the file
Description of changes
session_handoff
Prepare session for handoff to another agent
Example prompts:
- "Hand off to the next agent"
- "Prepare for context switch"
- "Save state for resumption"
Parameters
Summary of work done
Recommended next steps
Any blockers encountered
Context to pass to next agent
session_end
End the current session
Parameters
Final session status
Final summary
state_set
Store a value in workspace state - persists across sessions
Example prompts:
- "Save the database schema decisions"
- "Store the API endpoints we found"
- "Remember the test results"
Parameters
State key
Value to store
Category for organisation
state_get
Retrieve a value from workspace state
Parameters
state_list
List all state keys for a plan
Parameters
Filter by category
template_list
List available plan templates
Parameters
Filter by category
template_preview
Preview a template with variables
Parameters
Template name/slug
Variable values for the template
template_create_plan
Create a new plan from a template
Parameters
Template name/slug
Variable values for the template
Custom slug for the plan
content_status
Get content generation pipeline status
Example prompts:
- "What's the content generation status?"
- "Are the AI providers configured?"
content_brief_create
Create a content brief for AI generation
Example prompts:
- "Create a help article about setting up QR codes"
- "Write a blog post about analytics best practices"
Parameters
Content title
Type of content
Service context
SEO keywords to include
Target word count (default 800)
Brief description of what to write
Target audience level
Link to an existing plan
content_brief_list
List content briefs with optional status filter
Parameters
Filter by status
Maximum results (default 20)
content_brief_get
Get details of a specific content brief including generated content
Parameters
Brief ID
content_generate
Generate content for a brief using AI pipeline
Example prompts:
- "Generate content for brief 42"
- "Run the full pipeline for the QR codes article"
Parameters
Brief ID to generate content for
Generation mode (draft=Gemini only, refine=Claude only, full=both)
Run synchronously (wait for result) vs queue for async
content_batch_generate
Queue multiple briefs for batch content generation
Parameters
Maximum briefs to process (default 5)
Generation mode
content_from_plan
Create content briefs from plan tasks and queue for generation
Example prompts:
- "Generate help articles from the biohost-docs plan"
- "Create content from the API documentation plan tasks"
Parameters
Plan slug to generate content from
Type of content to generate
Service context
Maximum briefs to create (default 5)
Target word count per article
content_usage_stats
Get AI usage statistics (tokens, costs)
Example prompts:
- "How much have we spent on AI this month?"
- "Show me content generation usage stats"
Parameters
Time period for stats
Resources (5)
plans://all
List of all work plans
plans://{slug}
Full plan as markdown
plans://{slug}/phases/{n}
Phase tasks as checklist
plans://{slug}/state/{key}
Specific state value
sessions://{id}/context
Session handoff context
Workflows (3)
Structured Project
Full workflow for a multi-phase project
- plan_create — Define phases and tasks upfront
- session_start — Begin tracking work
- phase_update_status — Start first phase
- Work on tasks — Complete tasks, use task_toggle
- phase_update_status — Mark phase complete
- Repeat for each phase
- plan_update_status — Mark plan done
Multi-Agent Handoff
Pass work between agents
- session_start — Agent A starts
- Work on phases — Make progress
- session_handoff — Prepare handoff notes
- session_start — Agent B resumes
- Continue work — Pick up where left off
Context Recovery
Resume after context limit
- plan_get — Get previous context
- session_start — Start new session
- Continue — Pick up from checkpoint