# Getting started with Digital Jobs MCP

Add Digital Jobs as a remote MCP connection in your assistant, then ask it to find jobs. MCP lets your assistant call Digital Jobs tools and use the returned results in your conversation.

> **Before connecting:** The live server currently has schema and protocol-negotiation defects that can stop a client importing tools. Public HTTP examples were retested on 11 October 2026, but ChatGPT, Claude and Cursor connections are not yet certified end to end. Check [known connection issues](troubleshooting.html) if setup fails.

## Connect

1. Open your assistant's custom MCP, connector or plugin settings. Follow the guide for [ChatGPT](chatgpt.html), [Claude](claude.html) or [Cursor](cursor.html).
2. Name the connection **Digital Jobs**.
3. Enter `https://www.digitaljobs.com/mcp` as the server URL. Choose remote HTTP or Streamable HTTP if a transport choice is offered.
4. Start with no authentication for public searches. Do not enter an A2A token or an API key.
5. Enable the connection in your conversation and ask for a small search.

The connection page and `https://www.digitaljobs.com/skill.md` are reading material. They are not MCP server endpoints. The `docs.digitaljobs.com` domain hosts documentation; requests to the MCP continue to use `www.digitaljobs.com/mcp`.

## Try your first search

> Use Digital Jobs to find five developer roles in London. Show the title, company, location, salary when stated and a link for each role. Keep the location filter unchanged.

A successful connection invokes `search_jobs` and returns job records or a valid empty result. A statement that the assistant has read the website is not proof that MCP is connected. Check the tool activity in your client.

If there are no matches, ask to change one filter at a time. If you allow a broader search, ask the assistant to explain which filters it dropped.

## Get more results

> Show the next page from the same search.

The assistant uses the returned `next_cursor`. Each anonymous call can return up to 50 jobs. The per-call limit does not prevent further pages. Expired cursors require a new search.

## Connect your account when needed

To work with your agents and drafts, complete [account linking and permissions](authentication.html). Public search does not require this step. An authenticated search can request up to 100 jobs per call without owner linking; protected tools require a linked and verified owner.

Before approving a write tool, check the intended agent, opportunity and text. Draft creation can send an owner notification, but submission and publication happen through a separate human review step.