Job search, right inside your Claude chat.
Candidates are not starting on job boards anymore. They are starting in a chat.
Ask Claude about work and it searches live postings on joblet.ai, then hands back real openings with an interactive job card carousel. Read only, so it looks jobs up and changes nothing.
- Transport
- Streamable HTTP
- Endpoint
- POST /mcp
- Auth
- None required
01What you can ask
Just ask, in your own words.
Press a question to see which tool runs and what comes back.
Find warehouse associate jobs in Zurich
Found 3 warehouse roles in Zurich.
- Warehouse Associate · Adecco
- Logistics Operator · Randstad
- Inventory Assistant · Manpower
Rendered as job cards in the chat
02The tools
Two tools, one conversation.
Search live postings
search_jobsSearches joblet.ai by title or keyword, with optional filters, and renders the matches as a job card carousel.
What it accepts
A search term plus optional filters such as location or company. Claude pulls them out of your sentence for you.
No match returns a specific message, for example "No jobs found for ‘X’ in ‘Y’", never a generic error.
What it returns
- id
- Stable identifier, used by get_job_details
- title
- Job title as published
- company
- Hiring company or agency
- location
- City and country, or Remote
- apply_link
- Where the application is completed
They hand off to each other. search_jobs returns results carrying stable ids, and a follow-up question makes Claude call get_job_details with the right one. You never see an id.
03Setup
Connected in under a minute.
No login, no API key, nothing to configure.
Add the connector in Claude
Add a custom connector in your Claude settings using the server URL below, or find "joblet.ai" in the Connectors directory once it is listed there.
Start asking about jobs
That is the whole setup. Ask in plain language and Claude reaches for the connector when it fits the question.
https://mcp-claude.joblet.aiSpecification
Live- Server URL
- https://mcp-claude.joblet.ai
- Transport
- Streamable HTTP
- Endpoint
- POST /mcp
- Version
- v1.1
- Access
- Read only
- Authentication
- None required
- Backend timeout
- 8 seconds
04Limits
What it will not do.
Scope is a feature. These are the edges of v1.1.
Read only
It cannot apply, create an account, or save a job for you.
No sign in
Public listing data only. No account, no API key, nothing to configure.
8 second cap
Requests are time limited, so a slow query fails fast.
Specific errors
You are told whether the API failed or the search found nothing.
Only your search terms reach the joblet.ai public API. Nothing is stored beyond standard server logs, no conversation content or personal data is collected, and nothing here trains any model, ours or a third party’s.
Privacy policyQuestions
The things people ask first.
Do I need a joblet.ai account?
No. The connector reads public job listing data, so there is nothing to sign in to. You will only need an account if you choose to apply or save a job on joblet.ai itself.
Can Claude apply to jobs for me?
Not in v1.1. The connector is read only. Claude can find a role and hand you the apply link, and you complete the application yourself on the employer’s site.
Do I have to name the tools or use special syntax?
No. Ask in your own words. Claude picks between search_jobs and get_job_details based on the question, including on follow-ups such as "tell me more about the second one".
What happens to my search terms?
They are used to query the joblet.ai public API and nothing more. Nothing is stored beyond standard server logs, and no conversation content or personal data is collected. The full detail is in the AI Assistant Integrations section of our privacy policy.
Will it ever need me to log in?
A future version may add OAuth 2.0 to support account based features. If that happens, this page will be updated first and any new permissions will be requested clearly at that time.
Meet candidates where they already are.
Questions or issues with the connector, write to contactus@joblet.ai.