Skip to main content
Type: Application (proxy) | PCID required: Yes Application servers are proxies to external products and APIs. Each one exposes a vendor or product integration as MCP tools. You create a connection in Pinkfish, obtain a PCID (PinkConnect connection ID), then call tools on the matching server path. Coverage spans many categories (collaboration, CRM, cloud suites, data platforms, support, commerce, and more). This page stays high level — it does not list individual integrations.

​
How application servers work

  1. Connect — Set up a connection in the Pinkfish dashboard to get a PCID
  2. Discover — Call tools/list on the server path, or use capabilities_discover and capability_details on the workflow building server
  3. Call — Invoke tools with the standard JSON-RPC 2.0 pattern, passing the PCID in the tool arguments
For PCIDs and connection setup, see the Connections guide.

​
Generic call pattern

Replace <server-path>, <PCID>, and <tool_name> with your values: 
curl -s -X POST "https://mcp.pinkfish.ai/<server-path>" \
  -H "Content-Type: application/json" \
  -H "Authorization: Bearer <API_KEY>" \
  -d '{
    "jsonrpc": "2.0",
    "id": 1,
    "method": "tools/call",
    "params": {
      "name": "<tool_name>",
      "arguments": {
        "PCID": "<your-pcid>",
        ...
      }
    }
  }'

​
Discovering tools at runtime

Tool schemas are provided by the proxy and may change when integrations update. Prefer runtime discovery over assuming static docs are exhaustive: 
curl -s -X POST "https://mcp.pinkfish.ai/<server-path>" \
  -H "Content-Type: application/json" \
  -H "Authorization: Bearer <API_KEY>" \
  -d '{
    "jsonrpc": "2.0",
    "id": 1,
    "method": "tools/list",
    "params": {}
  }'
You can also resolve tool names and shapes through capability_details on /pinkfish-sidekick, passing the tool names you care about.

​
Where to find each server

  • Sidebar — Under Application MCP Servers, each entry is a dedicated page with path, tools, and parameters (including products where one parent page groups multiple related child server paths).
  • Runtime discovery — tools/list on a server path shows the live MCP surface available to your environment, including the current tool names and schemas.
For built-in platform capabilities (no PCID), see Embedded MCP servers.