Pipeshub AI vs WeJob
A side-by-side look at the Pipeshub AI and WeJob MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose Pipeshub AI for developer tools work; choose WeJob for developer tools over a hosted endpoint. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
Choose Pipeshub AI when
- You need dedicated capabilities in the Developer Tools domain.
Choose WeJob when
- You need dedicated capabilities in the Developer Tools domain.
- You prefer a remote HTTP/SSE transport.
- Its auth model fits you: No auth required.
- You want tools like
search, fetch, wejob_search_jobs.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Developer Tools | Developer Tools |
| Quality signal | 52/100 · Good | 69/100 · Great |
| Install command | Not confirmed yet | Confirmed |
| Transport | — | Remote HTTP/SSE |
| Auth | Not declared | No auth required |
| Pricing | Free | Free |
| Required env vars | None listed | None listed |
| Verified owner | Community listing | Community listing |
| GitHub stars | 3,844 | 1 |
| Directory activity | 1 views 0 installs 0 upvotes | 1 views 0 installs 0 upvotes |
| Tools | Not listed | 8 |
| Full listing | View Pipeshub AI | View WeJob |
Tools & capabilities
Pipeshub AI tools
No tool names declared yet. Check the project README from the listing page.
WeJob tools 8
searchSearch public WeJob jobs, formations, and companies. Returns ids usable with fetch.fetchFetch a public WeJob item by id. Supported id prefixes: job:, formation:, company:.wejob_search_jobsSearch public active WeJob job offers.wejob_get_jobFetch one public active WeJob job offer by public id (raw id or the job:<id> returned by search/fetch).wejob_search_formationsSearch public active WeJob formations.wejob_get_formationFetch one public active WeJob formation by public id (raw id or the formation:<id> returned by search/fetch).wejob_search_companiesSearch public WeJob company profiles.wejob_get_companyFetch one public WeJob company profile by public id (raw id or the company:<id> returned by search/fetch).
Ready-to-paste client configs
Paste either block (or both) into your client config, e.g. claude_desktop_config.json or ~/.cursor/mcp.json. We only show a config when the install command is confirmed.
Pipeshub AI
No confirmed install command for Pipeshub AI yet — follow the setup steps linked from its listing page rather than a guessed package name.
WeJob
{
"mcpServers": {
"wejob": {
"url": "https://mcp.wejob.ch/mcp"
}
}
}
Frequently asked questions
Pipeshub AI is categorized under Developer Tools and uses an install path we have not confirmed yet. WeJob belongs to Developer Tools and uses a remote HTTP/SSE transport. Pick Pipeshub AI for developer tools work and WeJob for developer tools.
Copy the mcpServers block from the config section on this page into your client's config (for example claude_desktop_config.json or ~/.cursor/mcp.json), then fully restart the client. Pipeshub AI has no confirmed install command yet — follow its own setup instructions.
Pipeshub AI is listed as free. WeJob is listed as free. Auth: no auth required. If a server needs environment variables such as API keys, define them under the env key in your client's MCP config.
Yes. MCP clients support multiple servers: add pipeshub-ai and wejob as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Pipeshub AI has a quality signal of 52/100 (Good) with 1 views, 0 installs and 3,844 GitHub stars. WeJob has 69/100 (Great) with 1 views, 0 installs and 1 GitHub stars.