Bob MCP Server: Now uses OAuth with expanded tools

We’ve released a new version of the Bob MCP Server, in a gradual rollout to customers, making it easier and more secure to connect AI tools to Bob using OAuth-based user access.

With this release, Bob MCP is now designed around employee-level OAuth access. AI clients connect on behalf of the signed-in Bob user, and access is limited to that user’s permissions in Bob.

What’s changed

Bob MCP now connects with OAuth and offers a wider range of tools.

This means:

• AI tools connect to Bob using OAuth.
• Access is based on the signed-in Bob user.
• The AI client can only access and act on data that the user is permitted to access in Bob.
• Bob MCP now includes a wider range of tools, including people and org chart, time and attendance, tasks, performance reviews, goals, reports, compensation, hiring, documents, and more. See What you can do with Bob MCP.
• Documentation has moved to the Bob Help Center. For the latest setup instructions, supported AI clients, and available Bob MCP tools, see: Use Bob MCP Server.

Use OAuth for Bob MCP connections

With the new OAuth-based version, we recommend using OAuth for Bob MCP connections. OAuth provides user-level access and aligns the AI client’s permissions with the employee using it.

Action required

If you previously used the service user setup from the Developer Docs, update your MCP connection to use OAuth.

Refer to the Bob Help Center for the latest setup instructions: Use Bob MCP Server.