
Company Social Mcp
io.github.GeminiGeorge22v1.0.0Updated Oct 2, 2026
Company social handles (LinkedIn, Instagram, X, Facebook, YouTube) via Apify MCP.
Overview
Resolves a company name, website, or Maps listing to its LinkedIn, Instagram, X, Facebook, and YouTube handles via Apify's hosted MCP.
- What it does
- Exposes the Apify Actor publicrecords/company-social-profile-finder through Apify's hosted MCP endpoint, so an assistant can turn a company name, domain, or Google Maps listing into verified social handles with confidence and evidence. Alongside the resolver tool it exposes generic Apify run tools: get-actor-run, get-dataset-items, get-key-value-store-record, and abort-actor-run. It is a manifest-only repository documenting MCP and client configuration, not the Actor source.
- When to use it
- Use it when a CRM, lead-gen, or enrichment workflow needs social profiles for a list of company domains, or when an assistant should answer which social accounts belong to a given company. It fits sales and marketing enrichment pipelines rather than general browsing.
- Requirements
- A remote MCP endpoint at mcp.apify.com with the tool pin for publicrecords/company-social-profile-finder. An Apify account and your own Apify token are required, supplied as the APIFY_TOKEN environment variable or by signing in when the client prompts. Runs are billed to that Apify account.
Installation
In SourceWeft
- Open Company Social Mcp in the dashboard and add it to a workspace.
- Enable the server for the chats that should use its tools.
Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.
Other MCP clients
Add this to your client's mcpServers config.
{
"mcpServers": {
"company-social-mcp": {
"type": "http",
"url": "https://mcp.apify.com/?tools=publicrecords/company-social-profile-finder"
}
}
}README
company-social-mcp
Drop-in company social profile resolution for sales and marketing software — CRMs, lead-gen tools, enrichment pipelines, and AI assistants — via Apify’s hosted MCP or the Store Actor directly.
Resolves a company name, website, or Google Maps listing to its verified LinkedIn, Instagram, X, Facebook and YouTube handles, with evidence. Manifest-only repo — no Actor source.
Disclosure: I maintain these Actors on Apify Store (publicrecords). This repo documents MCP / client config only.
MCP pin
Use either path:
- Apify MCP (Claude Desktop, Cursor, or any MCP client) with the pin above
- Store Actor directly in Apify Console / API for pipelines, CRMs, and dashboards
Auth: your own Apify token in the client when prompted. Runs are billed on your Apify account.
Pricing (Console PPE, FREE tier base, live 2026-10-02)
Measured proof: apify.com → run dqgG9vmZuLevEMQ3T — 5 confident / 4 confirmed handles (2026-09-28).
Tools
Live tools/list against the pin URL (Bearer Apify token). Tool names exposed:
Claude Desktop
Add to claude_desktop_config.json (macOS: ~/Library/Application Support/Claude/claude_desktop_config.json):
Or point the Apify remote MCP URL (with the pin above) if your Claude Desktop build supports remote MCP servers.
Cursor
In Cursor MCP settings / .cursor/mcp.json:
Sign in with Apify when Cursor prompts.
Example prompts
1) Resolve a company website
Prompt: Which social profiles belong to apify.com?
Expected: LinkedIn / Instagram / X / Facebook / YouTube handles with confidence + evidence (see proof run dqgG9vmZuLevEMQ3T).
2) Enrich a CRM row
Prompt: Resolve social handles for these domains: stripe.com, notion.so. Return confident LinkedIn and X only.
Tool call the agent makes (publicrecords--company-social-profile-finder):
What this repo is not
- Not Actor implementation / Docker / truth sets
- Not a substitute for Apify Console billing screens
- Not affiliated with LinkedIn, Meta, X Corp, Google, or YouTube
License
MIT — applies to this documentation and config only.
Published by the publicrecords maintainer on Apify.
Source: README.md at commit db8f280
Tools
0Version history
1- v1.0.0LatestOct 2, 2026

