Skip to main content
To connect Codex to Jobin, add a remote MCP server named Jobin.cloud with the URL https://mcp.jobin.cloud/mcp in Codex’s MCP settings (or in ~/.codex/config.toml), then complete the secure Jobin.cloud sign-in.

​
What you can do once connected

Your assistant works with your Jobin data in plain language, so you don’t switch between tools. For example, you can ask it to:
  • Find and review contacts by role, location, tag, sequence, or tenure, and read their profiles, notes, and activity.
  • Prepare outreach by reading a contact’s timeline and drafting personalized ideas.
  • Keep records current by creating contacts, adding tags and notes, and requesting enrichment, with your approval.
  • Work with sequences and pipelines by finding sequences, adding contacts, moving them between stages, and reviewing performance.
  • Manage follow-ups by reviewing tasks and creating new ones.
Your connection’s permissions decide which actions are available. See the Jobin MCP overview and the capabilities reference.

​
Before you begin

  • An active Jobin.cloud account.
  • Codex with MCP server support.
  • The Jobin MCP connection URL:

​
Set up in Codex settings

1

Open MCP settings

Open Codex Settings and find MCP settings.
2

Add a server

Add a new MCP server named Jobin.cloud.
3

Choose the server type

If prompted for a server type, select Remote, HTTP, or Streamable HTTP.
4

Paste the URL

Paste the connection URL: https://mcp.jobin.cloud/mcp
5

Leave advanced fields blank

Leave all advanced fields (STDIO, args, headers) blank.
6

Sign in

Follow the prompt to complete the secure Jobin.cloud web sign-in.
If you use the Codex terminal, type /mcp to review active connections.

​
Set up with the config file

If you prefer managing integrations through a config file, open ~/.codex/config.toml (or open it from the Codex IDE extension: Gear Menu > MCP Settings) and add:
After saving, authenticate from your terminal:
Restart Codex if the server does not register immediately.

​
Check the connection

Ask Codex:
Check my Jobin.cloud connection.
Then try a search:
Find contacts named Sarah in my Jobin workspace.
Your connection’s permissions determine which actions are available. Read access lets Codex retrieve information; write access lets it carry out changes with your approval. Ask it to check the current connection permissions before your first action.

​
Troubleshooting

Restart Codex. If you used the config file, confirm the [mcp_servers.jobin] block is saved and run /mcp to list active connections.
Check that the server is enabled and its credentials are valid. Run codex mcp login jobin again for expired credentials or missing scopes.
Refreshing tools and signing in again are different things. Follow the refresh guidance to confirm what Jobin supports and refresh the connection only if needed.
Use an MCP token instead. It is meant for agents and clients that can’t open an interactive sign-in.
Jobin MCP works in one workgroup at a time. Ask: “List my accessible workgroups and tell me which one is active.” See Switch workgroups.

​
Next steps

Jobin MCP overview

What you can do, workgroups, and example prompts.

MCP reference

Every tool, permission, resource, and prompt.