Skip to content

MCP Gateway

Connect AI agents and LLM-powered tools to your PartnerSignals data via the Model Context Protocol (MCP).

Overview

The PartnerSignals MCP Gateway exposes your partner ecosystem data as MCP tools that any MCP-compatible AI agent can call — Claude, custom agents, internal tools, or any system implementing the MCP standard.

MCP Gateway endpoint: https://eco.partnersignals.ai/mcp

Authentication

The MCP Gateway uses your PartnerSignals API key. Add it to your MCP client configuration:

{
  "mcpServers": {
    "partnersignals": {
      "command": "npx",
      "args": ["-y", "@partnersignals/mcp-server"],
      "env": {
        "PARTNERSIGNALS_API_KEY": "ps_live_your_key_here"
      }
    }
  }
}

curl "https://eco.partnersignals.ai/mcp" \
  -H "Authorization: Bearer ps_live_your_key_here" \
  -H "Accept: text/event-stream"

Available Tools

get_signals

Retrieve co-sell signals from the signal feed.

Parameters:

Name Type Required Description
type string No Signal type: co_sell, overlap, pre_intent
state string No Signal state: new, in_progress, handled
partner_id string No Filter to a specific partner
limit integer No Number of results (default: 10, max: 50)

Returns: Array of signal objects with partner, account, opportunity, and recommended action.

get_partner

Look up a specific partner by ID or name.

Parameters:

Name Type Required Description
partner_id string No* Partner ID
name string No* Partner name (fuzzy match)

*One of partner_id or name is required.

Returns: Partner detail including tier, type, co-sell density score, and active signal count.

list_partners

List all partners in your ecosystem.

Parameters:

Name Type Required Description
type string No Partner type filter
tier integer No Tier filter (1–4)
limit integer No Number of results (default: 20, max: 100)

Returns: Array of partner summaries.

get_attribution

Retrieve attribution records for closed deals.

Parameters:

Name Type Required Description
partner_id string No Filter to a specific partner
closed_after string No ISO 8601 date — filter to deals closed after
limit integer No Number of results (default: 10, max: 50)

Returns: Array of attribution records with tier, weight, and evidence summary.

update_signal_state

Update the state of a signal (mark handled, in progress).

Parameters:

Name Type Required Description
signal_id string Yes Signal ID
state string Yes New state: in_progress, handled
note string No Optional action note

Returns: Updated signal object.

request_intro

Queue a partner intro request for a specific signal.

Parameters:

Name Type Required Description
signal_id string Yes Signal ID
note string No Context for the partner manager

Returns: Intro request confirmation with routing details.

Example Agent Prompt

You have access to PartnerSignals MCP tools. When I ask about co-sell opportunities,
use get_signals to find new signals, then use get_partner to pull context on the
relevant partner before making a recommendation.

Troubleshooting

401 Unauthorized from the MCP Gateway - Verify your API key is correct and has at least signals:read scope - Check that the key is being passed as PARTNERSIGNALS_API_KEY in your env config

Tools not appearing in your MCP client - Ensure you're using the correct gateway URL: https://eco.partnersignals.ai/mcp - Restart your MCP client after updating the config