PipedreamHQ / PipedreamHQ/pipedream

[ACTION] unable to create image and text posts

Open
#17,752 3 comments 0 reactions 0 assignees View on GitHub
action enhancement good first issue help wanted tracked internally triaged
Dominant language
JavaScript
Stars
11.7k
Forks
5.8k
Avg merge
3d 10h
Merged PRs (30d)
102

Description

**Describe the bug**
I am unable to post images to LinkedIn via the Pipedream MCP server. I receive an authorization error (403 Forbidden) indicating that the authenticated user ID is missing or invalid.

**To Reproduce**
Steps to reproduce the behavior:

1. Connect your LinkedIn account to the MCP server using Pipedream.
2. Attempt to create a LinkedIn post through the Pipedream MCP server.
3. Observe the authorization error: "The authenticated user ID is missing or invalid, resulting in an authorization error (403 Forbidden) from LinkedIn."
4. See the reproduction on Pipedream chat at: `https://chat.pipedream.com/chat/9498e4ca-e957-430a-97ff-9bef8c74ab38`

**Expected behavior**
I expect to be able to successfully post to LinkedIn through the Pipedream MCP server after authenticating my LinkedIn account. The image post should be created without any authorization errors.

**Additional context**
The error suggests a problem with authentication or authorization when trying to post on my behalf, despite a successful connection of the LinkedIn account to the MCP server. Possible reasons include:
* **Token Scope or Expiry:** The access token from Pipedream/MCP might lack correct permissions for image posting or may have expired.
* **MCP Server Integration:** The MCP server might not be correctly passing the LinkedIn user ID or access token to the LinkedIn API, or there might be a mismatch between the Pipedream authenticated session and the IDE context.
* **User Context:** The integration might require explicit user context (user ID/profile) to be passed with each request, which might be missing.
* **Pipedream vs. IDE Context:** The authentication from Pipedream may not be valid in the IDE or MCP server context if tokens are not shared or valid for both environments.

Contributor guide

Open the contributing guide

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.