INDIVIDUAL MCP TOOL

find_people

Use this when the user wants people at a company or in a role: names, job titles, seniority, department and LinkedIn URLs found on company team, about and author pages.

agentdata.runnone authenticationAvailability not checked

LIVE ENDPOINT

https://mcp.agentdata.run/mcp

No auth detected

Connect to this endpoint to inspect the live schema for find_people and invoke it with your own arguments.

Indexed input schema

{}

Risk classification

Inferred read-only · medium confidence · heuristic, not a guarantee.

No write-capable action terms were found; this is not proof that invocation has no side effects.

Parent server

agentdata.run

CONNECT WITH APPROVAL

Client installation

Review this server and its permissions before adding it. Secret placeholders must be set locally.

Codex

~/.codex/config.toml

[mcp_servers.agentdata]
url = "https://mcp.agentdata.run/mcp"
enabled = true

Claude Code

.mcp.json

{
  "mcpServers": {
    "agentdata": {
      "type": "http",
      "url": "https://mcp.agentdata.run/mcp"
    }
  }
}

Claude Desktop

Settings → Connectors → Add custom connector

Name: agentdata
Remote MCP URL: https://mcp.agentdata.run/mcp

Add this remote URL as a custom connector in Claude Desktop. Availability depends on the user plan and workspace policy.

Cursor

.cursor/mcp.json

{
  "mcpServers": {
    "agentdata": {
      "url": "https://mcp.agentdata.run/mcp"
    }
  }
}

Visual Studio Code

.vscode/mcp.json

Add to Visual Studio Code

{
  "servers": {
    "agentdata": {
      "type": "http",
      "url": "https://mcp.agentdata.run/mcp"
    }
  }
}

Generic MCP

Client-specific MCP configuration

{
  "name": "agentdata",
  "transport": "streamable-http",
  "url": "https://mcp.agentdata.run/mcp"
}

MCP Inspector

Run the official MCP Inspector locally and enter the indexed Streamable HTTP endpoint.

Related tools

lookup_company — Use this when the user asks about one specific company and you know its website domain, for example to research an account before a call: what it does, sector and business model, headquarters where known, the tools and technologies it runs (each with how it was detected and when it was first and last seen), and web signals (pricing page, free trial, API docs, careers).
search_companies — Use this to find a company by name or part of its domain (query), or to build a list of companies by sector, business model, B2B or B2C, technology used or headquarters country.
get_technologies — Use this when the user asks which companies use a particular technology (for example Intercom, Zendesk, HubSpot, Shopify, Stripe), or which technologies are most used.
get_signals — Use this when the user asks which companies recently started, stopped or switched using a technology, for example companies that left Intercom or adopted HubSpot: set moved_from or moved_to.
check_usage — Use this before a large task to see how much of today's allowance is left: requests in the current 5-hour window, distinct companies today and, with an API key, contact reveals.