> ## Knowledge Base Index
> Fetch the complete knowledge base index at: https://docs.xobin.com/sitemap.xml
> Use this file to discover available pages before exploring further.
> Pure-Markdown content can be obtained by appending a '.md' suffix to the content URLs listed in the sitemap (without the trailing slash).

# Connecting Xobin to AI Assistants via MCP

**What is MCP Integration?**
Connecting a compatible AI assistant to Xobin MCP allows it to retrieve hiring data and perform supported recruiting actions on your behalf.
Once connected, you sign in to Xobin and approve access. The assistant never receives your Xobin password — all requests remain bound to your company, role, and the specific permissions you grant.

**Prerequisites:**
* A Xobin account with **Super Admin** or **Admin** access. Observer and Test Creator roles cannot complete connector consent.
* The **Xobin MCP server URL** for your environment — an HTTPS address ending in `/mcp`, provided by Xobin.
* An AI client that supports remote MCP over Streamable HTTP:
    * Claude (Web, Desktop, Cowork, or Mobile)
    * ChatGPT (Plus, Pro, Business, Enterprise, or Education)
    * Gemini Enterprise (Google Cloud) or Gemini Enterprise – Business Edition

Replace the placeholders below with the values provided by Xobin:
| Placeholder | Description |
| `{MCP_HOST}` | The MCP host, with no trailing slash |
| `{MCP_URL}` | https://{MCP_HOST}/mcp |

**Connection Values**
Use these values across all clients:
| Field | Value |
| MCP Server URL | https://{MCP_HOST}/mcp |
| Authorization URL | https://{MCP_HOST}/authorize |
| Token URL | https://{MCP_HOST}/token |
| Scopes | `mcp:read` `mcp:write` |
| PKCE | On (S256) |
| HTTP Basic Auth on Token Endpoint | Off |
| Scope | What It Allows |
| `mcp:read` | View and search supported Xobin data |
| `mcp:write` | Create, update, invite, and perform other write actions |

|| Note: Claude and ChatGPT discover OAuth automatically — leave Client ID and Client Secret empty unless Xobin has provided a pre-registered client. Gemini Enterprise does not support auto-discovery and requires a Client ID and Client Secret.

**How Access Works**
* Add Xobin as a remote MCP connector in your AI client.
* The client opens Xobin's sign-in and consent screen.
* Sign in with your Xobin recruiter account and select **Allow Access**.
* The assistant can now call Xobin tools on your behalf — all role and permission checks still apply.
* Review write actions (invites, messages, record changes) before confirming them in the assistant.
* You can disconnect and re-connect the connector at any time.

**Disconnecting Xobin**
| Client | Where to Disconnect |
| Claude | Customize → Connectors (Owners: Organization Settings → Connectors). Remove or disconnect Xobin. |
| ChatGPT | Settings → Plugins. Remove or disconnect the Xobin app. |
| Gemini Enterprise | Data Store Actions, or Business Edition → Connected Apps. Delete the MCP connection for a full reset. |

|| **Note:** Disconnecting stops new tool calls but does not delete candidates, assessments, or other records already created in Xobin.

**General Troubleshooting:**
* **Sign-in opens but consent is denied.**
Sign in as a Super Admin or Admin recruiter. Observer and Test Creator roles cannot authorize MCP.

* **Tools appear, but write actions return "forbidden."**
Your recruiter role or Xobin permissions may be blocking that action — the same limits apply within the Xobin app itself. Ensure the `mcp:write` scope has also been granted.

* **Assistant answers without calling Xobin.**
Ensure the connector is enabled for that conversation, and explicitly mention "Xobin" in your prompt.

* **Connection works for one person but not another.**
Each user must individually complete the Xobin sign-in process. Tokens are bound to the recruiter who approved consent — not shared across the company as a single API key.