Connect Claude to LinkedIn with FirstTouch

Connect Claude to LinkedIn through the FirstTouch MCP server at https://mcp.firsttouch.ai. Add FirstTouch as a custom connector in Claude, authenticate your account, and check which team and sender the connection can use. You can then plan prospecting, qualification and conversation workflows around the tools available to that account. HubSpot is optional for this starting path.

What you need before connecting

Sign in to the FirstTouch team you intend to use. Identify the person whose LinkedIn account should perform the work, and confirm that their account is connected and ready for the intended action. Do not assume the person chatting with Claude is automatically the correct sender.

For a shared team, agree on who can prepare outreach, who reviews it, and who owns the relationship. Product builders and agencies should also confirm their account access and permitted client setup with FirstTouch before extending a pilot to several customers.

Check your plan and available credits for the workflow you want to use. Connecting an assistant does not make every paid feature available or make prospect discovery free. Use current pricing and the requirements of the specific feature when estimating costs.

How to connect Claude to LinkedIn

1. Create or sign in to FirstTouch. Start at FirstTouch signup. Use the intended team and connect the LinkedIn sender you plan to use.
2. Open Claude's connector settings. In Claude, open Customize, then Connectors. On an individual account, use Add and choose Add custom connector where available. On a managed workspace, an authorized owner may need to add the connector for your organization first; members then connect their own account.
3. Enter the FirstTouch server URL. Name the connector FirstTouch and use https://mcp.firsttouch.ai. Complete the sign-in and authorization flow for the intended FirstTouch account. Do not paste passwords or API keys into a chat.
4. Check the connection before outreach. Use the read-only FirstTouch setup walkthrough to inspect the caller, team, reported scopes and sender capabilities. Resolve missing access or an unexpected sender before continuing.
5. Choose one workflow and its review policy. Read the guidance for that workflow before creating actions. Keep your first pilot small, with an agreed recipient, sender, message and review step.

Claude's interface and organizational controls can vary. Anthropic's custom connector guide explains the current setup path. There is no fixed setup-time promise: account verification, administrator access and sender readiness can add steps.

What should you check first?

Start with information you can inspect without creating outreach. The linked setup walkthrough covers six authenticated MCP reads tested on September 15, 2026. It checks identity, reported permissions, team members and current guides. It does not test delivery, approval gating or an HTTP integration.

Write down the intended team, the sender's exact user ID, any warnings, and the account capabilities returned. A recognizable display name is not enough when several team members or client accounts are involved. If the expected sender is unavailable, fix that setup instead of letting the assistant substitute someone else.

What can you build with the connection?

FirstTouch provides tools for prospect discovery, qualification, outreach workflows and LinkedIn conversations. Use the operation catalog to check the exact action, inputs and access requirements for your use case.

• Prepare a relevant prospect list. Define who could buy, why they fit, and who should be excluded before choosing a source or spending discovery credits.
• Work from engagement context. Review captured likes and comments from supported monitored sources, then assess the person and post before deciding on follow-up. Engagement alone is not proof of buying intent.
• Prepare outreach from the right person. Match the contact to a sender, choose the supported action and confirm its review configuration before proceeding.
• Review conversations. Use the inbox data available to your role and account. Check synchronization and sender context before treating the conversation as current.

For a broader implementation plan, see building a LinkedIn outreach agent with human approval. A workflow for your own team and a product offered to several clients have different access and commercial questions; connector availability alone does not settle those questions.

Set review controls for the action you are using

Decide what requires human review before the assistant prepares an action. Inspect the current controls for Flow Plans, Dynamic Actions or direct inbox replies separately. Do not assume a setting on one surface governs every other route.

For an approval-based pilot, verify that the intended action actually waits for review and that the reviewer can inspect the exact recipient and message. Telling Claude to ask first is useful instruction, but it is not evidence that a product approval gate is configured. The execution and recovery guide explains the operation-specific checks.

Keep four kinds of timing separate

See Social Engagement, Audiences and LinkedIn Unibox for feature prerequisites and current synchronization details. Social monitoring requires eligible paid access, credits and administrator configuration; adding the MCP connector does not enable it automatically.

Do you need HubSpot?

No. The FirstTouch MCP starting path does not require a HubSpot connection. You can assess the available tools and build a workflow for an internal team, a software product or an implementation project without making HubSpot the entry requirement.

If you use HubSpot, configure the supported integration features you need. FirstTouch's product activity history and HubSpot synchronization are separate. HubSpot timeline activity depends on enabled tracking and contact matching. Task sync also depends on the relevant Flow Plan setting, company context and owner mapping. Connecting the portal does not automatically satisfy all of those conditions.

Use the HubSpot task and activity sync guide to verify the expected record. For another system of record, confirm the adapter or application work required; do not assume the native HubSpot behavior applies to it.

Your LinkedIn agent launch checklist

Use these six checks for the first pilot and whenever you change the sender, workflow or integration. Download the one-page checklist (PDF).

1. Identity: record the intended team and exact sender. Resolve any mismatch.
2. Permissions: inspect reported access and account readiness for the specific action.
3. Freshness: record the source and its last observed or synchronized time. Review the original context.
4. Review: check the selected workflow's actual approval configuration and the exact content to be reviewed.
5. Outcome: retain the action receipt and inspect completion. A pending or ambiguous result is not a sent message.
6. CRM, if used: check the expected contact, activity or task in that system. Keep this separate from the FirstTouch result.

Keep a review record for each outreach action

A useful first pilot answers a small question: can your team identify the right sender, review the exact message and explain what happened afterward? Use one agreed contact and one action. Save the evidence as you go, instead of asking the assistant to reconstruct it from a long chat.

The worksheet below is an evaluation aid, not an executable workflow or a list of exact API field names. Copy it into your team's review notes. Leave unknown values blank and resolve them before moving on.

Use status words your team can verify

Drafted means the text is ready to inspect. It does not mean an action exists in FirstTouch. Awaiting review means a required human decision is outstanding. Approved records that decision; it does not establish that the action has run. Queued or pending means there is still execution work to check. Report sent only when the relevant result supports it, and keep any separate CRM confirmation alongside that result.

A status note can be short: “Draft reviewed; approval still pending; no send confirmed.” That is a reporting example, not a customer result or a tool response. It gives the next person a clear place to continue without creating the action again.

What to do when the result is unclear

Keep the original action reference and inspect its latest state before retrying. An assistant's success summary, an empty task list or a delayed page update is not enough to decide that an action failed. If you cannot establish the result, leave it marked unknown and investigate the existing record. Do not create a second outreach action merely to make the chat look complete.

For a team pilot, agree in advance who resolves identity mismatches, who reviews the message and who checks the result. Keep the first review record even after a successful send. It becomes a concrete reference when you change the sender, add a new workflow or connect a system of record.

Start with the read-only MCP setup walkthrough, then use this worksheet with an authorized pilot. Create your FirstTouch account if you have not connected one yet.

A relationship still needs an owner

Sales Assembly uses FirstTouch to make LinkedIn follow-up more consistent. Brad Rosen described moving away from spreadsheet-based tracking while keeping the team's judgment about whom to approach and what to say. That is a useful starting point for an agent project: make the process easier to run while keeping an accountable person close to the relationship. Read the Sales Assembly customer story.

Is it safe to let Claude act on my LinkedIn account?

Yes, when the connection runs through an execution layer built for account health. FirstTouch uses dedicated social agents to simulate human interaction and timing with dedicated proxies to keep your account safe, and you will not get banned if you follow our guide and practice proper safety and agent hours. Claude proposes; the actions you have gated wait at the Human-in-the-Loop approval step before anything sends. Keep pacing at roughly 15 to 20 actions per rep per day, target tightly, and never run two LinkedIn tools on one account.

FirstTouch is SOC 2 Type II certified, and 1M+ actions have been processed under approval, pacing, and audit. The line enforcement actually acts on is not whether a model wrote the message; it is whether the account behaves like a person and whether a human stayed in the loop on the sends that matter. The full rules live in the Safety Checklist and our guide to whether LinkedIn automation is safe.

Frequently asked questions

Can Claude connect to LinkedIn through FirstTouch?

Yes. Add the FirstTouch MCP server at https://mcp.firsttouch.ai as a custom connector in Claude, authenticate, and check the intended team and sender before preparing outreach.

How long does setup take?

Setup time depends on account access, authorization and connected-sender readiness. There is no fixed duration; complete the connection checks before moving to outreach.

Do I need HubSpot?

No. HubSpot is optional for the FirstTouch MCP starting path. Native HubSpot synchronization has its own settings and matching requirements.

Does a successful connection mean a message was sent?

No. Connection checks establish setup information. Creating an action, reviewing it and verifying the final outcome are separate steps.

Will every action wait for approval?

Check the control for the specific workflow and action. Do not assume Flow Plans, Dynamic Actions and direct inbox replies share one universal approval setting.

Can I monitor a single LinkedIn post URL?

Social Engagement monitoring targets supported LinkedIn person profiles or company pages, not individual post URLs. Engagement is pulled daily and can take 24+ hours to appear.