Skip to main content
This page covers the most common issues you might run into with Groovin MCP and how to resolve them quickly. Most problems fall into one of three categories: configuration, authentication, or LinkedIn session state. Work through the relevant section below, and if you’re still stuck, visit groovin.ai to contact support.
This is almost always a configuration or restart issue. Work through the following steps:
  1. Check the config file — make sure the Groovin MCP connector entry has been added correctly and that the file has been saved.
  2. Restart your AI platform — Claude Desktop, Cursor, Windsurf, and similar tools read the MCP config at startup. Any change to the config won’t take effect until you fully quit and reopen the application.
  3. Verify your API key (if using one) — open the config file and confirm the GROOVIN_API_KEY value is correct. Watch out for accidental extra spaces, surrounding quotes, or line breaks that can silently break the key.
  4. Confirm the tools are loaded — ask your assistant: “What MCP tools do you have access to?” You should see a list that includes Groovin tools such as get_linkedin_chat_messages and lookup_crm_contacts. If the list is empty or Groovin tools are absent, the connector is not loaded.
Your Groovin API key may have expired or been regenerated since you last set up the connector. To get a fresh key:
  1. Go to groovin.ai → Settings → MCP and copy your current API key.
  2. Update the GROOVIN_API_KEY value in your MCP config file with the new key.
  3. Save the config file and fully restart your AI platform.
API keys are tied to individual Groovin accounts. If a team member originally set up the connector, they need to use their own API key — you cannot share keys across accounts.
If every Groovin request suddenly fails, even in the middle of a conversation where it was working fine, your connection has most likely expired: some AI tools don’t refresh it on their own. This is not a Groovin outage and not a LinkedIn restriction. Make sure you’re logged into Groovin, reconnect the Groovin connector in your AI tool’s connector settings, then carry on.If your assistant reports a “Groovin connector problem”, follow the message: it says exactly what needs fixing (your LinkedIn account link, your CRM connection, or your subscription).
Groovin reads from your LinkedIn session via the Chrome extension. If tools return empty results or errors, check each of the following:
  1. The Groovin Chrome extension is installed and pinned — if it’s missing or disabled, Groovin has no way to access your LinkedIn session.
  2. You are logged into LinkedIn in the same browser — Groovin reads from an active LinkedIn session. If you’ve logged out from LinkedIn then you’ll need to log in again and reconnect LinkedIn to Groovin.
  3. The extension shows as “connected” — open your Groovin dashboard and check that the extension status shows as connected, not disconnected or paused.
If you recently installed the extension, give it a few seconds to initialise the session before running your first prompt.
Before creating contacts, always check which ones already exist. Run lookup_crm_contacts on the full batch first — only pass the profiles that come back exists: false into create_crm_contacts. Creating without that lookup step is the main cause of duplicate CRM records.If create_crm_contacts still fails after confirming the contact doesn’t exist, check the following:
  • Your CRM is connected in Groovin settings — go to groovin.ai → Settings → Integrations and confirm that Attio, HubSpot, or Affinity is connected.
  • Your OAuth token hasn’t expired — CRM OAuth tokens periodically expire. If the integration shows as connected but writes are failing, disconnect and reconnect your CRM to refresh the token.
  • Batch size is 25 or fewer — create_crm_contacts accepts a maximum of 25 profiles per call. Split larger sets across multiple calls, and wait between them (see rate limits below).
Message sync is enabled at contact-creation time via create_crm_contacts (with sync_messages: true or your org’s default preference) or via toggle_linkedin_sync.After enabling the sync, allow a few seconds before checking the CRM record for new messages. If messages still aren’t appearing after 1 minute, verify the extension is showing as connected in the Groovin dashboard. You can audit which contacts are actively syncing with list_synced_crm_contacts.
Reading your inbox (list_linkedin_conversation_attendees, get_linkedin_chat_messages) carries no LinkedIn limit. The other LinkedIn tools make live requests through your account, and LinkedIn enforces strict per-account limits and actively detects automation. If you hit a 429 or a rate-limit error:
  • Wait, then retry. For most read tools, wait several minutes before resuming. For get_linkedin_profile (the most tightly capped read, around 100 profile views a day), back off for longer.
  • Keep sends human-paced — send_linkedin_message and send_linkedin_invitation are the most restricted actions (roughly 100 messages a day, 80–100 invitations a day and about 200 a week). Send one at a time and never in sequences.
  • Split create_crm_contacts batches — max 25 profiles per call. Between batches, wait ~30 seconds when message sync is off, or 2–5 minutes when sync is on.
  • Don’t re-poll list_linkedin_relations on a schedule. Pull it a few times a day at randomly-spaced intervals and use connected_after to fetch only what’s new.
  • Avoid parallel bulk prompts — running multiple large imports simultaneously is more likely to trigger limits.
Repeatedly hitting rate limits in a short window can temporarily affect your LinkedIn session. Sustained over-use risks LinkedIn throttling or account restriction, so err on the side of pacing your requests.
It may have been. Don’t ask your assistant to send it again straight away. Ask it to check first: the conversation for a message, or your pending invitations for a connection request. Resend only if it isn’t there.
find_linkedin_profile_url and find_company_domains only write when they are sure of the match, so these answers are frequent and are not errors. Nothing is written to your CRM in either case.
  • For a contact — “not found” doesn’t mean the person isn’t on LinkedIn. Add what’s missing on the CRM record (first name, last name, company), then try again. “Ambiguous” means several people share the name.
  • For a company — give the name and LinkedIn URL of someone who currently works there. It’s the most reliable way to tell companies with similar names apart.
  • Large clean-ups — work in batches of 5 to 10 contacts and spread them over several days. If a batch comes back partly unprocessed, ask your assistant to run only the remaining records later.
Finding LinkedIn URLs, company domains and emails uses Groovin credits. When they run out, the records already processed are kept and the rest are left untouched. Check your credits in your Groovin account, or contact the Groovin team (support@groovin.ai).
  • Possible duplicates — when someone with the same name is already in your CRM and Groovin can’t confirm it’s the same person, nothing is created for that row. Ask your assistant for the rows that need attention and settle them in your CRM.
  • It’s taking a long time — an import runs in the background at roughly 25 minutes per 2,400 connections. You get an email when it’s done; asking for progress more often doesn’t speed it up.
  • “An import is already running” — only one import runs at a time. Wait for it to finish, or ask your assistant to check its progress.
  • The preview can’t be run anymore — import data is kept for 72 hours. After that, upload the file again.
  • Your CRM isn’t supported — the connections import works with Attio and HubSpot.
To revoke LinkedIn access:
  • Go to groovin.ai → Settings and disconnect your LinkedIn account.
To revoke CRM access:
  • Go to groovin.ai → Open app → CRM and click Revoke CRM connection.
Both actions stop all sync immediately. Your existing data in the CRM is not affected — Groovin does not delete or modify records when you disconnect.
If your issue isn’t covered here, visit groovin.ai or email the Groovin support team (support@groovin.ai). Include your account email and a description of the tool call or prompt that failed — this helps the team reproduce and resolve your issue faster.