Quibbly LinkedIn Inbox MCP

Kết nối Claude và ChatGPT với hộp thư đến LinkedIn của bạn. Nghiên cứu các liên hệ và soạn thảo các câu trả lời được con người xem xét.

Máy chủ MCP được lưu trữ

npx add-mcp 'https://server.quibbly.co/mcp'

Cài vào Claude Code, Codex, Cursor và nhiều công cụ khác

Tài liệu

Connect Claude, ChatGPT, Cursor or any MCP client to your LinkedIn inbox as Quibbly sees it: every synced conversation, your connections, who watched your videos and for how long, notes, tags, follow-ups and teleprompter scripts. An assistant can answer questions about all of it, keep it organised, and prepare replies and first messages. Every message waits in your Quibbly drafts queue until you send it.

https://server.quibbly.co/mcp

Remote MCP server over Streamable HTTP. Sign-in is OAuth 2.1 with PKCE, so you approve access on quibbly.co and never paste a password into an assistant.

Before you start

  • A Quibbly account on Solo Pro or any team plan. See pricing.
  • The Quibbly extension with Inbox turned on. The extension syncs your LinkedIn conversations and connections into Quibbly; the assistant reads that copy.
  • Extension 1.4.1 or later for connections and first messages to people you have never messaged.

Connect

  1. 1 Claude (web, desktop and mobile): Open Settings → Connectors. Find Quibbly in the directory, or choose Add custom connector and paste the URL above. Click Connect, sign in to Quibbly if asked, review the permissions and approve. Connectors added on the web also work in Claude Desktop and the mobile apps.
  2. 2 Claude Code: Run claude mcp add --transport http quibbly https://server.quibbly.co/mcp, then type /mcp in Claude Code and choose Quibbly to sign in.
  3. 3 ChatGPT: Settings → Connectors → Create, paste the URL, and approve on the Quibbly page.
  4. 4 Cursor: Settings → MCP → Add new server, transport HTTP, paste the URL, and approve on the Quibbly page.
  5. 5 Other MCP clients: Use OAuth if the client supports it. Otherwise create a personal token in Settings → Assistants and send it as Authorization: Bearer <token>.

On the approval page you see which assistant is asking and exactly what it will be able to do, and you can untick any permission before you approve.

What to ask

  • “Who is waiting on a reply from me, and what did each of them last say?”
  • “Who watched my pricing video this week but has not replied? Draft a short follow-up for each.”
  • “Draft an intro to everyone I connected with this month who runs a sales development team.”
  • “Summarise my conversation with Priya and set a follow-up for Thursday.”
  • “Tag everyone who asked for a demo this week as Demo requested.”
  • “Log my new LinkedIn messages into HubSpot.”
  • “For my Salesforce opportunities closing this month, who has gone quiet on LinkedIn?”

Example: first messages to new connections

Ask “draft an intro to everyone I connected with this month who runs a sales development team”. The assistant lists your recent connections, reads each headline, and queues a first message for each match. Each one waits in your drafts with the person's photo and a New message label until you send it.

Works with any CRM

Quibbly does not need its own CRM integration. Connect Quibbly and your CRM (HubSpot, Salesforce, Pipedrive, Attio or any other CRM with a Claude connector) in the same Claude account, and Claude uses both in one conversation:

  • CRM to LinkedIn. “For my HubSpot deals in Proposal sent, what did each contact last say on LinkedIn? Draft a nudge for the quiet ones.” Claude reads the deals in your CRM, finds each person's LinkedIn thread in Quibbly, and queues drafts for you to send.
  • LinkedIn to CRM. “Log this week's LinkedIn messages into Salesforce.” Claude pulls only what is new since the last sync, matches each person to a CRM record, and logs the conversation there.
  • Call prep. “I have a call with Priya in an hour. Summarise our LinkedIn conversation and her deal.”

Quibbly remembers which CRM record each person maps to (link_contact) and how far each conversation has been logged (mark_synced), so repeat syncs are fast and never log a message twice. The Sync to CRM prompt runs the whole routine.

See the setup and example prompts for your CRM on the integrations page: HubSpot, Salesforce, Pipedrive, Zoho CRM, Attio, Notion and more.

Tools

31 tools. Read tools only read Quibbly's copy of your data. Tools marked Changes Quibbly edit your Quibbly records (drafts, notes, tags, follow-ups, scripts); Claude asks you before it runs one. No tool sends a LinkedIn message.

Inbox and contacts

list_conversations Read

Synced conversations, newest activity 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 Read

Full-text search across synced messages and contacts: names, headlines and companies.

read_conversation Read

One thread, oldest first: messages, voice-note transcripts, the Quibblys sent in it and whether they were watched, open follow-ups, the pending draft, and notes on the person.

get_contact Read

One person: profile, CRM links, tags, notes, follow-ups, every Quibbly you sent them and its outcome. On team plans, whether a teammate is already in touch. Look up by name, profile URL or CRM id.

recent_messages Read

A flat feed of messages across the inbox, newest first. Can return only what is new since the last sync to a CRM.

list_connections Read

Your LinkedIn connections, newest first, including people you have never messaged. Filter by when you connected, words in the name, headline or company, and whether you have messaged them.

list_follow_ups Read

Follow-up reminders: overdue, due today, due this week, or all open.

list_tags Read

Your CRM tags.

sync_status Read

How fresh the data is: when the extension last reported, whether it is online, whether Inbox sync is on, pending drafts.

Videos and engagement

who_watched Read

Viewers of one video or of your whole library: watch percent, watch time, plays, where they watched from, and whether they replied. Anonymous viewers are counted, not listed.

list_library Read

Your videos and voice notes with send, seen and reply counts. Search covers names and what you say in each video.

get_library_item Read

One video or voice note in full: transcript, share link, and everyone you sent it to.

find_attachments Read

Everything that can go on a draft: videos and voice notes, files kept with snippets, and files and images from your LinkedIn conversations.

list_quick_replies Read

Your saved snippets with their shortcuts and placeholders.

Drafts

draft_reply Changes Quibbly

Proposes one message: a reply in a conversation, or a first message to a connection. Text, an attachment, or both. It waits in your Quibbly drafts queue until you send it. It can be timed to show on a later day, up to 30 days out. Nothing is sent by this tool.

withdraw_draft Changes Quibbly

Removes a draft before anyone sends it.

list_drafts Read

Drafts an assistant proposed and what happened to each: ready, sent, skipped, expired or failed.

upload_attachment Changes Quibbly

Stores a file (PDF, image, document, up to 8 MB) for 24 hours so a draft can carry it.

Organise

set_follow_up Changes Quibbly

Creates a follow-up reminder on a conversation, or moves an existing one.

complete_follow_up Changes Quibbly

Closes an open follow-up as done or cancelled.

add_note Changes Quibbly

Adds a note on a person. Private by default. On team plans it can be shared with your team and mention teammates, when you ask.

update_note Changes Quibbly

Edits one of your own notes: text, visibility and mentions.

delete_note Changes Quibbly

Deletes one of your own notes.

set_tags Changes Quibbly

Adds or removes tags on a person. New tags are created as needed.

Team and teleprompter

list_team_members Read

Your teammates' names, so a note can mention the right person.

list_scripts Read

Teleprompter scripts you can record with: team scripts with their requirement, then your own.

get_script Read

One teleprompter script in full.

save_script Changes Quibbly

Creates or edits one of your personal teleprompter scripts. Team scripts stay read-only.

CRM sync

link_contact Changes Quibbly

Remembers which record a person is in another system (HubSpot, Salesforce, Attio or any other), so later lookups skip the search.

mark_synced Changes Quibbly

Records how far a conversation has been logged into another system, so the next sync only returns what is new.

request_sync Changes Quibbly

Asks your extension to refresh your inbox now, if a LinkedIn tab is open. At most once every 3 minutes.

Prompts

Ready-made prompts your assistant can offer, for example from the + menu in Claude.

  • Morning brief: Who to reply to, who watched and went quiet, and what is due today, grouped by urgency.
  • Reply in my voice: Reads one conversation and a few of your recent messages, then drafts a reply in your tone for you to approve.
  • Sync to CRM: Logs new LinkedIn messages into a CRM you have also connected, one note per conversation, remembering record ids for next time.

Permissions

You choose these on the approval page. A tool whose permission you did not grant answers with an error that names the missing permission.

Read your inbox

inbox:read

Synced conversations and messages, your LinkedIn connections, contacts, follow-ups, tags, your notes and the notes teammates share with the team, teammates' names, and your teleprompter scripts.

Read engagement

engagement:read

Who watched your videos, for how long, and who replied.

Propose replies and organise

crm:write

Draft messages for you to send, set and complete follow-ups, add, edit and delete your notes, tags, CRM links and your personal teleprompter scripts. Never sends anything.

What an assistant cannot do

  • Send a LinkedIn message. Every draft, including one timed for a later day, waits for you to send it with one click.
  • Connect to LinkedIn. Every read is served from Quibbly's synced copy.
  • Read a teammate's private notes, change a teammate's notes, or edit team scripts.
  • Change your plan, billing, account settings or team.
  • Go past its limits: reads, changes and drafts are rate limited per connection.

Freshness is always visible

Every response includes how old the data is and whether your extension is online, so the assistant can tell you when it is working from an older copy.

Data and privacy

  • An assistant sees only what the permissions you approved allow, and only for your own account.
  • Quibbly receives the requests the assistant makes (the tool and its inputs), not your chat with the assistant. We never read your assistant conversations, memory or files.
  • Every request is listed under Activity in Settings → Assistants, kept for 90 days.
  • We never sell your data or use it to train AI models.
  • Disconnect one assistant, delete a personal token, or use Revoke all access in the same place. Access ends immediately.

Full details are in the privacy policy.

Troubleshooting

The approval page says assistant access is part of Solo Pro

Assistants are included with Solo Pro and every team plan. Upgrade on the billing page, then connect again.

The assistant says there are no conversations, or the data is old

Quibbly reads the copy your extension syncs. Install the Quibbly extension, turn on Inbox in the Quibbly sheet on LinkedIn, and keep a LinkedIn tab open for the first sync. Every answer includes synced_ago and extension_online; ask the assistant to call request_sync for a fresh pull.

Drafts do not show up in my inbox

Open the Quibbly sheet on LinkedIn and check the Drafts section. First messages to new connections need extension 1.4.1 or later. The queue holds 20 ready drafts; send or skip some to make room. Drafts expire 7 days after they show.

Rate limit reached

Each connection can make 120 reads, 30 changes and 20 drafts a minute. The error says how many seconds to wait.

Authorization failed or the connection stopped working

Disconnect Quibbly in your assistant and connect again. If it was revoked from Quibbly's side, or your plan changed, a new approval fixes it. Still stuck? Email [email protected] with the assistant you use and the time it failed.