Use Vitae inside ChatGPT, Claude, or Grok
Ask ChatGPT, Claude, or Grok about your jobs, candidates, and clients, and let it make changes in Vitae for you. It only sees what you can see, and it asks you before it changes any of them. You pay for ChatGPT, Claude, or Grok as usual.
Which app do you use?
Send one message to ChatGPT
ChatGPT opens in a new tab with the message already typed. Press send.
Works on ChatGPT Business, Enterprise, and Edu, in a web browser. If you are not a workspace admin, ask one to add Vitae first. ChatGPT Pro can only look things up. Other plans cannot use it yet.
Follow along
- ChatGPT walks you through the rest, one small step at a time.
- A Vitae page asks you to sign in and press Approve. That is normal and safe.
- To check it works, ask: “List my open jobs.” In Vitae, the Assistant then shows Connected.
Prefer to do it by hand?
ChatGPT
- In ChatGPT, open Settings, then Apps, then Advanced settings. Turn on Developer mode. You do not need to be a developer.
- Go back to Apps and choose Create. Name it Vitae and paste the address below.
- Choose Scan Tools. When the Vitae page opens, sign in and press Approve. Then choose Create.
- In a new chat, pick Vitae from the tools menu, or type @Vitae, and ask: List my open jobs.
On Business, only a workspace admin can do this. They share Vitae with the team from Workspace settings, then Apps.
Claude
- In Claude, open Customize, then Connectors.
- Choose Add, then Add custom connector. Name it Vitae, paste the address below, and choose Add. If Claude asks how to sign in, choose Sign in now.
- Choose Connect next to Vitae. Sign in to Vitae and press Approve.
- In a new chat, ask: List my open jobs.
On Team or Enterprise, an owner adds Vitae first in Organization settings, then Connectors. Then you choose Connect next to Vitae.
Grok
- Open grok.com/connectors.
- Choose New Connector, then Custom, and paste the address below.
- Sign in to Vitae and press Approve.
- In a new chat, ask: List my open jobs.
On Grok Business or Enterprise, an admin adds Vitae first.
For developers and admins
Vitae address
The MCP server URL for any client. It changes with the tool selection below.
The default address includes core, ATS, CRM, prospecting, and work tools. Your Vitae permissions still apply.
Choose individual toolsets
Claude Code
Run this once from any folder. The user scope makes Vitae available in all your Claude Code sessions.
claude mcp add --transport http vitae --scope user https://mcp.au.vitae.ai/mcp
Start Claude Code, run /mcp, choose vitae, and finish the Vitae OAuth flow in your browser. Check it with claude mcp list.
Install the Vitae MCP server for me in Claude Code from start to finish. Run this user-level setup command yourself: claude mcp add --transport http vitae --scope user https://mcp.au.vitae.ai/mcp Then start the Vitae OAuth connection flow. When browser authorization is required, pause and tell me exactly what to approve. After I authorize, verify the connection with claude mcp list and confirm that Vitae tools are available. Prefer OAuth. Do not ask me for or create a personal access token unless OAuth is unavailable. Do not modify project files. If setup fails, diagnose the error and give me the smallest next action.
Codex
Register Vitae in your user-level Codex configuration, then sign in.
codex mcp add vitae --url https://mcp.au.vitae.ai/mcp
Run codex mcp login vitae and finish the Vitae OAuth flow in your browser. Check it with codex mcp get vitae or codex mcp list. Open a new Codex task if the current one does not refresh its tools.
Install the Vitae MCP server for me in Codex from start to finish. Run these user-level setup commands yourself: codex mcp add vitae --url https://mcp.au.vitae.ai/mcp codex mcp login vitae When browser authorization is required, pause and tell me exactly what to approve. After I authorize, verify the connection with codex mcp get vitae and codex mcp list. Confirm that Vitae is registered, and tell me if I need to open a new Codex task before its tools become available. Prefer OAuth. Do not ask me for or create a personal access token unless OAuth is unavailable. Do not modify project files. If setup fails, diagnose the error and give me the smallest next action.
Grok terminal
grok mcp add --transport http vitae https://mcp.au.vitae.ai/mcp
OAuth starts on first use. Then run grok mcp list or grok mcp doctor vitae.
Cursor
Manual only. Put the endpoint in mcp.json. There is no one-click install, and Vitae does not ship a Cursor plugin.
Access keys
For clients that cannot complete OAuth. Keys start with vmcp_. Treat them like passwords: Vitae stores only a hash, so copy a key when you create it.
Server details
Streamable HTTP transport. OAuth metadata discovery is published at the protected resource URL.
Technical docs
Sign-in details, the tool list, scopes, and approvals.