MCP in Practice: Building a Job Application Server with OAuth 2.1
Shape_Weird · reddit · 2026-07-28
The author shares insights from building a newly launched remote MCP server featuring OAuth 2.1 and Dynamic Client Registration (DCR) for automated job applications.
Technical Highlights & Challenges:
- Asynchronous Execution: autoapply is asynchronous; verification happens in a background pipeline, making it hard to express the "settling state" sensibly to AI assistants.
- Auth Config: DCR enables paste-to-install, but Google's IdP config still requires manual callback URL registration. Missing this causes a confusing split where tools/list works but connected calls return 401.
- Verification Difficulty: Form filling is nearly solved, but confirming successful submission is hard. Different ATS systems confirm differently (redirects, DOM swaps, emails, or silent drops). The tool requires independent confirmation, returning granular states (processed, applied, pending) rather than a boolean.
Related event: Developer Builds Job Application Automation MCP Server with OAuth 2.1(2 posts)→
More from coding & agent
- Ami is an open-source local agent that learns your workflow across apps — vitaelabitur · 2026-07-28
- Search API pricing looks cheap per call, but full-context queries can cost 4× more — No_Marionberry_5366 · 2026-07-28
- Agent workflows are shifting from loops to structured graphs, with AFlow beating hand-built flows — dominik_ddd · 2026-07-28
- Open-source proxy stops agent loops, caps budget, and blocks risky tool calls — Electrical-War-549 · 2026-07-28
- Chunking may matter more than embeddings in a RAG pipeline — victorialslocum · 2026-07-28
- Claude Code users want local image references for agent-driven generation workflows — Ill-Resort-2920 · 2026-07-28