Company Social MCP

What company-social-mcp MCP server does

The company-social-mcp MCP server maps a company identity to its social media profiles. It accepts a company name, website, or Google Maps listing and uses the Company Social Media Profile Finder Actor from the Apify Store to look for LinkedIn, Instagram, X, Facebook, and YouTube handles.

Returned matches include confidence information and evidence. This makes the result suitable for workflows where an agent or application needs to distinguish likely profiles from less certain matches. The repository is a manifest and configuration project; it does not contain the Actor implementation, Docker files, or truth sets.

As a tool in the Social Media category, it fits systems that need to add or verify social profile fields alongside company records. Example inputs can include individual domains such as apify.com or a batch of domains such as stripe.com and notion.so.

How it works

The company-social-mcp MCP server can be used through Apify’s hosted MCP endpoint, pinned to the publicrecords/company-social-profile-finder Actor, or through the Store Actor directly. The hosted option exposes the resolver as publicrecords--company-social-profile-finder.

The MCP surface also includes tools for retrieving details about an Actor run, reading dataset items, reading a key-value-store record, and stopping a running Actor run. An agent can therefore start a resolution, inspect its output, and manage the associated Apify run through the same connection.

A representative resolver request uses a queries array and a mode value, such as {"queries":["stripe.com","notion.so"],"mode":"resolve"}. Apify authentication is required, and execution charges are applied to the user’s Apify account. The documented Console PPE events are actor-start, entity-resolved for a primary entity, and identity-change; the listed prices are subject to the referenced Apify billing setup.

Setup and configuration

For Claude Desktop, configure an MCP entry that runs @apify/actors-mcp-server with publicrecords/company-social-profile-finder in its actor list. Set the APIFY_TOKEN environment variable to an Apify token. Alternatively, use the hosted MCP URL:

https://mcp.apify.com/?tools=publicrecords/company-social-profile-finder

Cursor can use that same URL in its MCP configuration. The README also documents signing in with Apify when Cursor asks for authentication. Direct Actor execution is available from the Apify Console or API for pipelines, CRM systems, and dashboards.

Tools and capabilities

The company-social-mcp MCP server documents these tools:

• publicrecords--company-social-profile-finder runs the profile-finding Actor.
• get-actor-run retrieves detailed information about a specific run.
• get-dataset-items reads records from a run dataset.
• get-key-value-store-record reads a key-value-store record.
• abort-actor-run stops an active Actor run.

The resolver is appropriate for single-company lookups and batches of company queries. It can also support selective requests, such as asking an agent to return only confident LinkedIn and X matches from a batch.

Limitations and notes

The repository documents MCP and client configuration rather than implementing the underlying Actor. Its MIT license applies to that documentation and configuration. The project is not affiliated with LinkedIn, Meta, X Corp, Google, or YouTube, and it does not replace Apify Console billing screens.

Results depend on the Actor’s resolution process and should be reviewed when a workflow requires high-confidence identity matching. Runs are billed through the connected Apify account, so deployment owners should account for Apify usage before using the resolver in recurring enrichment jobs.