Homepage update
One shared content task
Muse proposed a change
The draft and its context are ready to inspect.
Your team keeps the final say
Feedback, approval, and publishing remain human decisions.
Self-managed compatibility path for MCP-capable clients.
What Muse can do
Agent speed, without an unreviewed path to production.
01
Keep Muse in its own environment
Use the agent workspace and model behavior you already chose instead of moving drafting into another tool.
02
Give website work a destination
Route proposed copy and page changes into a GitCMS content task with their context attached.
03
Keep publishing explicit
Let Muse prepare the work while reviewers decide what is ready to reach the website.
One governed workflow
Muse proposes. Your team publishes.
The agent proposes
Research, drafts, and edits arrive as one visible content task.
People review
Your team can refine the work, leave feedback, and approve it.
GitCMS publishes
Only approved changes reach the website and its Git history.
From conversation to review
Example shown with Claude. Compatible agents use the same GitCMS task and review path.
Connect through MCP
Connect Muse to GitCMS.
This is a compatibility path for Muse clients that support authenticated remote MCP servers. GitCMS does not manage the client itself.
Remote MCP connection
Client-managed setup
- 01Confirm that your agent client accepts authenticated remote MCP servers.
- 02Add the GitCMS connector URL in the client’s MCP or tools settings.
- 03Complete the GitHub sign-in and choose the workspace you want to use.
- 04Ask the agent to list your sites, then start a content task.
Consumer Muse currently documents custom connectors through APIs and CLIs, not an arbitrary MCP URL. This GitCMS path applies only to Muse environments that expose MCP configuration.
