# JustSift MCP connector Connect JustSift to Elaichi and Claude, ChatGPT, Cursor and the Elaichi Agent can search your company directory, open a person's profile and see their photo and fields, with every lookup recorded in an audit log. Source: https://elaichi.ai/connectors/justsift/ ## Facts | | | | --- | --- | | Application | JustSift | | Category | HRIS | | AI tools | 5 | | Authentication | Connects with an API key | | Bring your own OAuth app | No | | MCP endpoint | https://api.elaichi.ai/mcp | | Works with | Claude, ChatGPT, Cursor, any MCP client, and the Elaichi Agent | | Tools advertised by name | No. Connected tools are never listed one by one, however few there are. The endpoint advertises `search_tools` and `execute_tool` instead | ## What you can ask once JustSift is connected - Who on the Berlin support team reports to Priya? - Find engineers with Kubernetes listed in their JustSift profile. - List everyone in Finance with their titles and office locations. ## Connect JustSift in Elaichi This happens once for the organization, before any client is involved. 1. Open Connections, choose Add connection, and pick JustSift. 2. Optionally set Share with, then press Connect. 3. Paste a JustSift API key. One person generates a token in JustSift and pastes it once. Everyone else works through Share with, and never sees it. Credentials are vaulted and nobody, including the AI, reads them back. The connection becomes a toolbox immediately, so you can curate which JustSift tools are exposed, rename them, or freeze arguments before anyone points a client at it. ## JustSift MCP connector for Claude Endpoint: https://api.elaichi.ai/mcp 1. Open Customize, then Connectors. 2. Press Add. 3. Name it, paste the MCP server URL, then Continue. 4. Sign in and approve. On Team and Enterprise, an Owner adds it once. Everyone else turns it on for themselves. ## JustSift MCP connector for ChatGPT Endpoint: https://api.elaichi.ai/mcp 1. Open Plugins, then press the + button. 2. Name it and paste the endpoint into Server URL. 3. Leave Authentication on OAuth, then tick the risk acknowledgement. 4. Press Create, then sign in and approve. Works on the web today. The plugin directory lives at chatgpt.com/plugins. ## JustSift MCP connector for Cursor Endpoint: https://api.elaichi.ai/mcp 1. Open `~/.cursor/mcp.json`. 2. Add the endpoint under `mcpServers`. 3. Reload Cursor, then sign in and approve. Set up per machine, so repeat it on each computer you work from. ## Connect JustSift to any MCP client Endpoint: https://api.elaichi.ai/mcp 1. Add the endpoint as a remote MCP server. 2. Sign in and approve. The Elaichi Agent already has these tools, with nothing to set up. ## What the consent screen decides Only Read is granted by default, which is not enough to call a JustSift tool. Over MCP there is no trusted place to confirm a write in the moment, so the consent screen is the standing approval rather than a formality. Grant Read and Run tools. Think hard before granting Delete, which reaches into connected apps and cannot be undone. ## What teams do with JustSift through Elaichi ### Answer who reports to whom in seconds HR. Ask for everyone in a department with their titles, managers and locations, and get the list straight from JustSift profiles instead of exporting a spreadsheet. ### Confirm a person before granting access IT. When a request comes in, look the person up in JustSift by name or ID and check their team, manager and office before approving anything. ### Find the right owner for an escalation Support. Search JustSift for the person who covers a product, region or account, and hand the ticket to a named person rather than a shared inbox. ### Find internal experts for a deal Sales. Ask who in the company has worked in healthcare or speaks German, and pull the matching people from JustSift to loop into the pitch. ### Build a roster for an office or project Operations. Combine filters such as location, team and start date to list the people who belong on a floor plan, a rota or a project kickoff. ### Put names to faces on a new team Managers. Pull the photos and profile fields for everyone on a team you have just inherited, so the first one to ones start with the basics already known. ## Frequently asked questions ### How do I connect JustSift to Claude? First, connect JustSift in Elaichi by pasting your JustSift API key; there is no OAuth application to register and no client ID or secret to generate. Then open Claude, go to Customize, then Connectors, then Add, and paste https://api.elaichi.ai/mcp as the endpoint. Sign in to Elaichi when Claude asks, and JustSift people search is available in your next conversation. ### Does JustSift work with ChatGPT and Cursor as well as Claude? Yes. Once JustSift is connected in Elaichi, the same endpoint, https://api.elaichi.ai/mcp, works in Claude, ChatGPT, Cursor, any other MCP client and the Elaichi Agent. You connect JustSift once and every client picks it up. ### What can an AI agent actually do with my JustSift data? Through this connector an agent can search JustSift for people by name, team, location or any profile field, combine several filters into one search, open a single person's full profile, see their photo and other media, and check which fields your JustSift directory holds. In practice that means asking who is on a team, who someone reports to, or who has a particular skill. Short, concrete asks such as "everyone in Finance in Austin" work better than long sentences. ### Does connecting JustSift give the AI everything in the directory? No. Access through Elaichi follows the JustSift API key that was connected and the person who signed in to Elaichi, so an agent can only see the JustSift people and fields that connection can already see. Elaichi can narrow that further with roles and restrictions, and it can never widen it beyond what JustSift itself allows. ### Can my team share one JustSift connection? Yes. One person connects JustSift with the API key and shares the connection with a team in Elaichi, and nobody else on the team ever sees or handles that key. Each teammate still signs in to Elaichi as themselves, so every JustSift lookup in the audit log carries the name of the person who made it. ### Can I stop an agent from deleting or changing things in JustSift? Nothing in this connector can change or delete anything: all five JustSift actions look people, profiles, media and fields up, and none of them write back. If you also want to hide a particular lookup, such as browsing photos, an Elaichi restriction removes it per action, and a restricted action is never shown to the AI client at all, so no prompt can reach it. ### What happens to a JustSift connection when someone leaves? Offboarding a person in Elaichi ends their access to JustSift through every AI client at once. A JustSift connection they shared with a team keeps working for everyone else on that team. If you want the connection gone entirely, disconnecting JustSift once in Elaichi removes it from Claude, ChatGPT, Cursor and every other client together. ### Does the JustSift MCP connector work with Gemini, Codex, Claude Code or other MCP clients? Yes. JustSift is reached over the same MCP endpoint every client uses, so anything that speaks MCP can call it — Gemini, Codex, Claude Code, Windsurf, Cline, Zed and OpenCode among them — alongside Claude, ChatGPT, Cursor, and the Elaichi Agent. The tools on offer and the access behind them are identical whichever client asks. Only the setup screen differs. ## All 5 JustSift tools Every tool below is callable through https://api.elaichi.ai/mcp once JustSift is connected, subject to the toolbox it is in and the restrictions on the caller. - **List all JustSift complex search people** (List). Search justsift people using complex AND/OR filter logic against person fields, with an optional generic text query and field-based sorting. Returns: id, email. Max 100 per page. - **Get single JustSift person by ID** (Get). Get a single person in justsift by their id or email address. Returns the person record including its id and their profile attributes — a mix of standard properties and additional dynamic per-organization fields (the exact key set is listed by the /fields/person route). Required: id. - **List all JustSift search people** (List). Perform a simple people search in justsift. Returns a collection of matching people including id, firstName, lastName, pictureUrl, and dynamic per-organization fields. Accepts q plus optional sortBy, sortDirection (asc/desc), orQuery, and exact-match field filters by objectKey (e.g. department=Marketing); filters combine with AND unless orQuery is true. - **List all JustSift people media** (List). Retrieve a person's photo from justsift by their id or email. Returns the photo as binary JPEG image data. Required: id_or_email, media_kind. - **List all JustSift person fields** (List). List the person profile fields configured in justsift. Returns field definitions including objectKey and searchable; the field list is dynamic per organization.