Clado

You can run the Clado MCP Server to expose Clado’s Model Context Protocol endpoints to your clients. It lets you securely connect your MCP-enabled tools and workflows to Clado via the MCP interface, using your API key to authenticate and control access.

How to use

To use the Clado MCP Server, start it with your API key and connect your MCP client. The server runs locally and your client sends requests through the MCP interface. You manage configuration per client environment (Cursor, Windsurf, or Claude Desktop) using explicit MCP JSON blocks that specify how to launch the server and provide your API key. Make sure your API key stays secret and is kept out of versioned files.

How to install

Prerequisites you need before installation: Node.js and npm installed on your machine. You typically get npx with npm, so you don’t need a global install for npx itself.

Install and run the MCP server using the following command.

npx @clado-ai/mcp YOUR-CLADO-API-KEY

Configuration across common clients

Cursor configuration lets you auto-start the MCP server when your editor runs. Create or edit ~/.cursor/mcp.json and add the clado MCP entry with the launch command and your API key.

Windsurf configuration allows you to define the MCP server in ./codeium/windsurf/model_config.json. Include the same command and API key so Windsurf can start the server as part of your coding environment.

Claude Desktop provides an example JSON block to configure the MCP server for that client. Include the command, arguments, and your API key to enable access.

Examples of MCP server configurations you can use

{
  "mcpServers": {
    "clado_cursor": {
      "command": "npx",
      "args": ["-y", "@clado-ai/mcp"],
      "env": {
        "CLADO_API_KEY": "YOUR-API-KEY"
      }
    },
    "clado_windsurf": {
      "command": "npx",
      "args": ["-y", "@clado-ai/mcp"],
      "env": {
        "CLADO_API_KEY": "YOUR-API-KEY"
      }
    },
    "clado_desktop": {
      "command": "npx",
      "args": ["--yes", "@clado-ai/mcp"],
      "env": {
        "CLADO_API_KEY": "YOUR-API-KEY"
      }
    }
  }
}

Tools

The MCP server provides a set of tooling endpoints. You can use each tool to search, enrich, and retrieve LinkedIn data in a controlled, credit-based manner.

• search_for_users - Search for LinkedIn users with filters like query, school, and match threshold
• enrich_linkedin - Retrieves detailed profile information for a specific LinkedIn URL (1 credit per lookup)
• retrieve_contacts - Retrieves email addresses and phone numbers for LinkedIn profiles, supports reverse lookup via email/phone (4 credits for email, 10 credits for phone if found)
• scrape_linkedin - Retrieves detailed profile data and posts with comments from a LinkedIn profile URL (2 credits per request)
• linkedin_post_reactions - Retrieves reactions and engagement data for a specific LinkedIn post URL

Security and best practices

Keep your API key secure. Do not commit API keys to version control. Use environment variable configuration in each MCP client and prefer per-environment keys where possible.

If you rotate keys, update all client configurations promptly to avoid service interruption.

Notes and troubleshooting

If the MCP server does not start, verify Node.js and npm are properly installed and that you are using a valid API key. Check that the launcher commands are exactly as shown in your environment blocks and that there are no typos in the key.

Available tools

search_for_users

Search for LinkedIn users with filters like query, school, and match threshold

enrich_linkedin

Retrieves detailed profile information for a specific LinkedIn URL (1 credit per lookup)

retrieve_contacts

Retrieves email addresses and phone numbers for LinkedIn profiles, supports reverse lookup via email/phone (4 credits for email, 10 credits for phone if found)

scrape_linkedin

Retrieves detailed profile data and posts with comments from a LinkedIn profile URL (2 credits per request)

linkedin_post_reactions

Retrieves reactions and engagement data for a specific LinkedIn post URL