In-depth architectural comparison of the Jobgpt Mcp Server and Horizun Revit MCP MCP servers. Compare execution transports, security boundaries, tool capabilities, quality scores, and ready-to-paste client installation snippets for Claude, Cursor, Windsurf, and VS Code.
At a Glance & Executive Verdict
Jobgpt Mcp Server
Workplace & Productivity · Local stdio
Quality: 60/100 (Good) | Auth: API Key required
Horizun Revit MCP
Workplace & Productivity · Remote HTTP/SSE
Quality: 53/100 (Good) | Auth: No auth required
Verdict Summary: Choose Jobgpt Mcp Server if you need specialized Workplace & Productivity tools running via a local process. Choose Horizun Revit MCP if your workspace requires Workplace & Productivity integration with remote web transport. Both servers can be configured concurrently in your client's mcpServers manifest.
Which MCP Server Should You Choose?
Choose Jobgpt Mcp Server when:
You need dedicated capabilities in the Workplace & Productivity domain.
You prefer local stdio subprocess transport architecture.
Your security boundary fits: API Key required (BYOK (Pay Provider Direct)).
MCP server for JobGPT — search jobs, auto-apply, generate tailored resumes, track applications, and find recruiters from any MCP client. 34 tools for job search, applications, resumes, and outreach.
Open-source MCP server for Autodesk Revit: typed BIM edits, families, exports and Power BI.
Jobgpt Mcp Server is categorized under Workplace & Productivity and uses a local stdio subprocess. In contrast, Horizun Revit MCP belongs to Workplace & Productivity using remote streaming HTTP/SSE transport. Select Jobgpt Mcp Server when you need capabilities focused on workplace & productivity and Horizun Revit MCP when you require tools for workplace & productivity.
Create a new job hunt with search filters and auto-apply settings
get_job_hunt
Get details of a specific job hunt
+22 more tools listed on main page
Horizun Revit MCP Tools (46)
horizun_health
Is the bridge alive, and WHICH Revit is on the other end — year, build, our own version and commit, and the document active right now (an explicit null when none is).
get_document_info
The open document, its counts and identity.
horizun_open_document
Open a model, refusing a file saved in another Revit version (opening upgrades it irreversibly) and refusing a workshared central unless asked twice.
horizun_save_document
Save, then prove it: the file's timestamp and size before and after. On a workshared model it says, loudly, that this is not a synchronize.
horizun_relinquish_all
Give back everything this user owns, and count what is still owned afterwards rather than assume zero.
horizun_capture_view
Export a view and hand the IMAGE back, so the caller can look at the model instead of only reading it.
horizun_execute_python
The execution fallback: Python against the whole API on the UI thread, stdlib included. **Enabled by default**; an explicit off in `settings.json` is respected. `preflight=true` validates permission, document, size, hash and syntax without executing; the structured `__output__` evidence contract cl…
horizun_model_scan
The census, under the honesty contract.
horizun_write_params_verified
Parameter writes, each re-read after commit.
horizun_delete_verified
Deletion with the cascade counted, `dry_run` first.