Use SeekOut where your team works.

Choose by delivery path

• 01

  Interactive assistants

  ChatGPT, Claude, Microsoft 365 Copilot, Amazon Quick, and developer clients.

  Compare assistants

• 02

  Enterprise-managed setup

  Gemini Enterprise, Databricks, and Microsoft admin rollout paths.

  Review admin paths

• 03

  Headless automation

  OAuth client credentials for scheduled jobs and services that cannot open a browser.

  Plan automation

• 04

  Partner API

  Server-side REST integration for search, contact data, refresh, and analytics.

  Keep product contracts separate

After connecting an assistant, see the MCP V2 tool guide.

Documented setup paths

• Assistant app

  ChatGPT app

  Recruiters who want SeekOut inside ChatGPT.

  • Individual user; Team or Enterprise admin may need to allow the app.
  • Interactive SeekOut OAuth sign-in as the user.
  • Prerequisites: Active SeekOut account.; ChatGPT account with app availability for the workspace plan.
  Read setup guide

• Assistant connector

  Claude custom connector

  Personal, Team, or Enterprise Claude users connecting remote MCP.

  • User for personal plans; Owner or Primary Owner for Team and Enterprise.
  • Interactive SeekOut OAuth sign-in as the user.
  • Prerequisites: Active SeekOut account.; Claude account with connector support.; Custom connector URL: https://mcp.seekout.io/v2/claude.
  Read setup guide

• Enterprise assistant

  Microsoft 365 Copilot agent

  Recruiters working from the published SeekOut agent in Microsoft 365 Copilot.

  • Microsoft 365 or Teams administrator controls availability.
  • Interactive SeekOut OAuth sign-in as the user on first tool use.
  • Prerequisites: Microsoft 365 Copilot Chat access.; Active SeekOut account.; Agent allowed for the user or group.
  Read setup guide

• Custom assistant build

  Microsoft Copilot Studio connector

  Teams building and publishing their own Copilot Studio sourcing agent.

  • Copilot Studio maker plus Teams or Microsoft 365 administrator.
  • Microsoft authentication for the agent; SeekOut OAuth connection per user.
  • Prerequisites: Copilot Studio license.; Microsoft 365 Copilot license.; Administrator approval and distribution path.
  Read setup guide

• Managed enterprise assistant

  Gemini Enterprise

  Organizations connecting SeekOut as a custom MCP server data store.

  • SeekOut Support and a Google Cloud or Gemini Enterprise administrator.
  • Provisioned OAuth client; each user still signs in to SeekOut.
  • Prerequisites: Gemini Enterprise subscription.; Google Cloud or Gemini Enterprise administrator.; Custom MCP server support in an Agent Designer flow.
  Read setup guide

• Enterprise assistant connector

  Amazon Quick

  Amazon Quick Enterprise workspaces creating an MCP connector.

  • Amazon Quick administrator or connector creator.
  • Dynamic Client Registration with interactive SeekOut OAuth sign-in.
  • Prerequisites: Amazon Quick Enterprise subscription.; Administrator or connector-creation permissions.; MCP server endpoint: https://mcp.seekout.io/v2/mcp.
  Read setup guide

• Data and agent platform

  Databricks Marketplace MCP service

  Databricks users invoking SeekOut from Genie One, AI Playground, or agents.

  • Databricks workspace, metastore, or service administrator.
  • Marketplace OAuth client and per-user SeekOut OAuth sign-in.
  • Prerequisites: Unity Catalog workspace in a supported Model Serving region.; Managed MCP Servers preview enabled.; Required metastore, catalog, schema, service, connection, and egress permissions.
  Read setup guide

• Developer tool

  Developer and CLI tools

  Claude Code, Gemini CLI, Codex, VS Code, Cursor, desktop apps, and custom clients.

  • The developer or user configuring the local MCP client.
  • Interactive OAuth 2.1 through the MCP client.
  • Prerequisites: MCP-compatible client.; Streamable HTTP server URL: https://mcp.seekout.io/v2/mcp.; Browser access for first sign-in.
  Read setup guide

• Automation

  Automated MCP workflows

  Scheduled jobs, CI/CD, backend services, and headless environments.

  • SeekOut provisions the credential for the approved automation identity.
  • OAuth client credentials exchanged for a short-lived bearer token.
  • Prerequisites: Provisioned client ID and client secret delivered through a secure channel.; Credential permissions and rate limits set for the workflow.; Runtime secret storage outside source control.
  Read setup guide

• REST API

  SeekOut Partner API

  Server-side applications that need REST search, contacts, refresh, or analytics.

  • SeekOut representative provisions organization API access.
  • Provisioned API key sent in the Api-Key header from a trusted server.
  • Prerequisites: Partner API access approved by SeekOut.; Server-side secret storage.; Configured endpoint permissions and rate limits.
  Read setup guide

Access checklist

• Product license

  The customer has a SeekOut product that includes the requested source or action.

  • Does not prove that a specific user has permission.
  Check before running

• Tenant enablement

  ATS, internal talent, healthcare, nursing, or another configured source exists.

  • Does not prove that every assistant or API key can use it.
  Keep source explicit

• Admin approval

  The chosen assistant or platform is allowed for the workspace or users.

  • Does not prove that SeekOut data access has been granted.
  Pair with setup owner

• Configured connector

  The client or platform can discover and call the SeekOut MCP server.

  • Does not prove that paid actions are approved or funded.
  Hand to an agent

• User permission

  The signed-in user or provisioned credential can access the operation.

  • Does not prove that another user or tenant has the same access.
  Verify with the API reference

Boundaries before an assistant runs work

• A connected assistant means the client can reach SeekOut MCP; it does not prove the user's Recruit license, data-source entitlements, ATS connectivity, contact credits, export credits, or write permission.
• The Partner API uses a separate Api-Key header and base URL https://partnerapi.seekout.io; keep that key on trusted servers only.
• Headless automation uses provisioned OAuth client credentials, not a browser credential, a Developer API bearer key, or an MCP assistant connection.

Agent-readable artifacts

• Human integration guide

  Setup-owner and access-boundary guide for recruiters and administrators.

  Open guide

• Human recipe guide

  Outcome-led plans for shortlist, market kickoff, and ATS rediscovery work.

  Open recipes

• Agent starting point

  Human-readable agent context with the artifact map and useful-result contract.

  Open agent page

• Markdown index

  Agent-readable index with source URLs, routes, and handoff links.

  Fetch Markdown

• Catalog JSON

  Structured integration inventory from one public-safe data module.

  Fetch catalog

• Recipe JSON

  Structured recipe checklist and recovery behavior.

  Fetch recipes