DoneState docs / Hosted MCP
Use DoneState as a remote MCP service
The owned-domain endpoint is the first-class hosted channel. OpenAI and GitHub Marketplace are additional distribution channels, not prerequisites for using the service.
Endpoint and authentication
https://donestate.proofandstate.com/mcp- Transport
- Remote HTTP MCP with the OAuth flow exposed by the service.
- Identity
- GitHub OAuth identifies the normal operator.
- Execution funding
- Each user connects their own OpenAI API key through a short-lived DoneState HTTPS settings flow.
- Repository publication
- Public repositories can use the authenticated GitHub identity; private repositories require a selected GitHub App installation.
- Tool surface
- 20 current MCP tools across credentials, maintenance, objectives, and verification.
Recommended first-session order
- 01
Authenticate
Complete the service OAuth flow before attempting repository or credential operations. - 02
Check credential status
Start withget_openai_credential_status. It is safe to call repeatedly because it never returns the secret. - 03
Connect a credential when needed
Usecreate_openai_credential_setup. Enter the API key only on the generated HTTPS page. - 04
Choose maintenance or a direct objective
Maintenance is best for selected repositories and bounded recurring findings. A direct objective is best for one explicit repository outcome. - 05
Keep the run ID
The run ID is the durable handle for status, cancellation, deletion, handoff, and verification.
Tool groups
3 tools
Credentials
Inspect, connect, replace, or delete the user-funded execution credential.
8 tools
GitHub & maintenance
GitHub App status/setup, selected repositories, discovery, findings, and PR-only repair.
5 tools
Objectives
Create, start, inspect, cancel, and delete durable repository objectives.
4 tools
Verification
Seal handoff, submit trusted evidence, or ask OpsTruth to re-observe a run.
Client compatibility
The protocol surface is client-neutral: the endpoint is not intentionally tied to one chat product. But compatibility claims should stay evidence-based. A new MCP client is a new integration until its OAuth flow, tool calls, browser handoffs, and error handling have been exercised end to end.
Continue
Maintenance workflow
Select repositories, discover work, and queue bounded repairs.
Objective workflow
Build a direct outcome with acceptance criteria and explicit authority.
MCP tool index
Every tool, every input, grouped by purpose.
Security & data
Understand secrets, access, deletion, and trust boundaries.