Quibbly LinkedIn MCP server
Commit Oct 20, 2026Connects your LinkedIn inbox to AI assistants to read conversations, track video engagement, and draft replies that sync with your CRM.
Also known as Scriptify-Inc/linkedin-mcp
- Stars
- 1
- Tools
- 34
- Downloads, 30 days
- —
- Latest version
- —
- Last commit
- Oct 20, 2026
- License
- MIT
What is Quibbly LinkedIn MCP?
Quibbly LinkedIn connects your LinkedIn inbox to AI assistants to read conversations, track video engagement, and draft replies that sync with your CRM. It exposes 34 tools, such as inbox, engagement, crm.
Summary generated from the project's README
About Quibbly LinkedIn MCP server
Sales professionals and recruiters can manage their LinkedIn communications directly from AI assistants like Claude, Cursor, or ChatGPT. This hosted MCP server connects your LinkedIn inbox to your preferred AI client, allowing you to read conversations, track video engagement, and manage connections without leaving your chat interface. Because it is a hosted service using streamable HTTP and OAuth 2.1, there is no local installation required.
The server operates by reading a synced copy of your inbox maintained by a Chrome extension, ensuring the AI never logs into your account directly. It provides tools to search messages, list connections, and analyze video transcripts to see who watched your content and for how long. Instead of sending messages automatically, the server uses a draft-only workflow where the AI proposes replies that appear in a Quibbly sheet for you to review and send manually.
Integration with CRM platforms like HubSpot and Salesforce allows for advanced workflows. You can sync LinkedIn direct messages to your CRM, match contacts, and prepare for calls by pulling deal information alongside recent conversation history and video watch metrics.
What you can do with it
- 1Automate personalized outreachAsk your assistant to write introductory messages to all new connections from a specific month based on their job title.
- 2Prepare for sales callsCombine CRM data with LinkedIn history to get a complete briefing on a prospect before a meeting.
- 3Follow up with video insightsDraft replies that include specific video content based on the transcript of what was discussed.
- 4Synchronize communication historyAutomatically log your LinkedIn direct messages into your CRM to keep contact records up to date.
Written from the project's README. Every use case is checked against a quote from it.
Quibbly LinkedIn MCP tools 34
Detected from the READMEinboxengagementcrmlist_conversationssearch_messagesread_conversationget_contactrecent_messageslist_connectionslist_follow_upslist_tagssync_status
| inbox | — | |
| engagement | — | |
| crm | — | |
| list_conversations | — | |
| search_messages | — | |
| read_conversation | — | |
| get_contact | — | |
| recent_messages | — | |
| list_connections | — | |
| list_follow_ups | — | |
| list_tags | — | |
| sync_status | — |
Show all 34 toolsShow fewer tools
who_watchedlist_libraryget_library_itemfind_attachmentslist_quick_repliesdraft_replywithdraw_draftlist_draftsupload_attachmentset_follow_upcomplete_follow_upadd_noteupdate_notedelete_noteset_tagslist_team_memberslist_scriptsget_scriptsave_scriptlink_contactmark_syncedrequest_sync
| who_watched | — | |
| list_library | — | |
| get_library_item | — | |
| find_attachments | — | |
| list_quick_replies | — | |
| draft_reply | — | |
| withdraw_draft | — | |
| list_drafts | — | |
| upload_attachment | — | |
| set_follow_up | — | |
| complete_follow_up | — | |
| add_note | — | |
| update_note | — | |
| delete_note | — | |
| set_tags | — | |
| list_team_members | — | |
| list_scripts | — | |
| get_script | — | |
| save_script | — | |
| link_contact | — | |
| mark_synced | — | |
| request_sync | — |
Automated checks
Ran Nov 14, 2026Full report →Not verified yet. A server needs a score of 80, no serious finding, and enough data for us to check. How checks work · What to fix for more points
- Source repository linked and reachablescriptify-inc/linkedin-mcp is public and reachablegithub.com/scriptify-inc/linkedin-mcp ↗Pass
- Package names this repository as its sourceNot checked
- Build provenance (Sigstore attestation)Not checked
- Open source license (OSI)MITspdx.org/licenses/MIT.html ↗Pass
- Commit or release in the last yearLast commit or release 2026-10-20github.com/scriptify-inc/linkedin-mcp ↗Pass
- OpenSSF ScorecardNot checked
- Package name not close to a popular packageNot checked
- No critical advisory in the package or its dependenciesNot checked
- No hidden instructions to the model34 tool descriptions and the README read; no override phrases, credential paths or hidden charactersPass
- Destructive tools are labelledNot checked
- Remote endpoint answers the MCP handshakeNot checked
README
View on GitHubThe Quibbly LinkedIn MCP server connects your LinkedIn inbox to Claude and any other MCP client. Claude can read your conversations and connections, see who watched your videos, pull your CRM in beside them, and write messages that wait in Quibbly for you to send.
It is a hosted server, so there is nothing to install or run. You add one URL to your assistant and approve it once:
https://server.quibbly.co/mcp
Watch the 3:50 walkthrough
Setup from sign-up to the first prompt, then four real examples: first messages to new connections, call prep with HubSpot, a follow-up with the right video attached, and syncing LinkedIn DMs into HubSpot.
See it work
One prompt in Claude, and a first message for every new BDR manager lands in the Quibbly sheet on LinkedIn, each with its own Send button. Nothing is sent until you click it.
What you can do
Write first messages to new connections
Write a first message to every BDR manager I connected with this month.
Claude searches your connections, skips anyone you have already messaged, and writes each person a message based on their role and company. Ask it to attach your intro video and every draft carries it.
Prep a call with your CRM beside the conversation
Prep me for my call with Marcus at Brightloop. Use HubSpot and my LinkedIn.
With HubSpot or Salesforce connected too, Claude pulls the deal, reads the whole LinkedIn conversation and checks who watched your videos: the part your CRM never had.
Write the follow-up, with the right video
Write my follow-up to Marcus. Answer his Sales Navigator question and attach my video that shows Sales Navigator.
Claude searches what you say inside your videos, not just their titles, attaches the right one, and drafts the reply beside the conversation on LinkedIn.
Sync your LinkedIn DMs into HubSpot or Salesforce
Sync my LinkedIn DMs into HubSpot.
Claude finds every message that isn't logged yet, matches each person to their CRM contact, creates the missing ones and logs each conversation. Quibbly remembers every match and where it stopped, so the next sync only moves what is new.
How it works
Claude never logs into LinkedIn. The Quibbly extension keeps a private, synced copy of your inbox while you use LinkedIn. Claude reads that copy through the MCP, and anything it writes goes back as a draft into the Quibbly sheet, right next to the conversation, where you send it yourself.
Quick start
About five minutes, start to finish.
- Start Quibbly. Sign up at quibbly.co and pick Solo Pro, the plan with assistant access. The first 3 days are free; a card is needed to start, and if you cancel before the trial ends you pay nothing.
- Add Quibbly to Chrome from the Chrome Web Store, in the Chrome profile you use for LinkedIn.
- Turn on Inbox. Open LinkedIn, click the Quibbly tab on the left edge to open the sheet, and click Turn on Inbox. Your conversations start syncing.
- Connect your assistant with the server URL below, then approve the connection on the Quibbly page that opens.
Connect your assistant
Claude (web, desktop and mobile)
- Open Customize → Connectors, click + Add and choose Add custom connector.
- Name it
Quibblyand pastehttps://server.quibbly.co/mcp, then Add and Connect. - Sign in to Quibbly if asked, review the permissions and click Allow.
Connectors you add on claude.ai also work in the Claude desktop and phone apps.
Claude Code
claude mcp add --transport http quibbly https://server.quibbly.co/mcp
Then run /mcp in Claude Code and choose Quibbly to sign in.
Cursor
Add it in Settings → MCP → Add new server (transport HTTP), or put this in .cursor/mcp.json:
{
"mcpServers": {
"quibbly": {
"url": "https://server.quibbly.co/mcp"
}
}
}
VS Code
.vscode/mcp.json:
{
"servers": {
"quibbly": {
"type": "http",
"url": "https://server.quibbly.co/mcp"
}
}
}
ChatGPT
On chatgpt.com, open Plugins, click + and choose Add custom MCP server. Paste https://server.quibbly.co/mcp, choose OAuth, create and install it, then approve on the Quibbly page that opens. ChatGPT allows custom MCP servers that write (Quibbly writes drafts) on Business and Enterprise plans; on Business, a workspace admin adds it.
Any other MCP client
Any client that supports remote MCP servers over streamable HTTP with OAuth can connect to https://server.quibbly.co/mcp.
If your client can't do the sign-in step, create a personal access token in Quibbly under Settings → Assistants and send it as Authorization: Bearer <token>. For clients that only speak stdio, a bridge such as mcp-remote works:
{
"mcpServers": {
"quibbly": {
"command": "npx",
"args": ["-y", "mcp-remote", "https://server.quibbly.co/mcp"]
}
}
}
Ready-made versions of these files are in examples/.
Prompts to try
| Ask Claude | You get |
|---|---|
| Who is waiting on a reply from me on LinkedIn, and what did each of them last say? | Every open thread, newest first, with the last thing each person said |
| Give me my morning brief: who to reply to, who watched and went quiet, and what is due today. | Three short lists you can clear before your first call |
| Who watched my pricing video this week but has not replied? Draft a short follow-up for each. | The viewers, how much each watched, and a draft for each in your Quibbly sheet |
| Write a first message to every BDR manager I connected with this month. | One draft per new connection, written to their role and company |
| For my HubSpot deals in Proposal sent, what did each contact last say on LinkedIn? | Your pipeline with the LinkedIn side of every deal next to it |
| Tag everyone who asked for a demo this week as Demo requested. | The right people found and tagged |
More in the full guide.
Tools
Claude picks the tools for you, so you never call them by name. 31 tools, in three permission scopes you approve when you connect:
inbox:read: your synced conversations, connections, follow-ups, tags and draftsengagement:read: your videos and voice notes, and who watched themcrm:write: propose replies and organise (drafts, follow-ups, notes, tags, CRM links). Nothing in this scope sends.
| Tool | What it does |
|---|---|
list_conversations |
Synced conversations, newest first. Filter by status (waiting on you, waiting on them, follow-up due, hot, gone quiet, not interested, closed), tag, company or date. |
search_messages |
Full-text search across synced messages and contacts: names, headlines and companies. |
read_conversation |
One thread: messages, voice-note transcripts, the videos you sent and whether they were watched, follow-ups, the pending draft and your notes. |
get_contact |
One person: profile, CRM links, tags, notes, follow-ups and every video you sent them. On team plans, whether a teammate is already in touch. |
recent_messages |
A feed of messages across the inbox. Can return only what is new since the last sync to a CRM. |
list_connections |
Your connections, newest first, including people you have never messaged. Filter by date, words in the headline or company, and whether you have messaged them. |
list_follow_ups |
Follow-up reminders: overdue, due today, due this week, or all open. |
list_tags |
Your tags. |
sync_status |
How fresh the data is, whether the extension is online and whether Inbox sync is on. |
| Tool | What it does |
|---|---|
who_watched |
Who watched one video or your whole library: watch percent, watch time, plays and whether they replied. |
list_library |
Your videos and voice notes. Search covers names and what you say in each video. |
get_library_item |
One video or voice note in full: transcript, share link and everyone you sent it to. |
find_attachments |
Everything a draft can carry: videos, voice notes, snippet files, and files from your LinkedIn conversations. |
list_quick_replies |
Your saved snippets and their placeholders. |
| Tool | What it does |
|---|---|
draft_reply |
Proposes one message: a reply, or a first message to a connection. Text, an attachment, or both. It waits in your Quibbly drafts until you send it. Nothing is sent by this tool. |
withdraw_draft |
Removes a draft before anyone sends it. |
list_drafts |
Drafts and what happened to each: ready, sent, skipped, expired or failed. |
upload_attachment |
Stores a file (up to 8 MB) for 24 hours so a draft can carry it. |
| Tool | What it does |
|---|---|
set_follow_up |
Creates or moves a follow-up reminder. |
complete_follow_up |
Closes a follow-up as done or cancelled. |
add_note |
Adds a note on a person. Private by default; on team plans it can be shared with your team. |
update_note |
Edits one of your notes. |
delete_note |
Deletes one of your notes. |
set_tags |
Adds or removes tags on a person. |
| Tool | What it does |
|---|---|
list_team_members |
Your teammates' names, so a note can mention the right person. |
list_scripts |
Teleprompter scripts you can record with. |
get_script |
One teleprompter script in full. |
save_script |
Creates or edits one of your personal teleprompter scripts. |
| Tool | What it does |
|---|---|
link_contact |
Remembers which HubSpot, Salesforce, Attio or other record a person is, so later lookups skip the search. |
mark_synced |
Records how far a conversation has been logged into a CRM, so the next sync only returns what is new. |
request_sync |
Asks your extension to refresh your inbox now, if a LinkedIn tab is open. |
Safe for your LinkedIn account
LinkedIn doesn't allow automation, so Quibbly is built so that nothing automated ever runs on your account:
- No bots, no auto-sending, no auto-connecting. None of the 31 tools can send a message, a connection request or a post.
- You click Send on every message, exactly as if you had typed it. Each draft has its own Send button; there is no send-all.
- Claude never touches LinkedIn. It reads the copy your extension already synced. The extension syncs gently in the background and backs off the moment LinkedIn asks it to.
- You stay in control. Every request an assistant makes is listed in Quibbly under Settings → Assistants, where you can disconnect any assistant or revoke all access at once. Reads and writes are rate limited per connection.
Pricing
The LinkedIn MCP is included in Solo Pro ($39 a month) and every team plan. Every plan starts with a 3 day free trial; a card is needed to start, and if you cancel before the trial ends you pay nothing. See all plans.
FAQ
Links
- Full guide with video: quibbly.co/linkedin-mcp
- Docs, permissions and troubleshooting: quibbly.co/docs/mcp
- Walkthrough on YouTube: youtube.com/watch?v=xkXJ8pm3af8
- Official MCP Registry:
co.quibbly/linkedin-inbox(metadata inserver.json) - Support: quibbly.co/support
License
The docs and example configs in this repository are MIT licensed. The Quibbly service itself is covered by the Quibbly terms.
Quibbly LinkedIn MCP questions
What tools does Quibbly LinkedIn MCP provide?
It exposes 34 tools, including inbox, engagement, crm, list_conversations, search_messages.
Does this server send messages automatically?
No, it only creates drafts. Nothing is sent until you manually click the Send button in the Quibbly sheet.
How does the server access my LinkedIn account?
The server does not log into LinkedIn directly. Instead, a Chrome extension keeps a private, synced copy of your inbox which the AI reads through the MCP.
Can I use this with HubSpot or Salesforce?
Yes, the server can pull deal information from HubSpot or Salesforce and sync your LinkedIn DMs into those CRMs.