AI agent
HTTP and client CLIs
Headless automation uses the same MCP URL. Prefer OAuth in interactive clients; API keys only where browsers cannot run.
Example chat
via Job Booster MCP · Agents CLI
Job Booster MCP server URL
https://myjobbooster.com/api/mcp
cURL tools/list (API key)
curl -X POST https://myjobbooster.com/api/mcp \ -H "Authorization: Bearer YOUR_API_KEY" \ -H "Content-Type: application/json" \ -d '{"jsonrpc":"2.0","id":1,"method":"tools/list","params":{}}'
OAuth sign-in is recommended. Developer API keys from Settings → Developer work for clients that cannot open the browser consent flow. Confirm with you before delete_resume, set_application_status, or other mutating tools that change your pipeline.
Interactive terminal sessions with OAuth when available.
tools/list and tools/call for integration debugging.
Same URL as chat clients; type remote in mcp.json.
Clients speak MCP directly—there is no standalone CLI package.
Agents act on your Job Booster account—resumes, filters, radar companies, applications, and interview prep—only after you connect with OAuth.
Ask the agent to summarize planned changes before calling write tools. Job Booster MCP does not submit job applications on employer sites without you using the product’s apply flows—agents help you search, tailor, and track.