ENDPOINT 1
https://www.lexgo.be/mcp
MCP server metadata
- Name
- lexgo-jobs
- Version
- 1.1.0
Use search_jobs to shortlist. Call get_job before recommending a vacancy; list payloads have no description. Give the candidate click_url (it is the LexGO page with tracking). url is the untagged canonical page; get_job/get_event accept either. Do not apply on their behalf. Do not invent employer emails or ATS URLs; this API does not include them.
Known tools 6
list_functionsList LexGO job function names (lawyer, in-house counsel, paralegal, notary, …) for use as function_id filters.
Inferred read-onlylist_taxonomiesList function, discipline, region, and work-environment ids plus experience, contract, and work-arrangement enums.
Inferred read-onlyget_eventFetch one upcoming LexGO event by integer id, id-slug, url, or click_url.
Inferred read-onlyCONNECT WITH APPROVAL
Client installation
Review this server and its permissions before adding it. Secret placeholders must be set locally.
Codex
~/.codex/config.toml
[mcp_servers.lexgo-jobs]
url = "https://www.lexgo.be/mcp"
enabled = true
Claude Code
.mcp.json
{
"mcpServers": {
"lexgo-jobs": {
"type": "http",
"url": "https://www.lexgo.be/mcp"
}
}
}
Claude Desktop
Settings → Connectors → Add custom connector
Name: lexgo-jobs
Remote MCP URL: https://www.lexgo.be/mcp
Add this remote URL as a custom connector in Claude Desktop. Availability depends on the user plan and workspace policy.
Cursor
.cursor/mcp.json
{
"mcpServers": {
"lexgo-jobs": {
"url": "https://www.lexgo.be/mcp"
}
}
}
Visual Studio Code
.vscode/mcp.json
Add to Visual Studio Code{
"servers": {
"lexgo-jobs": {
"type": "http",
"url": "https://www.lexgo.be/mcp"
}
}
}
Generic MCP
Client-specific MCP configuration
{
"name": "lexgo-jobs",
"transport": "streamable-http",
"url": "https://www.lexgo.be/mcp"
}
MCP Inspector
Run the official MCP Inspector locally and enter the indexed Streamable HTTP endpoint.
TRUST AND VERIFICATION EVIDENCE
Loading Trust v2 evidence…
Checking the associated registrable domain. The BuiltWith key remains server-side.
Evidence is source-attributed and does not guarantee that a third-party server is safe. Risk labels are conservative metadata heuristics.