LinkedIn MCP server Let your AI agent run your LinkedIn.

ToolWhat it doesAccess

• list_my_posts Your recent posts with reactions, comment count and date, newest first. read

  Returns posts from your profile activity, newest first. Pass as_page to read the posts of a Company Page you administer. Each post has a post_id for list_post_comments and comment_on_post, and the counts LinkedIn shows under the post. Scheduled posts are listed with status scheduled and their publish time.

  MCP calllinkedin_read → list_my_posts

  REST endpointGET https://cotlet.dev/api/v1/linkedin/my-posts

  Parameters

  Parameters: list_my_posts

  Name	Type	Description
  as_page string	string	Name of a Company Page you administer, to act as that Page. Leave out to act as yourself.
  limit integer	integer	How many results to return. Default: 10.
  cursor string	string	Next page cursor from the previous call.

  Example response

  {
    "posts": [
      {
        "post_id": "p_7390001",
        "text": "Why we dropped the weekly report",
        "status": "published",
        "reactions": 58,
        "comments": 12,
        "posted_at": "2026-11-03T08:00:00Z",
        "url": "https://www.linkedin.com/feed/update/p_7390001"
      },
      {
        "post_id": "p_7390002",
        "text": "Three questions to ask before hiring an agency",
        "status": "published",
        "reactions": 94,
        "comments": 31,
        "posted_at": "2026-10-30T08:00:00Z",
        "url": "https://www.linkedin.com/feed/update/p_7390002"
      }
    ],
    "next_cursor": "c_3"
  }

• list_post_comments Comments on one post, with author, text and whether you replied. read

  Returns the comments under one post in the order LinkedIn shows them, with the commenter name, headline and comment text. replied is true when you already answered that comment. Pass comment_id to comment_on_post to reply in the thread.

  MCP calllinkedin_read → list_post_comments

  REST endpointGET https://cotlet.dev/api/v1/linkedin/post-comments

  Parameters

  Parameters: list_post_comments

  Name	Type	Description
  post_id string required	string	Post ID from list_my_posts.
  limit integer	integer	How many results to return. Default: 10.
  cursor string	string	Next page cursor from the previous call.

  Example input

  {
    "post_id": "post_8c41d2"
  }

  Example response

  {
    "comments": [
      {
        "comment_id": "c_5521",
        "author": "Jonas Weber",
        "headline": "Head of Growth at Example GmbH",
        "text": "How long did the switch take?",
        "replied": false,
        "posted_at": "2026-11-04T09:12:00Z"
      }
    ],
    "next_cursor": null
  }

• create_post Publishes or schedules a post on your profile or a Company Page. writeasks first

  Creates a text post, with a link in the text if you add one. visibility is anyone or connections, and comments is anyone, connections or off, as in the post settings. Set schedule_at to schedule it instead of publishing now. Returns the post_id and the post URL. By default you confirm each call; you can switch that off for this tool.

  MCP calllinkedin_write → create_post

  REST endpointPOST https://cotlet.dev/api/v1/linkedin/posts

  Parameters

  Parameters: create_post

  Name	Type	Description
  text string required	string	Post text.
  visibility enum	enum	anyone or connections. Default: anyone.
  comments enum	enum	Who can comment: anyone, connections or off. Default: anyone.
  schedule_at datetime	datetime	ISO 8601 time to publish at. Leave out to post now.
  as_page string	string	Name of a Company Page you administer, to act as that Page. Leave out to act as yourself.

  Example input

  {
    "text": "Three questions to ask before hiring an agency. 1) Who does the work? 2) How do you report? 3) What happens if we stop?",
    "visibility": "anyone",
    "comments": "anyone",
    "schedule_at": "2026-11-10T09:00:00+01:00"
  }

  Example response

  {
    "post_id": "p_7390010",
    "status": "scheduled",
    "publish_at": "2026-11-10T09:00:00+01:00",
    "url": "https://www.linkedin.com/feed/update/p_7390010"
  }

• comment_on_post Adds a comment to a post, or replies to a comment. writeasks first

  Posts a text comment under a post as you, or as a Company Page you administer. Pass comment_id to reply inside a thread. Returns the new comment_id. By default you confirm each call; you can switch that off for this tool.

  MCP calllinkedin_write → comment_on_post

  REST endpointPOST https://cotlet.dev/api/v1/linkedin/posts/{post_id}/replies

  Parameters

  Parameters: comment_on_post

  Name	Type	Description
  post_id string required	string	Post ID from list_my_posts or a post URL.
  text string required	string	Comment text.
  comment_id string	string	Comment ID from list_post_comments, to reply to that comment.
  as_page string	string	Name of a Company Page you administer, to act as that Page. Leave out to act as yourself.

  Example input

  {
    "post_id": "post_8c41d2",
    "text": "text"
  }

  Example response

  {
    "comment_id": "c_5530",
    "post_id": "p_7390002",
    "status": "published"
  }

ToolWhat it doesAccess

• search_people People search by keywords, with filters for location, current company and connection degree. read

  Runs the LinkedIn people search with the filters you set and returns one page of matches: name, headline, location and connection degree. Results follow the order LinkedIn shows. Use get_profile on a match for the full profile. What you see depends on your account and the connection degree.

  MCP calllinkedin_read → search_people

  REST endpointGET https://cotlet.dev/api/v1/linkedin/peoples/search

  Parameters

  Parameters: search_people

  Name	Type	Description
  keywords string required	string	Search words, for example a job title.
  location string	string	Place name as LinkedIn shows it in the Locations filter.
  company string	string	Current company name.
  connection_degree enum	enum	1st, 2nd or 3rd. Default: all.
  limit integer	integer	How many results to return. Default: 10.
  cursor string	string	Next page cursor from the previous call.

  Example input

  {
    "keywords": "keywords"
  }

  Example response

  {
    "people": [
      {
        "name": "Anna Keller",
        "headline": "Head of Marketing at Example Software",
        "location": "Berlin, Germany",
        "connection_degree": "2nd",
        "url": "https://www.linkedin.com/in/anna-keller-example"
      },
      {
        "name": "Lukas Brandt",
        "headline": "Head of Marketing at Sample Cloud",
        "location": "Berlin, Germany",
        "connection_degree": "3rd",
        "url": "https://www.linkedin.com/in/lukas-brandt-example"
      }
    ],
    "next_cursor": "c_2"
  }

• search_companies Company search by keywords, with filters for location and industry. read

  Runs the LinkedIn company search and returns one page of Company Pages: name, industry, size range as LinkedIn shows it, location and follower count. Use the company name in search_people to find the people who work there.

  MCP calllinkedin_read → search_companies

  REST endpointGET https://cotlet.dev/api/v1/linkedin/companies/search

  Parameters

  Parameters: search_companies

  Name	Type	Description
  keywords string required	string	Search words, for example a product category.
  location string	string	Place name as LinkedIn shows it in the Locations filter.
  industry string	string	Industry name as LinkedIn shows it in the Industry filter.
  limit integer	integer	How many results to return. Default: 10.
  cursor string	string	Next page cursor from the previous call.

  Example input

  {
    "keywords": "keywords"
  }

  Example response

  {
    "companies": [
      {
        "name": "Sample Freight Software",
        "industry": "Software Development",
        "size": "51-200 employees",
        "location": "Rotterdam, Netherlands",
        "followers": 4210,
        "url": "https://www.linkedin.com/company/sample-freight-software"
      }
    ],
    "next_cursor": null
  }

• get_profile A member profile: name, headline, location, current role, about text and mutual connections. read

  Opens one member profile as you see it while signed in. Returns the headline, location, current company and role, the about text and recent positions. connection_degree tells whether the person is a 1st, 2nd or 3rd degree connection, which decides whether send_message or send_invitation fits. Leave profile empty to read your own profile.

  MCP calllinkedin_read → get_profile

  REST endpointGET https://cotlet.dev/api/v1/linkedin/profile

  Parameters

  Parameters: get_profile

  Name	Type	Description
  profile string	string	Profile URL or the part after /in/. Default: your own profile.

  Example response

  {
    "name": "Anna Keller",
    "headline": "Head of Marketing at Example Software",
    "location": "Berlin, Germany",
    "company": "Example Software",
    "connection_degree": "2nd",
    "mutual_connections": 4,
    "about": "I lead demand generation for a B2B software team.",
    "url": "https://www.linkedin.com/in/anna-keller-example"
  }

ToolWhat it doesAccess

• list_connections Your connections, newest first, with headline and the date you connected. read

  Reads My Network, Connections, in the order LinkedIn shows it (recently added first). Each row has the name, headline, profile URL and connected_at. Use search to filter by name, company or title.

  MCP calllinkedin_read → list_connections

  REST endpointGET https://cotlet.dev/api/v1/linkedin/connections

  Parameters

  Parameters: list_connections

  Name	Type	Description
  search string	string	Filter by name, company or title.
  limit integer	integer	How many results to return. Default: 10.
  cursor string	string	Next page cursor from the previous call.

  Example response

  {
    "connections": [
      {
        "name": "Marta Nowak",
        "headline": "Founder at Example Studio",
        "connected_at": "2026-10-28",
        "url": "https://www.linkedin.com/in/marta-nowak-example"
      }
    ],
    "next_cursor": "c_2"
  }

• list_invitations Pending invitations you received or sent, with the note and the date. read

  Reads My Network, Manage invitations. direction is received or sent. Each row has an invitation_id for accept_invitation or withdraw_invitation, the person, their headline, the note if there is one and the date.

  MCP calllinkedin_read → list_invitations

  REST endpointGET https://cotlet.dev/api/v1/linkedin/invitations

  Parameters

  Parameters: list_invitations

  Name	Type	Description
  direction enum	enum	received or sent. Default: received.
  limit integer	integer	How many results to return. Default: 10.
  cursor string	string	Next page cursor from the previous call.

  Example response

  {
    "invitations": [
      {
        "invitation_id": "i_4410",
        "direction": "received",
        "name": "Tom Becker",
        "headline": "Operations Manager at Sample Logistics",
        "note": "Saw your post on reporting.",
        "sent_at": "2026-11-04"
      }
    ],
    "next_cursor": null
  }

• send_invitation Invites a person to connect, with an optional note. writeasks first

  Sends a connection invitation from the person's profile, with a note if you give one. The person gets it in My Network, Manage invitations. It stays pending until they accept or you withdraw it. Returns the invitation_id. By default you confirm each call; you can switch that off for this tool.

  MCP calllinkedin_write → send_invitation

  REST endpointPOST https://cotlet.dev/api/v1/linkedin/invitations

  Parameters

  Parameters: send_invitation

  Name	Type	Description
  profile string required	string	Profile URL or the part after /in/.
  note string	string	Optional note shown with the invitation.

  Example input

  {
    "profile": "profile"
  }

  Example response

  {
    "invitation_id": "i_4502",
    "status": "pending",
    "name": "Anna Keller"
  }

• accept_invitation Accepts an invitation you received, which connects you. writeasks first

  Accepts one received invitation from Manage invitations. The person becomes a connection and LinkedIn tells them. Returns the new connection. By default you confirm each call; you can switch that off for this tool.

  MCP calllinkedin_write → accept_invitation

  REST endpointPOST https://cotlet.dev/api/v1/linkedin/invitations/{invitation_id}/accept

  Parameters

  Parameters: accept_invitation

  Name	Type	Description
  invitation_id string required	string	Invitation ID from list_invitations.

  Example input

  {
    "invitation_id": "invitation_8c41d2"
  }

  Example response

  {
    "invitation_id": "i_4410",
    "status": "accepted",
    "name": "Tom Becker"
  }

• withdraw_invitation Withdraws an invitation you sent that is still pending. write

  Withdraws one sent invitation from Manage invitations. The person is not notified, and one call undoes nothing for anyone else, so it needs no confirmation. LinkedIn does not allow a new invitation to the same person for up to three weeks after a withdrawal.

  MCP calllinkedin_write → withdraw_invitation

  REST endpointPOST https://cotlet.dev/api/v1/linkedin/invitations/{invitation_id}/withdraw

  Parameters

  Parameters: withdraw_invitation

  Name	Type	Description
  invitation_id string required	string	Invitation ID from list_invitations with direction sent.

  Example input

  {
    "invitation_id": "invitation_8c41d2"
  }

  Example response

  {
    "invitation_id": "i_4502",
    "status": "withdrawn"
  }

ToolWhat it doesAccess

• list_conversations Your message threads, newest first, with the last message and who wrote it. read

  Reads Messaging and returns the threads in the order LinkedIn shows them. Each has a conversation_id, the people in it, the last message and last_from, which is you or them. unread_only returns only threads with unread messages.

  MCP calllinkedin_read → list_conversations

  REST endpointGET https://cotlet.dev/api/v1/linkedin/conversations

  Parameters

  Parameters: list_conversations

  Name	Type	Description
  unread_only boolean	boolean	Only threads with unread messages. Default: false.
  limit integer	integer	How many results to return. Default: 10.
  cursor string	string	Next page cursor from the previous call.

  Example response

  {
    "conversations": [
      {
        "conversation_id": "m_8802",
        "with": "Tom Becker",
        "last_message": "Thanks, can you send the pricing?",
        "last_from": "them",
        "unread": true,
        "last_at": "2026-11-05T14:20:00Z"
      }
    ],
    "next_cursor": null
  }

• read_conversation The messages of one thread, oldest first. read

  Returns the messages of one thread in order, each with the sender, text and time. Opening a thread marks it as read in LinkedIn, the same as opening it yourself.

  MCP calllinkedin_read → read_conversation

  REST endpointGET https://cotlet.dev/api/v1/linkedin/conversations/{conversation_id}/read

  Parameters

  Parameters: read_conversation

  Name	Type	Description
  conversation_id string required	string	Conversation ID from list_conversations.
  limit integer	integer	How many results to return. Default: 10.
  cursor string	string	Next page cursor from the previous call.

  Example input

  {
    "conversation_id": "conversation_8c41d2"
  }

  Example response

  {
    "messages": [
      {
        "from": "you",
        "text": "Hi Tom, thanks for connecting.",
        "sent_at": "2026-11-04T10:00:00Z"
      },
      {
        "from": "Tom Becker",
        "text": "Thanks, can you send the pricing?",
        "sent_at": "2026-11-05T14:20:00Z"
      }
    ],
    "next_cursor": null
  }

• send_message Sends a message to a connection, or into an existing thread. writeasks first

  Sends a text message as you. Give conversation_id to answer in a thread, or recipient (a profile URL) to start one. LinkedIn lets you message your connections directly; for people you are not connected to it needs InMail, a Premium feature. Returns the message time. By default you confirm each call; you can switch that off for this tool.

  MCP calllinkedin_write → send_message

  REST endpointPOST https://cotlet.dev/api/v1/linkedin/messages

  Parameters

  Parameters: send_message

  Name	Type	Description
  text string required	string	Message text.
  conversation_id string	string	Conversation ID from list_conversations. Use this or recipient.
  recipient string	string	Profile URL of a connection. Use this or conversation_id.

  Example input

  {
    "text": "text"
  }

  Example response

  {
    "conversation_id": "m_8802",
    "status": "sent",
    "sent_at": "2026-11-06T09:15:00Z"
  }