Qampi

What the Qampi MCP server does

The Qampi MCP server is described as an agent-facing interface for LinkedIn outreach. Its stated scope covers four activities: finding prospects, adding leads, running outreach campaigns, and reading campaign results. These capabilities make it relevant to workflows that use an agent to coordinate prospect discovery and campaign operations on LinkedIn.

The available project information does not explain whether prospect searches use filters such as job title, company, location, or industry. It also does not describe how leads are represented, which campaign controls are available, or what result data an agent can read. Those details should be confirmed from the repository before implementing against the server.

Tools and capabilities

The listed capabilities are:

• Find prospects on LinkedIn.
• Add leads to an outreach workflow.
• Run LinkedIn outreach campaigns.
• Read campaign results.

The source description does not provide the exact MCP tool names, parameters, return formats, pagination behavior, or error responses. Treat the capability list as a functional outline rather than a complete API reference. In particular, it does not establish whether the server can update or remove leads, edit campaigns, send individual messages, or export results.

Limitations and notes

The repository README is unavailable in the supplied material, so setup and operational details cannot be verified. No installation command, package name, transport mode, configuration key, authentication flow, LinkedIn account requirements, or client compatibility information is documented here. The Qampi MCP server should therefore be evaluated against the repository's current instructions before use.

The description also does not specify campaign safeguards, rate limits, consent handling, or LinkedIn policy considerations. Teams planning automated outreach should validate those areas independently. Likewise, “read results” is not defined further: the available material does not say whether results include delivery, response, conversion, or other campaign metrics.

For a developer deciding whether this fits, the clearest match is an agent workflow that needs the four stated LinkedIn operations. If the application requires documented authentication, reliable result schemas, advanced campaign editing, or a named client integration, the supplied information is insufficient to confirm support. The Qampi MCP server's precise behavior depends on implementation details that are not included in the available listing.