Documentation

Getting Started

1. Sign up at rankedin.app
2. Export your LinkedIn data — LinkedIn → Settings & Privacy → Data Privacy → Get a copy of your data → Request archive
3. Upload the ZIP at rankedin.app/dashboard/upload — analysis usually takes about a minute
4. Connect to Claude using the MCP server below. Claude signs you in with OAuth, so no API key is needed
5. For the REST API or config-file clients only: generate an API key at Dashboard → Settings

You can connect Claude before uploading. Career-path guidance (get_career_paths) works without an analysis; everything personal about your profile needs one.

MCP Server

RankedIn exposes a Model Context Protocol server at https://rankedin.app/api/mcp. This lets Claude, Cursor, Windsurf, and other MCP-compatible clients answer career questions using your own LinkedIn data.

https://rankedin.app/api/mcp

Alternative for developers and other MCP clients (API key): clients configured through a file can connect with an API key from Dashboard → Settings. This isn't needed for the Claude apps above.

{
  "mcpServers": {
    "rankedin": {
      "url": "https://rankedin.app/api/mcp",
      "headers": { "Authorization": "Bearer rkin_YOUR_API_KEY" }
    }
  }
}

{
  "mcpServers": {
    "rankedin": {
      "command": "npx",
      "args": [
        "mcp-remote",
        "https://rankedin.app/api/mcp",
        "--header",
        "Authorization: Bearer rkin_YOUR_API_KEY"
      ]
    }
  }
}

Claude Plugin

RankedIn also has a Claude plugin, which is under review for the Claude directory. It pairs the connector above with two skills that guide Claude in using it. There are two ways to start:

Tools Reference

The Claude connector exposes seven tools. All are read-only (readOnlyHint: true). Each accepts an optional analysis_id — omit to use the most recent analysis. Answers drawn from your analysis state the date it was completed.

Connection Changes

Your first analysis establishes a baseline. When you upload a newer LinkedIn export, your next analysis is compared with your previous export, and the My Network tab of your analysis on rankedin.app shows what changed, connection by connection:

• New connections since your previous export
• Discontinued connections — records no longer present in the newer export. RankedIn can't tell which of you removed the connection
• Job, company, role and title changes — connections whose recorded title or company differs between the two exports. RankedIn compares the exported text, so a change can reflect a new job, a promotion or an edited profile
• Relationships to reconnect with — your longest-standing connections, which may be worth re-engaging

Through Claude, get_connection_insights reports the counts behind these changes but deliberately never returns names. Open your analysis on rankedin.app for the person-level lists.

REST API

All endpoints require Authorization: Bearer rkin_YOUR_API_KEY. Full OpenAPI spec available at rankedin.app/openapi.json.

OAuth 2.0

The Claude connector signs users in with the OAuth 2.0 Authorization Code flow; PKCE (S256) is supported. Server metadata is published at https://rankedin.app/.well-known/oauth-authorization-server.

Claude registers itself automatically through dynamic client registration, so no setup is needed when you connect from Claude. Registration accepts only supported integrations' callback URLs. To connect another OAuth client, contact rahul@rankedin.app, or use an API key as described above.

Troubleshooting