{
  "markdown": "# SalesTouch\n\n![Version 0.8.0](https://img.shields.io/badge/version-0.8.0-111827)\n![License MIT](https://img.shields.io/badge/license-MIT-16a34a)\n\nSalesTouch is an AI-native GTM prospecting platform. It helps agents research\nand qualify prospects, build audiences, start conversations, manage follow-ups,\nand execute controlled LinkedIn outreach. It provides account, conversation,\nlookup, outreach, engagement, publishing, durable scheduling, queue, and paginated extraction tools\nthrough an OAuth-protected remote endpoint.\n\nSalesTouch is not affiliated with, endorsed by, or sponsored by LinkedIn.\n\n## Install\n\n### Claude Desktop, Cowork, or Claude Code\n\nIn Claude Desktop or Cowork, add the marketplace `antoinedsh/salestouch`, then\nenable the `salestouch` plugin and complete OAuth from `/mcp`.\n\nIn Claude Code:\n\n```text\n/plugin marketplace add antoinedsh/salestouch\n/plugin install salestouch@salestouch\n/mcp\n```\n\n### Cursor\n\nInstall this repository as a Cursor plugin, or add the following remote MCP\nconfiguration:\n\n```json\n{\n  \"mcpServers\": {\n    \"salestouch\": {\n      \"url\": \"https://www.salestouch.io/api/mcp\"\n    }\n  }\n}\n```\n\n### Any Streamable HTTP client\n\nUse `https://www.salestouch.io/api/mcp` and name the server `salestouch`. The\nclient discovers the SalesTouch OAuth flow automatically; no static API key or\nLinkedIn credential belongs in the MCP configuration.\n\n## OAuth and first check\n\nThe browser authorization flow grants scoped SalesTouch access. LinkedIn\npasswords, cookies, and authentication secrets are never shared with the AI\nclient.\n\nVerify the connection with a read-only request:\n\n> List the LinkedIn accounts connected to my SalesTouch workspace.\n\n## Three complete workflows\n\n### 1. Research a lead without changing external state\n\n1. Ask SalesTouch to look up a profile URL.\n2. Ask for the profile's recent posts.\n3. Ask the agent to summarize useful context and draft a message.\n4. Review the draft; no message is sent until a mutation tool is authorized.\n\n### 2. Review a conversation and send an exact reply\n\n1. Search the conversation by profile URL.\n2. Read the bounded message history.\n3. Ask the agent to draft a reply without sending.\n4. Confirm the recipient and exact text, then authorize `linkedin_message`.\n\n### 3. Build a Sales Navigator audience from structured filters\n\n1. Resolve ambiguous filter values with `linkedin_sales_navigator_search_parameters`.\n2. Run `scrape_sales_navigator_companies` or `scrape_sales_navigator_people` with the returned ids.\n3. To restrict people to extracted companies, pass the company `result_id` to `scrape_sales_navigator_people` as `company_result_id`.\n4. Inspect the bounded preview, page with `scrape_result_page`, or use the signed CSV/JSONL export.\n\n### 4. Turn post engagement into a paginated result\n\n1. Provide a LinkedIn post URL.\n2. Run `scrape_linkedin_post_reactions` or\n   `scrape_linkedin_post_comments`.\n3. Read the bounded preview and stored result id.\n4. Continue with `scrape_result_page` until the result is complete.\n\n## Safety and limitations\n\n- Read tools are non-destructive and idempotent.\n- Messages, invitations, likes, comments, and publications modify LinkedIn and\n  are non-idempotent.\n- These write tools accept `scheduled_for`; SalesTouch persists the action and\n  reconnects a sleeping credential-based account when execution becomes due.\n- Cancelling a queued action modifies SalesTouch state and cannot be assumed\n  idempotent.\n- Availability depends on an active SalesTouch plan, a connected LinkedIn\n  account, platform availability, permissions, and usage limits.\n- SalesTouch does not bypass LinkedIn safeguards. Users are responsible for\n  reviewing targets and content and for complying with applicable platform\n  rules and law.\n\n## Troubleshooting\n\nIf OAuth fails, reconnect from the MCP client, confirm the endpoint, verify the\nSalesTouch plan and connected account, then retry the read-only account check.\nNever paste credentials, cookies, OAuth tokens, private messages, or prospect\ndata into a support request.\n\n## Documentation and support\n\n- [Documentation](https://www.salestouch.io/docs)\n- [Getting started](https://www.salestouch.io/docs/getting-started)\n- [Authentication and scopes](https://www.salestouch.io/docs/authentication)\n- [Troubleshooting](https://www.salestouch.io/docs/troubleshooting)\n- [OpenAI plugin submission](OPENAI_PLUGIN_SUBMISSION.md)\n- [Claude directory submission](CLAUDE_DIRECTORY_SUBMISSION.md)\n- [Support](SUPPORT.md)\n- [Security](SECURITY.md)\n- [Privacy](https://www.salestouch.io/privacy)\n- [Terms](https://www.salestouch.io/terms)\n- Email: [support@salestouch.io](mailto:support@salestouch.io)\n\nThe files in this public distribution wrapper are licensed under the\n[MIT License](LICENSE). The hosted SalesTouch backend remains proprietary.\n",
  "bytes": 4808,
  "sha": "b3460662170ff7bb8de403cac2b5cd168fe6cbd5940b7986beaefa4f5821a59a",
  "repo_slug": "antoinedsh/salestouch",
  "fonte": "repo",
  "truncated": false,
  "api": "https://agentalog.com/api/listings/mcp_io_salestouch_salestouch_a4a09eae/readme"
}