Vitae

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?

Install Vitae in ChatGPT

Install in ChatGPT Set Up Manually

Opens the Vitae plugin page in ChatGPT. Choose Install, then connect your Vitae account.

Install the Vitae plugin in ChatGPT, then connect your Vitae account when asked. Availability depends on your ChatGPT account and workspace settings.

Follow along

Prefer to do it by hand?

ChatGPT

  1. In ChatGPT, open Plugins, press the plus button, then choose Add custom MCP server.
  2. Name it Vitae. Under Connection, paste the address below as the Server URL and choose OAuth.
  3. Read the warning and select I understand and want to continue. Choose Create as a plugin. Sign in to Vitae and review the requested access before approving.
  4. Install the resulting plugin. In a new chat, type @Vitae and ask: List my open jobs.

Manual setup has separate plan and workspace requirements: full access needs ChatGPT Business, Enterprise, or Edu on the web. Business admins or owners create the connection; Enterprise and Edu can also authorize members. Pro supports read-only custom connections.

Guide Me Through Manual Setup
Please help me connect Vitae to ChatGPT. I am not technical, so give me one small step at a time and wait for me after each one.

1. First, check that my ChatGPT plan, and my work account if I use one, lets me add a custom connector. If it does not, tell me plainly who can turn it on, and stop.
2. Walk me through adding a connector named Vitae with this address: https://mcp.vitae.ai/mcp
   In ChatGPT, open Plugins, press the plus button, then choose Add custom MCP server.
3. A Vitae page will ask me to sign in and press Approve. Tell me before it opens so I know it is safe. Never ask me to type my Vitae password into this chat.
4. When it is done, test it by asking Vitae to list my open jobs.

If I get stuck, I will tell you what I see on my screen.

Claude

  1. In Claude, open Customize, then Connectors.
  2. 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.
  3. Choose Connect next to Vitae. Sign in to Vitae and press Approve.
  4. 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

  1. Open grok.com/connectors.
  2. Choose New Connector, then Custom, and paste the address below.
  3. Sign in to Vitae and press Approve.
  4. In a new chat, ask: List my open jobs.

On Grok Business or Enterprise, an admin adds Vitae first.

https://mcp.vitae.ai/mcp
For developers and admins

Vitae address

The MCP server URL for any client. It changes with the tool selection below.

https://mcp.vitae.ai/mcp

The default address includes core, ATS, CRM, prospecting, and work tools. Your Vitae permissions still apply.

Choose individual toolsets
Included 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.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.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.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.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.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.

Open

Server details

Streamable HTTP transport. OAuth metadata discovery is published at the protected resource URL.

View ยท Health

Technical docs

Sign-in details, the tool list, scopes, and approvals.

Read