Skip to main content

​
Overview & Capabilities

Jobin MCP acts as a secure, read-only bridge between your AI assistant and your Jobin.cloud workspace. It allows your assistant to pull context directly from your database during research or outreach planning.

​
What Your Assistant Can Do

⚠️ Important: Stable Jobin MCP tools do not mutate CRM contacts, campaigns, notes, tags, or messages. People search is sales-enabled and may cache returned prospects as known profile data so later imports and dedupe can reuse the same profile truth.

​
Before You Begin

Ensure you have the following ready:
  • An active Jobin.cloud account.
  • An AI assistant that supports remote MCP servers, HTTP MCP servers, or custom connectors (e.g., Claude, Codex).
  • Access to your assistant’s integration or developer settings.

​
Connection Details

When your assistant prompts you for a connection URL, use the following:
💡 Default setup: Most desktop assistants use a secure web sign-in flow. Just paste the URL and log in when prompted.

​
Step-by-Step Integration Guides

​
Option 1: Connecting with Claude

Bring your Jobin.cloud context directly into your Claude conversations.
  1. Navigate to Claude Settings > Connectors.
  2. Click Add connector (or Add custom connector).
  3. Name it Jobin.cloud.
  4. Paste the Connection URL: https://mcp.jobin.cloud/mcp
  5. Click Add, then select Connect.
  6. Sign in with your Jobin.cloud credentials.
  7. Ensure Jobin.cloud is enabled in your chat sidebar menu when starting a new conversation.
Note: For Team or Enterprise plans, an organization admin must add the connector first before individual team members can sign in.

​
Option 2: Connecting with ChatGPT

Bring your Jobin.cloud context and actions directly into ChatGPT conversations using Developer Mode.
  1. Open ChatGPT on the web.
  2. Go to Settings > Apps & Connectors.
  3. Open Advanced settings and turn on Developer Mode.
  4. Return to Apps & Connectors and click Create or Create app.
  5. Name it Jobin.cloud.
  6. Add a short description, for example: Use Jobin.cloud to search, enrich, and manage recruiting and outreach workflows.
  7. Paste the Connection URL: https://mcp.jobin.cloud/mcp
  8. Select the remote MCP connection type if prompted.
  9. Complete the Jobin.cloud authorization flow when prompted.
  10. Click Scan Tools, then confirm the tools detected from Jobin.cloud.
  11. Click Create.
  12. Start a new ChatGPT conversation, open the + tools menu near the composer, and select Jobin.cloud from the available apps/tools.
Note: Developer Mode must be enabled before custom MCP apps can be created. For Business, Enterprise, or Edu workspaces, an admin or owner may need to enable Developer Mode or approve the app before other workspace members can use it.

​
Option 3: Connecting with Codex

Perfect for developers and recruiters using Codex for outreach engineering and profile research.
  1. Open Codex Settings and find MCP settings.
  2. Add a new MCP server named Jobin.cloud.
  3. If prompted for a server type, select Remote, HTTP, or Streamable HTTP.
  4. Paste the Connection URL: https://mcp.jobin.cloud/mcp
  5. Leave all advanced fields (STDIO, args, headers) blank.
  6. Follow the prompt to complete the secure Jobin.cloud web sign-in.
Tip: If you use the Codex terminal, type /mcp to quickly review active connections.

​
Advanced Configurations

If you prefer managing integrations via config files or command-line interfaces, use the configurations below.

​
Non-Interactive Bearer Token Setup

Use this option for AI agents or server-side MCP clients that cannot complete an interactive browser OAuth flow.
  1. In Jobin.cloud, open WorkGroup > Integrations.
  2. Create a new integration credential with provider jobin-mcp.
  3. Choose the MCP scopes to grant. Read access is selected by default; select write access when the connector should be allowed to make approved changes.
  4. Copy the returned mcp_... token once.
  5. Configure your MCP client to call https://mcp.jobin.cloud/mcp with:
Dashboard-issued MCP tokens are scoped to the workgroup where they were created and only grant the MCP scopes selected at creation time. Regular sk_... REST API keys are not accepted by the MCP endpoint.

​
Codex config.toml Setup

Open your configuration file located at ~/.codex/config.toml (or access it via Codex IDE Extension > Gear Menu > MCP Settings). Add the following snippet:
After saving, authenticate via your terminal:
Note: Restart Codex if the server does not register immediately.

​
Claude Code Terminal Setup

For developers using the Claude Code CLI interface, run the following command to add the remote server:
Once added, initiate authentication by running:

​
Managing Multiple Workgroups

Jobin MCP functions within one active workgroup at a time to maintain data boundaries and prevent your AI from mixing up client or team data. Even though Jobin MCP is read-only, switching workgroups changes which workspace the assistant is allowed to read from. The switch tool therefore requires the assistant to include confirmation that you manually approved the workgroup change before the server issues a refreshed MCP token. If your account belongs to multiple workgroups, your assistant can navigate between them using this workflow:
  1. Ask the assistant which Jobin workgroups you can access.
  2. Tell it which workgroup you want to use.
  3. Confirm the switch when the assistant asks for approval.
  4. Ask your Jobin question after the switch.
Examples:
Switch to my Recruiting workgroup.
Use my Sales Ops workgroup for the next Jobin search.
Show my Jobin workgroups and move to the one called Hiring Team.
After the assistant switches workgroups, continue with your normal request:
Switch to my Recruiting workgroup, then find contacts named Sarah.
Use my Client Delivery workgroup and show me contacts tagged Finance.

​
If The Assistant Is Not Sure

If the assistant cannot tell which workgroup you mean, ask it to list your workgroups first:
Show my Jobin workgroups and tell me which one is active now.
Then ask it to switch:
Switch to the Recruiting workgroup.
If two workgroups share the same name, the assistant may ask to use the workgroup ID instead so it can switch safely to the correct one.

​
Verifying & Using Your Connection

​
Test Prompt

Once connected, test the integration by asking your assistant:
“Check my Jobin.cloud connection.”

​
Example Prompts to Try

  • “Find contacts named Sarah in my Jobin workspace.”
  • “Search for profiles with the title ‘Head of Sales’.”
  • “Find Project Manager candidates with 10 or fewer years at their current company.”
  • “Review this contact’s profile and suggest personalized outreach angles.”
  • “List my accessible workgroups and tell me which one is currently active.”
  • “Switch to my Sales Ops workgroup, then search for contacts tagged ‘Leads’.”

​
Troubleshooting

​
My assistant can’t find specific contacts.

  • Broaden your search: AI models handle broad queries better initially. Try “Search for contacts named Sarah” before narrowing it down to “Search for Sarah with the role Head of Sales”.
  • Verify your workgroup: Ensure the assistant is searching the correct workspace by asking: “List my accessible workgroups and tell me which one is active.”

​
The assistant says a requested action is “Not Available”.

  • This is expected behavior if you ask the assistant to modify data. Jobin MCP is strictly read-only and cannot write, edit, or delete information.
  • If jobin_get_mcp_capabilities lists a read-only tool that your assistant cannot call, rescan tools or reconnect the Jobin MCP connector. Some assistants cache tool discovery separately from the active Jobin session.

​
Authentication is failing or looping.

  • Disconnect the Jobin MCP server completely from your assistant’s settings page, re-add the server URL, and perform a fresh login.