Connect Cursor to GreenHired
Add the GreenHired MCP server to Cursor with a few lines in mcp.json, sign in with OAuth or send an API key header, and use GreenHired jobs in your editor.
#Add the server
Cursor reads MCP servers from .cursor/mcp.json in a project, or ~/.cursor/mcp.json for all projects. Add GreenHired with its address:
{
"mcpServers": {
"greenhired": {
"url": "https://mcp.greenhired.com/mcp"
}
}
} Cursor supports OAuth for servers that need it, with PKCE and dynamic registration, which GreenHired supports. Open Cursor's MCP settings and sign in with GreenHired when asked, then choose permissions on the consent page.
#Or use an API key
For the three job search tools only, send a ghk_ key as a header. Cursor can read it from an environment variable:
{
"mcpServers": {
"greenhired-jobs": {
"url": "https://mcp.greenhired.com/mcp",
"headers": { "Authorization": "Bearer ${env:GREENHIRED_API_KEY}" }
}
}
} These details are from Cursor's documentation at cursor.com/docs/context/mcp, read on 21 November 2026. The file format and settings can change, so check it if something differs.
#Frequently asked questions
- Where do I find the sign-in prompt?
- In Cursor's MCP settings, where the server shows that it needs authentication. Cursor's documentation does not say exactly when it prompts, so look there first.
- Should I use a project file or the global one?
- Use the global file for your own account. Use a project file only for a key-based setup you are happy to share, and keep the key itself in an environment variable.
- Which tools will I get?
- With sign-in: your account tools for the permissions you ticked, plus the three job search tools. With a key header: the three job search tools. See Tools.
Was this page helpful?