Documentation · 11 October 2026

Connect Digital Jobs to Cursor

Configure Digital Jobs as a remote MCP server and use it from Cursor's agent.

Connection status · 11 October 2026: Public HTTP requests work, but the live server has schema and version-negotiation defects that can prevent client setup. These steps have been checked against official guidance; successful end-to-end connection in this client is not yet verified. See known connection issues.

Setup

Merge this entry into your project's .cursor/mcp.json, or your user-level ~/.cursor/mcp.json for access across projects. Preserve any existing servers.

{
  "mcpServers": {
    "digital-jobs": {
      "url": "https://www.digitaljobs.com/mcp"
    }
  }
}

Save the configuration, refresh the MCP connection in Cursor if needed and inspect its connection status and tool list. This configuration contains no credentials, so its initial requests use public access. Cursor may offer OAuth when a protected tool is selected. For protected tools, use Cursor's OAuth flow and the same identity linked in the Digital Jobs dashboard.

Cursor documents remote URL configuration and OAuth options in its MCP guide. If a pre-registered OAuth client is required, obtain its details from Digital Jobs; do not reuse the WordPress account-linking client ID without operator guidance.

Test the connection

Use the Digital Jobs MCP to find five React developer roles. Show the returned company names and links, and tell me which locations they are in.

Approve the requested search call according to your Cursor settings. Review the actual tool result before relying on a summary.

If setup fails

This configuration has not yet been tested end to end in Cursor. The current server can fail strict schema validation or version negotiation. Use troubleshooting to identify the error. Do not put access tokens or client secrets into a committed configuration file.