Periodix Actions

The Periodix Actions MCP server lets AI agents search LinkedIn and Sales Navigator using plain text.

От сообществаРаботаетБез входаГлобальныйБесплатноМожет изменять данные

Что умеет

  • Get Company Profile: Retrieve a LinkedIn company profile by its public identifier, numeric ID, or URN. Returns name, industry, employee-count range, description, locations, specialities/activities, we
  • Get Post Comments: List the comments on a LinkedIn post, including author details — a high-intent source of engaged leads. Requires a connected `profileId` (call `list-profiles` first). `postId` is th
  • Get Post Reactions: List the people who reacted to a LinkedIn post (or, with `commentId`, to a specific comment), including author details — a source of warm leads already active on the topic. Require

Какие данные видит

Нужен ли аккаунт

Не нужен: сервер работает без входа

The Periodix Actions MCP server lets AI agents search LinkedIn and Sales Navigator using plain text. No workflow builder, no HTTP configuration, no orchestrator. Describe what you need in natural language and the agent returns structured results.

This works with any MCP-compatible client: Claude Code, Claude Desktop, Cursor, Windsurf, or your own implementation.

Built by the team behind Periodix, an AI sales agent for LinkedIn rated 4.9/5 on G2. Periodix has been working with LinkedIn's infrastructure since 2023, and the MCP server is the fastest way to give your AI agent direct access to LinkedIn search.

Example prompts your agent can handle

  • "Find 4 DevOps engineers from Germany who work at companies with 50 to 100 employees in the SaaS industry."

  • "Who posted about Web Summit from France yesterday?"

  • "Search Sales Navigator for marketing directors at fintech companies in London with 200+ employees."

  • "Find open product manager jobs at Series B startups in New York."

  • "Show me people who posted about hiring a Head of Sales this week in the US."

  • "Find job posts for senior data engineers published in the last 7 days at companies with 500+ employees."

The MCP server accepts the same search types as the HTTP API: People, Companies, Posts, and Jobs on LinkedIn Classic, plus People and Companies on Sales Navigator. The difference is that you describe the search in words, and the agent constructs the query for you.

Список инструментов сервера (11)

Технические названия из tools/list. Нужны только разработчикам.

get-company-profileRetrieve a LinkedIn company profile by its public identifier, numeric ID, or URN. Returns name, industry, employee-count range, description, locations, specialities/activities, website and follower count — for B2B filtering by company size or industry. Requires a connected `profileId` (call `list-profiles` first); the `identifier` is the company you are looking up, not the connected account.
get-post-commentsList the comments on a LinkedIn post, including author details — a high-intent source of engaged leads. Requires a connected `profileId` (call `list-profiles` first). `postId` is the post's `social_id` (returned by `get-user-posts`), not the numeric ID in the post URL. Returns up to `limit` (max 100) comments; paginate by passing the returned `cursor` back on the next call.
get-post-reactionsList the people who reacted to a LinkedIn post (or, with `commentId`, to a specific comment), including author details — a source of warm leads already active on the topic. Requires a connected `profileId` (call `list-profiles` first). `postId` is the post's `social_id` (returned by `get-user-posts`), not the numeric ID in the post URL. Returns up to `limit` (max 100) reactions; paginate by passing the returned `cursor` back on the next call.
get-profileRetrieve the full LinkedIn profile of a person by their public identifier (e.g. `john-doe`) or internal ID (e.g. `ACoAA...`). Returns name, headline, summary, location, full work experience, education, skills, languages and certifications — the core data for CRM enrichment and ICP filtering. Requires a connected `profileId` (call `list-profiles` first); the `identifier` is the person you are looking up, not the connected account. Set `notify: true` to let the viewee see the visit (default false).
get-resultRetrieve the result of a long-running action by its `resultId`. Returns `status`: `pending` (still running), `completed` (with `output`), or `failed` (with `error`). Poll until the status is no longer `pending`.
get-relationsList the 1st-degree connections of a connected LinkedIn account — for finding mutual connections, re-engaging existing contacts, or network analysis. Requires a connected `profileId` (call `list-profiles` first); returns that account's own connections. Returns up to `limit` (max 1000) per page; paginate by passing the returned `cursor` back on the next call.
get-user-postsList the recent posts published by a LinkedIn person or company, for content analysis before outreach (e.g. AI personalization). Requires a connected `profileId` (call `list-profiles` first). `identifier` is the author's internal ID — for a person it starts with `ACo`/`ADo`, for a company it is the numeric company ID; set `isCompany: true` for a company. Returns up to `limit` (default provider-decided, max 100) posts; paginate by passing the returned `cursor` back on the next call.
linkedin-searchSearch LinkedIn (People, Companies, Posts, Jobs — Classic and Sales Navigator) via a search URL. Result shape depends on the URL. Returns a `resultId`; retrieve the result with the `get-result` action, polling until its `status` is `completed`.
list-profilesList the LinkedIn profiles connected to this organization. Use this to discover the `profileId` required by `search-people`, `lookup-search-parameter`, and `linkedin-search`. The `salesNavigator` flag indicates whether the profile has Sales Navigator access — required for `api: "sales_navigator"` and the SN-only filter fields in `search-people`. Only profiles with `connectionStatus: "connected"` can be used.
lookup-search-parameterResolve a free-text query to LinkedIn search parameter IDs for use in `search-people`. Pass the `type` matching the filter you are resolving and the `service` matching your search. Classic search (`service: "CLASSIC"`, the default) uses types LOCATION, INDUSTRY, COMPANY, JOB_TITLE. Sales Navigator search (`service: "SALES_NAVIGATOR"`) uses REGION (location), SALES_INDUSTRY (industry), DEPARTMENT (function), JOB_TITLE (role) and COMPANY. Returns several candidates; pick the one that matches the user's intent. Requires a connected `profileId` — call `list-profiles` first if you don't have one.
search-peopleSearch LinkedIn for people, returning one page of up to 100 results. Requires a connected `profileId` — call `list-profiles` first if you don't have one (`salesNavigator: true` indicates the profile can use `api: "sales_navigator"`). Filter IDs must be resolved beforehand via `lookup-search-parameter` (using the matching `service`) — they are NOT free text. Classic search (`api: "classic"`) takes flat ID arrays for `location` (type LOCATION), `industry` (INDUSTRY) and `company` (COMPANY). Sales Navigator search (`api: "sales_navigator"`) takes `{include, exclude}` objects and adds `function` (type DEPARTMENT), `role` (JOB_TITLE or plain text), `seniority` (fixed levels), `tenure`, and `company_headcount`; its `location`/`industry` resolve via REGION/SALES_INDUSTRY. To filter by skills or technologies, put them in `keywords` using boolean operators (e.g. `Node.js AND Vue AND ("full stack" OR full-stack)`).