Prosp MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| PROSP_API_KEY | Yes | Your Prosp API key from https://prosp.ai/settings | |
| TOOL_CATEGORIES | No | Comma-separated list of tool categories to load (leads, campaigns, messaging) |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
| logging | {} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| add_leadC | Add a lead to a Prosp contact list and campaign by LinkedIn URL. |
| add_lead_to_listA | Add a lead to a contact list only (no campaign assignment). |
| add_existing_lead_to_campaignA | Add an existing lead (already in workspace) to a campaign. |
| remove_lead_from_campaignA | Remove a lead from a campaign (lead stays in workspace). |
| delete_leadA | Permanently delete a lead from the workspace. |
| get_leads_in_campaignA | Get all leads in a campaign with optional pagination. |
| get_lead_stageA | Get the current stage of a lead in a campaign. |
| check_api_keyA | Verify the Prosp API key is valid and the API is reachable. |
| get_all_campaignsA | Get all campaigns in the workspace. |
| get_campaign_statusC | Get the current status of a campaign. |
| start_campaignA | Start a campaign. Campaign must be in a startable state. |
| stop_campaignA | Stop a running campaign. |
| get_analyticsA | Get analytics data for a campaign or the entire workspace. |
| send_messageB | Send a LinkedIn message to a profile. |
| send_voice_messageC | Send a LinkedIn voice message to a profile. |
| get_conversationA | Get the LinkedIn conversation history with a lead. |
| get_server_infoA | Get Prosp MCP server version, config status, and loaded tools. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 17 tools
Most tools target distinct resources and actions, but the add_lead, add_lead_to_list, and add_existing_lead_to_campaign trio could cause confusion since they all relate to lead/campaign assignment. The descriptions help clarify the differences, and send_message vs send_voice_message are clearly separated.
Tool names follow a consistent verb_noun pattern with clear actions like get_, add_, remove_, delete_, start_, stop_, and send_. Minor variations like check_api_key instead of get_api_status do not break the overall predictability.
17 tools is slightly above the typical 3-15 sweet spot, but the count is justified by the mix of campaign management, lead lifecycle, messaging, and server information tools. There is no obvious bloat or redundancy.
The server covers lead management, campaign assignment and status flows, sending messages, and viewing conversations. However, there is no campaign creation/update/delete, no contact list management beyond adding leads, and no direct lead detail retrieval, leaving notable administrative gaps.