Hosted MCP server

New to the integration? Explore the Postiv LinkedIn MCP server for a workflow demo, client setup instructions, and examples of research, drafting, scheduling, and analytics.

Connect your AI app to Postiv with OAuth: sign in with your own Postiv account, select the workspace it can use, and approve permissions. No organization API key is needed for Claude or ChatGPT. Posts and carousels created through OAuth are attributed to the signed-in Postiv user within the approved workspace.

https://postiv.ai/mcp

3db7f794-4990-4a61-a4e9-855d0c052eb5

Use the public client ID above when your app asks for OAuth client details. Leave the client secret empty. Choose a predefined or user-defined client if offered; automatic client registration is not required for this setup.

For a guided setup with copy buttons, open Connect Postiv. Custom connector availability depends on your AI app plan and workspace policy.

Connect Postiv to Claude

Add a custom connector, then sign in with your Postiv account.

Open Claude connectors

1. 1
   Open Claude connectors, choose Add custom connector, and name it Postiv.

   
2. 2
   Paste the MCP server URL from this guide and choose Continue. Wait for Claude to check the server.

   
3. 3
   On the authentication step, select Always required and Use your own OAuth client. Enter the OAuth client ID from this guide and leave the client secret empty. Then choose Add.

   
4. 4
   Choose Connect on the Postiv connector. Sign in to Postiv, select your workspace, review the permissions, and choose Connect workspace.
5. 5
   Enable Postiv in a new conversation and ask it to confirm your workspace and list your LinkedIn profiles.

Current Claude requirements

Connect Postiv to your ChatGPT account

Create a custom MCP app for your own account. Availability depends on your plan and workspace settings.

Add Postiv in ChatGPT

1. 1
   On chatgpt.com, open Settings → Security and login and enable Developer mode. Some accounts show it under Apps → Advanced settings.

   
2. 2
   Open the connector form, name the app Postiv, paste the MCP server URL from this guide, and choose OAuth. If the form does not open, go to Plugins and choose Create app.

   
3. 3
   In advanced OAuth settings, choose User-Defined OAuth Client. Enter the client ID from this guide, leave the secret empty, and set token endpoint authentication to none.
4. 4
   Turn OpenID/OIDC off. Keep email selected under Default scopes, and enter offline_access in Base scopes so ChatGPT can refresh access.

   
5. 5
   Review the custom-server notice, create the app, and choose Sign in with Postiv. Select your workspace, review the permissions, and choose Connect workspace.

   

   
6. 6
   Back in ChatGPT, refresh the app tools if needed. Choose Try in chat, or start a new chat and select Postiv from the tools menu. Ask it to confirm your workspace and list your LinkedIn profiles.

Current ChatGPT (web) requirements

Workspace and permissions

Read & write is selected by default for new connections and allows creating, editing, deleting, scheduling, and publishing content, plus approvals and engagement actions. Choose Read only if you only need research and reporting.

The workspace you approve stays fixed for that connection. Postiv checks your current workspace access on every request, including agency access. Existing LinkedIn profile approval rules still apply.

Token refresh and reconnecting

Your AI app uses refresh tokens to renew access automatically while the authorization remains valid. You do not need to copy or rotate access tokens yourself. If the app asks you to sign in again, reconnect from its connector settings. Losing workspace access or revoking the connection stops access.

Existing connections keep their original permissions. To change workspace or access, revoke the connection in Postiv and reconnect. Claude and ChatGPT currently share the Postiv MCP authorization, so revoking it can disconnect both.

Manage or revoke connected apps. Revoking an OAuth connection does not invalidate an organization API key.

Connection troubleshooting

Other clients and existing API keys

Claude Code, Cursor, Codex, and generic HTTP clients can still use an organization API key. An admin can generate one in Postiv integrations; see API-key setup. The examples below use key authentication. OAuth in another client requires its exact callback URL to be registered first.

Existing Authorization bearer headers, x-api-key headers, and secret URLs such as https://postiv.ai/mcp/pk_postiv_... remain supported. Treat keys and any URL containing one like passwords. The REST API continues to use organization API keys.

Claude Code

claude mcp add --transport http postiv https://postiv.ai/mcp \
  --header "Authorization: Bearer pk_postiv_..."

Cursor with an API key

Open Postiv setup in Cursor. This adds an environment-variable template, not a credential. Set POSTIV_API_KEY in the environment used to launch Cursor, restart Cursor, and enable the server. See Cursor install links and environment-variable configuration.

{
  "mcpServers": {
    "postiv": {
      "url": "https://postiv.ai/mcp",
      "headers": {
        "Authorization": "Bearer ${env:POSTIV_API_KEY}"
      }
    }
  }
}

Generic Streamable HTTP client

{
  "postiv": {
    "url": "https://postiv.ai/mcp",
    "headers": {
      "Authorization": "Bearer pk_postiv_..."
    }
  }
}

Claude Desktop with mcp-remote

{
  "mcpServers": {
    "postiv": {
      "command": "npx",
      "args": [
        "-y",
        "mcp-remote",
        "https://postiv.ai/mcp",
        "--header",
        "Authorization: Bearer pk_postiv_..."
      ]
    }
  }
}

Available tools

Tools use the approved workspace permissions. Hosts that support MCP Apps can display interactive post, image, carousel, and inspiration widgets.