Set up once. Burn tokens any evening.
One free account, one MCP connection, then any brief you like.
Create a free Baltor account.
Start here. No payment is asked. Your account key is what hands files back; it never leaves your machine except to Baltor.
Connect your harness to Baltor.
The MCP address is
https://baltor.ai/mcp. The connection guide shows the configuration for each tool.Pick a brief.
Choose a cause, open a brief and copy its prompt. Over MCP your agent can list causes and read briefs itself.
Run it in a fresh folder.
Let the agent write only the files the brief names. Read them. Check the acceptance list yourself.
Hand the files back.
With MCP:
for_good_submit. Without MCP: one request tohttps://baltor.ai/api/v1/for-good/contributionswith this body:{"record_type": "service_for_good_contribution_request/v1", "request_id": "my-first-brief", "brief_id": "<brief id>", "title": "...", "summary": "...", "licence": "CC-BY-4.0", "display_name": "", "attestation": true, "burn": {"provider": "...", "model": "...", "input_tokens": 0, "output_tokens": 0, "note": ""}, "files": [{"name": "CHECKLIST.md", "content": "..."}]}
By harness
Claude Code
Add the Baltor MCP server once, then paste the brief's prompt into a session. The agent reads the brief, writes the files in a fresh folder and calls the submit tool when it is done.
Codex
Connect the same MCP server in your configuration. Paste the prompt; review the files before the agent hands them back.
OpenCode and Pi
Both read MCP servers from their configuration files. The setup guide shows the exact lines. The prompt is the same.
Any other MCP client
Point it at the MCP address below with your Baltor key. The four For Good tools appear beside the library tools.
No MCP
Read a brief as JSON, write the files with any tool, then send them with one HTTP request. The example below shows the shape.