# hirly MCP server

Use [hirly](https://hirly.me/ai-assistants?utm_source=github&utm_medium=mcp&utm_campaign=hirly-mcp) from your AI assistant. Once connected, the assistant can read the jobs hirly matched to your resume, tailor a resume for one of them, and — only if you allow it, and only after you confirm the job in the chat — ask hirly to apply.

| | |
| --- | --- |
| **Server URL** | `https://mcp.hirly.me/mcp` |
| **Transport** | Streamable HTTP (remote; nothing to install) |
| **Sign-in** | OAuth, with your hirly account |
| **Tools** | 9 |
| **Docs** | [hirly.me/ai-assistants](https://hirly.me/ai-assistants?utm_source=github&utm_medium=mcp&utm_campaign=hirly-mcp) |

This repository holds the server's public documentation and its [MCP Registry](https://registry.modelcontextprotocol.io) entry (`server.json`). The server itself is hosted by hirly; there is no code to run here.

## What you need

- A hirly account. You sign in to it when the assistant connects.
- A paid hirly plan to read your matched jobs and to apply.

## Connect

### Claude

hirly is in Claude's connectors directory: open the directory, find hirly and connect it. Or add a custom connector with the server URL above.

### ChatGPT

hirly is not in ChatGPT's plugin directory yet, so for now it is added by hand:

1. In ChatGPT, open Settings, then Security and login, and turn on Developer mode.
2. Open Plugins, press the plus button and choose "Create app".
3. Enter the server URL above, and choose OAuth for Authentication.
4. Tick the box acknowledging the risk of adding a custom app, and create it.
5. Approve the connection on hirly's consent screen.

### Any other client that supports remote MCP servers

Add a remote MCP server with the URL `https://mcp.hirly.me/mcp` and sign in with your hirly account when asked.

### Clients that only support local (stdio) servers

Bridge to the remote server with [`mcp-remote`](https://www.npmjs.com/package/mcp-remote), which opens the hirly sign-in in your browser:

```json
{
  "mcpServers": {
    "hirly": {
      "command": "npx",
      "args": ["-y", "mcp-remote", "https://mcp.hirly.me/mcp"]
    }
  }
}
```

### Then, in any assistant

1. Sign in with your hirly account when asked. hirly shows what the assistant will be able to do.
2. Choose whether it may start applications for you. This is off unless you tick it, and you can change it later in hirly under Connected assistants.
3. Press Allow, then ask for your best new job matches.

## Tools

| Tool | Title | What it does | Changes anything? |
| --- | --- | --- | --- |
| `get_matches` | Get matched jobs | Lists the next jobs hirly matched to your resume that you have not acted on yet, best first. | No |
| `get_job` | Get job details | Gives your assistant one job's full posting, how your resume meets its requirements, and the hiring contact when hirly can find one. | No |
| `save_resume` | Save a résumé version | Saves a resume your assistant tailored as a new version in your hirly account. Your main resume changes only if you ask. | Yes |
| `record_application` | Record an application | Marks a job as applied in hirly — after you confirm you sent it — with the resume version you used. | Yes |
| `get_profile` | Get hirly profile | Shows your plan, whether your profile is set up, and a short summary of your main resume. | No |
| `get_pending_questions` | Get questions waiting on the user | Lists the applications that are paused because the employer's form asked something only you can answer, with the questions. | No |
| `answer_questions` | Answer an application's questions | Sends the answers you give in the chat, so hirly can finish the application. Only if you allowed applying. | Yes |
| `submit_application` | Apply to a job for the user | Starts hirly applying to one job for you, after you confirm that job in the chat. Only if you allowed applying. | Yes |
| `get_application_status` | Get an application's status | Says where an application stands: queued, applying, waiting for your answers, applied, or stopped and why. | No |

## How applying works

- Applying is off by default. You turn it on for an assistant on hirly's consent screen, and can turn it off again under Connected assistants.
- Before hirly sends an application, the assistant names the job and the company and asks you. hirly starts the application only after you say yes to that job.
- If the employer's form asks something only you can answer — work authorization, notice period, salary — the application waits, and the assistant asks you.
- hirly does not sign in to an employer's site for you or get past a CAPTCHA.

## What an assistant can and cannot reach

**Reads:** your matched jobs and their postings; your plan, whether your profile is set up, and a summary of your main resume; how your main resume meets a job's requirements; hiring contacts hirly finds for a job you open; where your applications stand, and the questions they are waiting on.

**Writes:** resume versions you or your assistant save; your main resume and profile, only when you ask it to replace them; applications you confirm you sent, and those jobs' status; and, if you allowed applying, applications hirly starts for jobs you confirm, and your answers to their questions.

**Never:** start an application unless you allowed applying and confirmed that job; delete anything in your hirly account; read the rest of your hirly account; see your card details.

## Privacy, terms and support

- Privacy policy: [hirly.me/privacy](https://hirly.me/privacy)
- Terms of service: [hirly.me/terms](https://hirly.me/terms)
- Support: [hirly.me/support](https://hirly.me/support) · support@hirly.me

Found a problem with the server or these docs? [Open an issue](https://github.com/Hirly-Me/hirly-mcp/issues) — please do not include personal information or anything from your hirly account.

## For maintainers

`server.json` is the server's entry in the official MCP Registry. To publish a change: edit it, bump `version` (the registry never overwrites a published version), merge to `main`, then run the **Publish to MCP Registry** workflow from the Actions tab. The workflow authenticates with GitHub's OIDC token, which grants the `io.github.Hirly-Me/*` namespace to workflows in this organisation; it uses no secrets.

## License

The documentation and configuration in this repository are MIT licensed — see [LICENSE](LICENSE). That does not cover the hirly service itself, which is governed by the [terms of service](https://hirly.me/terms).

hirly is a product of Insihts, Corp.