Auteur works with a generic MCP client
Any spec-compliant MCP client can connect to Auteur. This is the fallback path when your harness is not one of the named integrations, the agent can change; the project, process, authority, and evidence remain.
What a generic MCP client does well
A conforming MCP client speaks the open protocol Auteur exposes, without needing a harness-specific adapter. If your tool implements MCP, it can discover and call the Auteur domains you are authorized to reach.
What Auteur adds
For any MCP client, Auteur adds a persistent project that keeps its own canon and evidence; governed campaigns; production tools beyond code; and canonical receipts that verify what actually changed independently of the agent's own claim. Your MCP client stays your interface, Auteur is the amplification and accountability layer behind it.
How it connects
- Client, local stdio. A spec-compliant MCP client connects over local stdio to the Algernon MCP server.
- Client, remote. Remote reach runs only through a development gateway, a development affordance, not the commercial deployment, and not presented as a product. The supported remote path is the hosted Conductor endpoint.
- Executor. A generic client is a control surface, not a Build executor seat.
- Direct model. There is no model lane for a generic client.
Which Auteur products it reaches
Over local stdio, a generic MCP client can address the Auteur domains you are entitled to, writing and story, prep, film, game, learning, and the Build campaign system, in natural language. Reachability is not entitlement: the connection can address these domains; which you operate depends on what you hold.
What is measurable
Auteur measures the Auteur-side actions a generic client performs. It does not see the client's own session token usage, and there is no executor or direct-model lane to account for here.
Auteur never invents missing usage data; missing = unknown, never zero. No token or cost figure is ever shown for work performed outside Auteur's visibility.
What this integration does not do
- It is not a Build executor seat.
Security and authority boundary
Connecting a generic MCP client does not grant it wildcard authority over your files, spending, publication, or application changes. The connection is an interface, not a grant of authority, what a connected agent may do stays governed by Auteur, not widened by connecting it.
Current status
Current per-mode status is shown above.
Proof
No published connection evidence yet. A recorded local-stdio canary will be linked here when one exists; the general-purpose remote canary awaits the hosted Conductor endpoint. Follow the roadmap for progress.
Set it up
A spec-compliant MCP client connects over local stdio through the invited local Conductor connection:
Request Invitation, /founding-beta/?track=invite. A small, deliberately limited cohort; this starts a conversation with us, and seats, when offered, are paid.
Affiliation
Auteur is designed to connect with any spec-compliant MCP client. No partnership, endorsement, or certification is claimed, and none exists.