Skip to main content
Connect FirstTouch to your AI assistant so you can build lists, launch flows, enrich prospects, check queues, review metrics, and track work inside the tools you already use. Choose browser OAuth for interactive clients or an API key for clients with secure custom-header support. With browser OAuth, your MCP client should open a browser window for sign-in and approval automatically.
Full FirstTouch MCP tools require an active paid plan or active trial. A Free Team can connect, but it can use only basic account, billing, and static reference tools. Creating MCP Dynamic Actions requires Team Admin permissions.

​
Browser OAuth Setup

1

Copy the MCP server URL

Copy the MCP server URL shown in FirstTouch.
2

Add a remote server connection

Open your MCP client and add a remote server connection.
3

Paste the URL

Paste the MCP server URL into your client.
4

Complete sign-in

Complete FirstTouch sign-in and approve the Team in your browser when prompted.
5

Start using FirstTouch

Return to your client and start using FirstTouch.
Example MCP server URL:
Use the exact URL shown in FirstTouch. MCP access is authorized for the Team you approve during sign-in.

​
API-Key Setup

Use an API key for server integrations or MCP clients that support custom HTTP headers.
  1. Open Settings > MCP & API in FirstTouch.
  2. Create and securely save a Public API key.
  3. Configure the MCP client to send this header to the FirstTouch MCP server:
The connection uses the key’s fixed team and the creator’s current permissions. See Public API Keys for rotation, revocation, and security guidance.
Never paste a real API key into a chat prompt, repository, screenshot, or client-side application. Use the MCP client’s secure header or secret configuration.

​
One-Prompt Setup By Client

The fastest path: paste one prompt and your assistant walks itself through connecting the MCP, asks you to pick a role pack (RevOps, Founder, AE, or BDR), loads the plays, and recommends three to start with.
Paste into any Claude.ai chat (or use Settings → Connectors to add the URL manually):

​
Multiple Teams

If you manage more than one FirstTouch Team, add one MCP connection per Team. Give each connection a clear name, such as firsttouch-main and firsttouch-client-a, and approve the right Team during sign-in. Then include the connection name in your prompt:
Use firsttouch-client-a and show pending approval tasks.
If you switch teams in FirstTouch, reconnect or add another MCP connection for that team before asking your assistant to work there.

​
Manage Connections

FirstTouch settings can show connected MCP clients for your Team. Use this list to review the client name, client ID, redirect URI, last-used time, and active status when available. Revoking a connected MCP client removes that client’s authorization to use FirstTouch. It does not disconnect your email, LinkedIn, HubSpot, or other Connected Accounts.

​
Verify The Connection

After setup, ask your assistant one of these:
  • “Show my current FirstTouch user.”
  • “List my FirstTouch audiences.”
  • “List my recent Flow Plans.”
  • “Show my FirstTouch credit balance.”
  • “Show active LinkedIn outreach waiting to run.”
  • “Show team metrics for the last 30 days.”
  • “Show my pending FirstTouch tasks.”
If the connection works, the assistant should return information from the approved FirstTouch Team.

​
Agent References

If your assistant needs more context, point it to llms.txt for a docs map or skill.md for MCP workflow guidance.