Orbit MCP Server

Use this when the user wants to add a known Orbit profile to a directory. Confirm the directory and profile. Requires an Orbit user connection; organization and directory permissions are enforced by Orbit.

Use this when the user wants to check supplied identities for existing directory membership before import. Requires an Orbit user connection; organization and directory permissions are enforced by Orbit.

Use this when the user wants to check if a public directory slug is available. Requires an Orbit user connection; organization and directory permissions are enforced by Orbit.

Use this when the user wants to create a directory. Confirm the organization, name, and visibility; public makes it discoverable outside the organization. Requires an Orbit user connection; organization and directory permissions are enforced by Orbit.

Use this when the user wants to schedule updates for selected members. Confirm profile IDs, interval, phases, and ongoing organization credit usage. Requires an Orbit user connection; organization and directory permissions are enforced by Orbit.

Use this when the user wants to stop a directory member's watcher after confirming the target. Requires an Orbit user connection; organization and directory permissions are enforced by Orbit.

Use this when the user wants to read a directory and its readiness before changing it. Requires an Orbit user connection; organization and directory permissions are enforced by Orbit.

Use this when the user wants to inspect people behind a completed city map or scalar people-count result, never arbitrary aggregate values. Supply its exact definition and evidenceSnapshot when present; city is required only for maps. Follow offset/hasMore. A stale snapshot requires refreshing the original insight, not a new search. This read never starts inference or enrichment. Requires an Orbit user connection; organization and directory permissions are enforced by Orbit.

Use this when the user wants to evaluate the saved shared Insights dashboard over the entire authorized published directory, not ranked search results. Set capabilities=true to check canView/canManage without evaluating. Evaluation and continued polling can advance external model work. Pending results are progress, never final counts. Preserve coverage, unknowns and freshness; stop on errors or rate limits. Returns data, not charts. Requires an Orbit user connection; organization and directory permissions are enforced by Orbit.

Use this when the user wants to read a directory member. Use its returned profile ID with get_profile for deep person research. Requires an Orbit user connection; organization and directory permissions are enforced by Orbit.

Use this when the user wants to check whether a directory is ready to search. Requires an Orbit user connection; organization and directory permissions are enforced by Orbit.

Use this when the user wants to read a source and recover pending CSV processing where needed. Requires an Orbit user connection; organization and directory permissions are enforced by Orbit.

Use this when the user wants to check import progress and recover pending CSV processing where needed. Queued or importing is not completion. Requires an Orbit user connection; organization and directory permissions are enforced by Orbit.

Use this when the user wants to read sourced directory-member updates sorted by event date or discovery date. Requires an Orbit user connection; organization and directory permissions are enforced by Orbit.

Use this when the user wants to inspect directory access grants before sharing or revoking access. Requires an Orbit user connection; organization and directory permissions are enforced by Orbit.

Use this when the user wants to find the user's organizations before choosing a directory. Do not guess organization IDs. Requires an Orbit user connection; organization and directory permissions are enforced by Orbit.

Use this when the user wants to list directory members, optionally filtering by name or source. This is not semantic search. Requires an Orbit user connection; organization and directory permissions are enforced by Orbit.

Use this when the user wants to check one-time refresh progress. Report acceptance separately from completion. Requires an Orbit user connection; organization and directory permissions are enforced by Orbit.

Use this when the user wants to list import sources and recover pending CSV processing where needed. Requires an Orbit user connection; organization and directory permissions are enforced by Orbit.

Use this when the user wants to list watchers for directory members. Requires an Orbit user connection; organization and directory permissions are enforced by Orbit.

Use this when the user wants to remove selected directory members after confirming the exact selection. Save the returned removal source for restoration. Requires an Orbit user connection; organization and directory permissions are enforced by Orbit.

Use this when the user wants to remove one directory member after confirming its directory-person ID, not its Orbit profile ID. Requires an Orbit user connection; organization and directory permissions are enforced by Orbit.

Use this when the user wants to remove members contributed by a source after confirming the source and impact. Requires an Orbit user connection; organization and directory permissions are enforced by Orbit.

Use this when the user wants to search within one directory using concise natural-language criteria close to the user's wording. Preserve explicit constraints without adding inferred roles or synonym lists. Never fall back to global search if access is denied or the directory is not ready. Requires an Orbit user connection; organization and directory permissions are enforced by Orbit.

Use this when the user wants to change a directory's details. Read it first and confirm changes, especially public visibility, which publishes it outside the organization. Requires an Orbit user connection; organization and directory permissions are enforced by Orbit.

Use this when the user wants to make an explicitly requested administrative source-status correction. Never mark an import completed merely to hide a failure; verify the actual processing state first. Requires an Orbit user connection; organization and directory permissions are enforced by Orbit.

Use this when the user wants to change a member's watcher. Confirm schedule, phases, enabled state, and credit implications. Requires an Orbit user connection; organization and directory permissions are enforced by Orbit.

Create or re-enable a scheduled profile watcher. Runs consume Orbit credits. Confirm the profile, organization and schedule first.

Permanently delete a watcher in its original organization.

Read one watcher by ID in the selected account. Keep its original organization.

List newest runs for a watcher in its original organization.

Replace selected watcher settings. May disable future runs or change schedule/phases; enabled runs consume credits. Keep its original organization.

Resolve identity at quick depth without upgrading known profiles; new discovery candidates may build level-1 profiles using credits. Quick discovery needs phone/email/address, URLs with exactly one intent.names entry, or one name plus an organization in intent.experiences. Use search_people for open-ended partial/full discovery. Enrich only selected profile IDs afterward. This call returns quickly; poll get_search_status until terminal (completed, completed_with_errors, failed). On timeout, retry with the same requestId and identical arguments — do not start a new search. Prefer get_search_status if you already have searchId. Discovery and depth beyond quick always run asynchronously. Find or resolve people and return compact people data for cards or text summaries. Use a concise query close to the user's wording. If the user's request is already clear and short, send it essentially unchanged: "aepi brothers who work in tech" needs no expansion into a full name, synonyms, or tech job categories. Preserve explicit constraints without adding inferred criteria. Supports query, structured intent, or identity signals; at least one must be nonempty. Prefer query alone for ordinary searches; use intent for explicit structured constraints, which override query-derived fields. For find, list, or shortlist requests, if the host visibly renders an interactive people list or single-result summary card, finish with that view and a brief acknowledgement. Otherwise, including in a text-only host, summarize the returned people data in text with available names, headlines, locations, and links; do not refer to an unseen card. Do not call get_profile or enrichment merely to verify, summarize, or display individual matches, including while searching or for a single match. Read profiles only after selection or an explicit request for person-specific details, research, or a substantive comparison. If done is false, the search is still running, even when people is empty: poll get_search_status before claiming a final result. Never restart the same search to poll it. Enable Candidate Discovery to find people beyond the known index. Discovery and generation use Orbit credits. Optional faceSearch requires candidateDiscovery: true, profileDepth: full, and at most 30 combined limit + candidateDiscoveryLimit slots (defaults 20 + 10). Already-full cached profiles remain cached.

Poll a people batch without new work. Each item id is the submitted personKey; result contains profile IDs, per-result statuses and profiles after that person finishes. Keep successes when another person fails. Read every next_offset page, including after terminal status. Poll queued/processing every 3 seconds; stop on completed, completed_with_errors, failed or canceled.

This call returns quickly; poll get_search_status until terminal (completed, completed_with_errors, failed). On timeout, retry with the same requestId and identical arguments — do not start a new search. Prefer get_search_status if you already have searchId. Discovery and depth beyond quick always run asynchronously. Find or resolve people and return compact people data for cards or text summaries. Use a concise query close to the user's wording. If the user's request is already clear and short, send it essentially unchanged: "aepi brothers who work in tech" needs no expansion into a full name, synonyms, or tech job categories. Preserve explicit constraints without adding inferred criteria. Supports query, structured intent, or identity signals; at least one must be nonempty. Prefer query alone for ordinary searches; use intent for explicit structured constraints, which override query-derived fields. For find, list, or shortlist requests, if the host visibly renders an interactive people list or single-result summary card, finish with that view and a brief acknowledgement. Otherwise, including in a text-only host, summarize the returned people data in text with available names, headlines, locations, and links; do not refer to an unseen card. Do not call get_profile or enrichment merely to verify, summarize, or display individual matches, including while searching or for a single match. Read profiles only after selection or an explicit request for person-specific details, research, or a substantive comparison. If done is false, the search is still running, even when people is empty: poll get_search_status before claiming a final result. Never restart the same search to poll it. Enable Candidate Discovery to find people beyond the known index. Discovery and generation use Orbit credits. Optional faceSearch requires candidateDiscovery: true, profileDepth: full, and at most 30 combined limit + candidateDiscoveryLimit slots (defaults 20 + 10). Already-full cached profiles remain cached.

Start one durable job for independent people; returns jobId quickly. Poll get_people_batch_status for per-person status and results. One failure never discards successful people. Discovery and generation use credits; existing search defaults apply. On timeout retry identical people with the same requestId; if jobId is known poll it instead. Never start a replacement batch.

Register an HTTPS endpoint to receive Orbit events. Confirm destination, organization, and event types first. The one-time signing secret is shown in the widget and hidden from the model.

Permanently delete a webhook endpoint in its original organization.

List organizations available to the connected Orbit user and show the default organization chosen during connection. Returns data for account questions or conversational organization switching with select_organization. This does not start paid work or buy credits.

Use this when the user wants to archive a directory after confirming the exact target. Orbit's delete route also archives; this does not permanently erase data. Requires an Orbit user connection; organization and directory permissions are enforced by Orbit.

Check whether the user connected Orbit to this app.

Start profile research for 1 to 20 Orbit profile IDs or slugs using the connected account's Orbit credits. The regenerate operation forces fresh work and can replace existing facts for every selected profile. Use regenerate only when the user asks for that refresh. Optional faceSearch applies to every selected profile, requires full or regenerate, needs no candidate discovery, and starts new paid work even for already-full profiles.

Use this when the user wants to count resolved directory members. Requires an Orbit user connection; organization and directory permissions are enforced by Orbit.

Read usage for the current research credential/principal and available/reserved credits for its billing account. Use for credit questions or to refresh a balance. Usage is not necessarily all activity by the user or organization. Does not purchase credits.

Use this when the user wants to list directories in a selected organization. Requires an Orbit user connection; organization and directory permissions are enforced by Orbit.

Remove a legacy widget token. This does not disconnect OAuth; use your host's connector settings for that.

Start profile research in Orbit using the connected account's Orbit credits. Partial builds a partial profile, full builds a full profile, and regenerate forces fresh work that can replace existing profile facts. Use regenerate only when the user asks to refresh the profile. Optional faceSearch requires full or regenerate, needs no candidate discovery, and starts new paid work even for an already-full profile.

Read the latest status and optional profile for one v3 enrichment request.

Use this when the user wants to grant directory permissions only to an existing principal in the same Orbit organization. The backend rejects recipients outside that organization; this does not publish the directory or send to arbitrary external destinations. Confirm the exact recipient, directory, and permissions; never infer a principal ID. Requires an Orbit user connection; organization and directory permissions are enforced by Orbit.

Use this when the user wants to suggest CSV column mapping from user-supplied headers. Review the mapping before upload; this may call an external model. Requires an Orbit user connection; organization and directory permissions are enforced by Orbit.

Use this when the user wants to remove the authenticated user's own membership after confirmation. Requires an Orbit user connection; organization and directory permissions are enforced by Orbit.

Use this when the user wants to inspect unresolved or processing directory members. Requires an Orbit user connection; organization and directory permissions are enforced by Orbit.

Use this when the user wants to populate a directory from known companies or schools. Confirm IDs, AND/OR criteria and research costs. Never guess entity IDs. Poll source status after acceptance. Requires an Orbit user connection; organization and directory permissions are enforced by Orbit.

Search everyone in one population: every current employee of a company, or everyone who attended a school. Reserves the quoted credits from the connected account and returns compact people data at once for cards or text summaries; Orbit keeps adding people while it runs. Follow with get_search_status until terminal. For find, list, or shortlist requests, if the host visibly renders an interactive people list or single-result summary card, finish with that view and a brief acknowledgement. Otherwise, including in a text-only host, summarize the returned people data in text with available names, headlines, locations, and links; do not refer to an unseen card. Do not call get_profile or enrichment merely to verify, summarize, or display individual matches, including while searching or for a single match. Read profiles only after selection or an explicit request for person-specific details, research, or a substantive comparison. Use only after quote_population_search and confirmation of the cost.

Use this when the user wants to answer a directory-wide analytics question using existing published facts, without enrichment or saving. Requires directory manage access. Supply either prompt alone OR title and definition, never both. Ask returned clarifications. If pending, continue with the returned widget title and definition, not the prompt; this advances model work. Space polls out and stop on errors/rate limits. Never present partial counts as final or infer sensitive traits. Returns data, not charts. Requires an Orbit user connection; organization and directory permissions are enforced by Orbit.

Read the full existing Orbit profile for an explicit person-specific research question, substantive comparison, or a text-only host. Modern callers must set purpose: research for requested analysis, or text_summary for a text-only host. Never choose a research purpose merely to display a profile or narrate search results. For compatibility, older published clients may omit purpose and receive the legacy profile response; this still makes one billed profile read. Modern research returns data without opening a card or changing visible results; older published widget bindings may display it. In a UI-capable host, use show_profile instead for simple profile-display requests or selection; do not read the full profile merely to narrate a visible card. Search already returns compact people data: do not call this merely to verify, summarize, or display each search match for a find, list, or shortlist request. For a simple profile-display request, if the host visibly renders a profile card, acknowledge it briefly without repeating its details. The visible card fulfills that display request: use at most one short acknowledgement, not a second profile card, portrait/image, name-and-headline block, Orbit link, biography, or unsolicited fact list. Do not start additional web searches or enrichment merely to decorate or repeat the visible card. Otherwise, including in a text-only host, summarize the returned profile in text with available source links; do not refer to an unseen card. For an explicit research question, use the returned source-backed profile to answer with analysis focused on the requested question, without recreating a visible card's portrait or identity block. Uses Orbit credits; use enrich_profile for requested new research.

Price a search for everyone in one population: every current employee of a company, or everyone who attended a school. Returns the whole cost as one number in credits. This read starts no work and reserves no credits. Quote first, tell the user the cost, and call search_population only after they confirm.

Use this when the user wants to start a credit-consuming one-time refresh. Confirm selected members or everyone and cost implications; preserve request_id on retries. Requires an Orbit user connection; organization and directory permissions are enforced by Orbit.

Use this when the user wants to restore selected removed members or a recorded removal source, within the backend's restoration window. Confirm the exact selection or source. Requires an Orbit user connection; organization and directory permissions are enforced by Orbit.

Use this when the user wants to rematerialize selected directory members from existing data, after confirming the selection. This is separate from a research refresh. Requires an Orbit user connection; organization and directory permissions are enforced by Orbit.

Use this when the user wants to revoke a specific access grant after confirming the recipient and permissions affected. Requires an Orbit user connection; organization and directory permissions are enforced by Orbit.

Use this when the user wants to replace the shared Insights dashboard after confirming the directory and requested changes. Read get_directory_insights first and preserve unrelated widgets. Send the latest revision and complete widgets array (empty explicitly clears it). A revision conflict requires reloading and reconciling, never blindly retrying. Requires directory manage access. Requires an Orbit user connection; organization and directory permissions are enforced by Orbit.

Set the default organization for new work on this Orbit connection. Use only for an organization explicitly chosen by the user; discover IDs with get_account_context. Changes apply across chats using this connection, not to existing jobs. Never switch automatically to bypass insufficient credits or permissions.

Display the full available existing Orbit profile after the user selects a person or explicitly asks to see/open their profile in a UI-capable host. Use this instead of get_profile for display-only requests. Profile details are delivered only to the widget, not the model; contact details remain masked. Finish with at most a brief acknowledgement; do not recreate the card, add another portrait or biography, or call get_profile, web search, or enrichment merely to narrate it. Search results already fulfill find/list/shortlist requests, including the summary card for a single match; do not open each match. For an explicit research question or a text-only host, use get_profile instead. Uses Orbit credits for one profile read; it does not generate or refresh facts.

Poll every 3 seconds while running; stop on completed, completed_with_errors or failed. Progress percent/ETA can be unknown; do not invent estimates. Keep ready people if others fail. Read the latest compact results and status for an existing Orbit search, including population searches, for a visible list or text summary. Empty results while done is false mean still searching, not no matches. Use outcome to distinguish failure from completed no matches. For find, list, or shortlist requests, if the host visibly renders an interactive people list or single-result summary card, finish with that view and a brief acknowledgement. Otherwise, including in a text-only host, summarize the returned people data in text with available names, headlines, locations, and links; do not refer to an unseen card. Do not call get_profile or enrichment merely to verify, summarize, or display individual matches, including while searching or for a single match. Read profiles only after selection or an explicit request for person-specific details, research, or a substantive comparison.

Send one signed test event to an existing endpoint in its original organization. Payload can contain recent real account data or an example. Confirm destination and type first. Free, not retried or stored in delivery history.

Use this when the user wants to import user-supplied CSV text into a directory. Confirm the target and field mapping. Never invent rows. Limited to 512 KiB; use the dashboard for larger files. Preserve idempotency_key on retries. Requires an Orbit user connection; organization and directory permissions are enforced by Orbit.

List profile watchers for the selected Orbit account.

List webhook endpoints for the selected organization. Secrets are masked.