ContentMaschine
ai.contentmaschinePublished by contentmaschine.aiOfficial publisherv1.1.0Updated Oct 24, 2026
AI image, video, audio and text tools for creators. Pay per use with credits.
Overview
ContentMaschine is a remote MCP server giving assistants AI image, video, audio and text creation tools for creators, billed per use with credits.
- What you can do
- Generate and work with AI-created media and text: images, video, audio and written content for creators.
- Tools are not listed in the manifest, so the exact set of operations is not documented here.
- Access is tied to a ContentMaschine account or API key, which also tracks credit usage.
- When to use it
- Useful when you want an assistant to produce creator-oriented media or text assets through a hosted service, and you are comfortable paying per use with credits rather than running models locally.
- Requirements
- A remote streamable HTTP endpoint at contentmaschine.ai; no local package or runtime is needed. Authentication is required via the Authorization header: either OAuth sign-in with a ContentMaschine account or a Bearer API key (sk-cm-...) from the provider's dashboard. A funded credit balance is implied by the pay-per-use model.
Installation
In SourceWeft
- Open ContentMaschine in the dashboard and add it to a workspace.
- Connect the required credentials. They are stored privately and never shown on public pages.
- Enable the server for the chats that should use its tools.
Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.
Use with an agent
Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.
Read https://sourceweft.com/mcp/ai.contentmaschine%2Fcontentmaschine/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.Other MCP clients
Add this to your client's mcpServers config. The client completes OAuth sign-in on first connect.
{
"mcpServers": {
"contentmaschine": {
"type": "http",
"url": "https://contentmaschine.ai/api/mcp"
}
}
}Tools
0Version history
2- v1.1.0LatestOct 1, 2026
- v1.0.0Sep 30, 2026
Score
67% of the applicable checks met
How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.
- Reached in the last 30 daysRequired25 pts
- Auth declaredRequired10 pts
- Tools listed15 pts
Answer tools/list without a credential, or ship a package that starts in a sandbox without one.
- DescriptionRequired15 pts
- Logo10 pts
- Documentation15 pts
Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.
- LicenseNot applicable
A hosted service is used under its provider's terms, so no license is expected here. This check is left out of the percentage.