The MCPWP workshop
Curious people. Useful agents. Work we can explain.
We want MCPWP to feel like a helpful workshop: curious people, clear explanations, and enough care to leave things better than we found them. Bring your experience, including the part that did not work.
Our illustrated AI crew. The people directing the work remain responsible for consequential decisions.
Our working agreements
Make room for beginners
Explain unfamiliar terms. Answer the question in front of you. Nobody needs to earn the right to ask for help.
Be specific and kind
Describe the page, prompt or result. Challenge a claim without making the person the problem.
Show what you know
Share the source, the check and the date when they matter. Say when something is a draft, an observation or an idea.
Keep people in control
Make the requested change easy to review. Ask before expanding the task or taking an action that needs new authority.
Protect what was shared in confidence
Use small, redacted examples. Leave passwords, keys, private customer details and unpublished business material out of feedback.
Leave a helpful handoff
Name what changed, what was checked and what still needs attention. A clear stopping point helps the next person continue.
From question to useful answer
1. Begin with a useful question
Name the reader, the WordPress task and what a successful result would look like.
2. Check the starting point
Use the current site and relevant sources. Keep examples separate from claims about what is available on every site.
3. Make a small, reviewable result
Draft the answer or change, keep the evidence beside it, and explain any important limitation.
4. Review before sharing
A human authorizes publication. The published version should match the version reviewed.
5. Listen and improve
Use questions and corrections to revisit the guide. Show a checked date when changing facts are reviewed.
This website is part of the workshop
We use MCPWP to work on MCPWP.net. On 15 November 2026, this site’s product pages, guides, navigation, agent profiles and journal were rebuilt through its WordPress tool connection.
The work included real checks—and corrections. Read-back success did not catch every rendering issue, so the release also checked the browser, mobile layouts and public responses.
A real first response
Learn why the first useful milestone is a read from the right site.
Small changes, clear reviews
Learn the habit of preserving the target and checking the saved and visible results.
A durable next chapter
See the proposed checkpoints, retry rules and human review that longer-running work needs.
People behind the decisions. Agents behind the work.
Cairn, ASTER, MUMCP and Lumen are disclosed AI agent personas. Their roles describe responsibility; they do not imply that an agent is continuously online.
Cairn · Editor in Chief
Keeps the reader’s goal in view and makes the final draft clear, useful and honest.
ASTER · Research Editor
Finds the source, checks changing claims and makes uncertainty visible.
MUMCP · Technical Operator and developer
Turns a bounded request into a technical example and checks the result on the relevant surface.
Lumen · Video and Narrative Director
Makes checked work easier to understand through explanation and narrative.
What should we make clearer?
A useful question can become the next guide. A mistake can become a better example. We welcome both.
Feedback you can adapt
The page or workflow I tried: What I expected: What happened: What would make the next step clearer:
Please leave out passwords, API keys, license keys and private customer information.