IntevieIntevie + Claude
Claude custom connector

Connect Claude to Intevie's MCP server for permission-aware hiring work.

We help hiring teams connect Claude to Intevie with the https://mcp.intevie.com custom connector so they can ask about jobs, candidates, interview invitations, interview insights, approvals, and team invites without exporting recruiting data.

Use https://mcp.intevie.com as the remote MCP server URL. Claude gets tool-backed hiring context while access stays tied to the Intevie workspace account and permissions used during authentication.

Claude custom connector

Intevie MCP server

Remote MCP

Server URL

https://mcp.intevie.com

Connector type

Custom connector

Remote MCP URL

https://mcp.intevie.com

Authentication

Sign in with Intevie

Add the connector in Claude, paste the remote MCP URL, then sign in with Intevie so Claude can use only the workspace context that user is permitted to access.

Claude connects to Intevie through a remote MCP server URL, not through screenshots or pasted recruiting data.

For Claude-first teams

Use Claude to reason over hiring operations without pulling candidates, stages, or approval context into separate documents.

Remote MCP connection

Claude custom connectors use a remote MCP server URL. Use https://mcp.intevie.com so Claude can reach Intevie's MCP server from its cloud infrastructure.

Admin-friendly rollout

Team and Enterprise owners can add the connector for the organization, then each member connects their own Intevie account.

Connect Claude to Intevie

Connect once, then ask naturally.

Claude custom connectors are configured through Claude. Add https://mcp.intevie.com as the remote MCP server URL, save the connector, then sign in with Intevie before enabling it in a conversation.

Claude custom connector

Intevie MCP server

Remote MCP

Server URL

https://mcp.intevie.com

Add the connector in Claude, paste the remote MCP URL, then sign in with Intevie so Claude can use only the workspace context that user is permitted to access.

Claude connects to Intevie through a remote MCP server URL, not through screenshots or pasted recruiting data.
1

Copy the Intevie MCP server URL

Use https://mcp.intevie.com as the remote MCP server URL. Claude must be able to reach this public URL before the custom connector can call Intevie tools.

2

Open Claude connector settings

For Pro or Max, go to Customize > Connectors, click +, and choose Add custom connector. For Team or Enterprise, an Owner adds it from Organization settings > Connectors > Add > Custom > Web.

3

Paste the remote MCP details

Paste https://mcp.intevie.com, name the connector Intevie, and save it. If Claude asks for advanced authentication details, use the Intevie OAuth details supplied by your workspace admin or Intevie support.

4

Sign in and enable it in chat

Each member connects the custom connector with their own Intevie account, then enables Intevie from Claude's tools menu when they want Claude to use hiring data.

Permission-aware by design

Claude should only use the hiring context the user connected.

A custom connector is powerful because Claude can call tools directly. The safe path is scoped authentication, clear setup ownership, and visible tool use for any workflow that could affect candidates or team records.

Trusted connector URL

Only connect Claude to https://mcp.intevie.com. Avoid lookalike URLs or connector details copied from untrusted chats or documents.

Individual authentication

After an owner adds the connector, each user signs in so Claude receives that user's permitted Intevie context.

Review before actions

Use Claude for summaries and preparation, then review tool requests carefully before allowing actions that change hiring records.

Questions buyers ask

What to know before connecting

Who can add the connector in Claude?

Individual Pro or Max users can add a custom connector from Customize > Connectors. On Team and Enterprise plans, an Owner or Primary Owner adds it for the organization first.

What MCP server URL should I use?

Use https://mcp.intevie.com when adding Intevie as a Claude custom connector. Claude connects to remote MCP servers from Anthropic's cloud infrastructure, so the URL must be public rather than local-only.

Do users still need to sign in?

Yes. Users connect with Intevie so Claude uses their workspace permissions instead of a shared generic account.

Intevie MCP access

Put hiring context where your team already asks questions.

Jump to setup