Skip to main content

Documentation Index

Fetch the complete documentation index at: https://docs.pinkfish.ai/llms.txt

Use this file to discover all available pages before exploring further.

Custom MCP Servers is where every MCP server your organization has registered or generated shows up. Once a server is here, every tool it exposes is available in the agent catalog and the workflow builder’s slash menu — right alongside Pinkfish’s embedded services and third-party connections. Find it under Tools → Custom MCP Servers. Custom MCP Servers page — list with search and the empty state "No custom MCP servers available"

​
How Servers Get Here

Custom MCP servers are created in two ways:
  1. Generated from a custom integration. When you build a custom integration and upload an OpenAPI spec on Step 3 (MCP Server Setup), Pinkfish generates a new MCP server from the spec. The generated server lands on this page automatically, and the integration is wired up so connections built from it know about the new tools.
  2. Registered manually. Remote MCP servers that your org operates (or that a vendor ships) can be registered by admins through the platform’s MCP registration API. Contact support@pinkfish.ai to get one added if you don’t have admin access.
Both paths produce the same record: a server with an ID, a service key, a description, and a set of tools.

​
What Each Row Shows

Each row on the list is one registered server. Columns:
ColumnDescription
NameDisplay label (falls back to the raw server name if no label was set) with a short description underneath.
ActionsA More menu (⋯) with View Details and Delete options.
The list supports free-text search in the top toolbar.

​
Empty state

When your org has no custom servers, the list shows No custom MCP servers available. That’s the expected state for fresh orgs — registering one or generating one from a custom integration will fill it in.

​
Row Actions

​
View Details

Opens a side sheet with everything Pinkfish knows about the server:
  • Server ID — the internal identifier used when tools are called.
  • Service Key — the stable key agents and workflows reference (for example mycompany-orders or vendor-widgets).
  • Tools (N) — a count badge plus one card per tool. Each card shows the tool name as a monospace badge and a description pulled from the server’s schema. If a tool has no description, Pinkfish shows No description available rather than hiding the row, so you always know what’s registered.
Use the details panel to audit what an agent can actually do with a server before you reference it in a workflow.

​
Delete

Also in the More menu. Delete opens a confirmation dialog titled Delete MCP Server with the body Are you sure you want to delete "{name}"? This action cannot be undone. Click the destructive Delete button to confirm; on success a toast reads Server "{name}" deleted and the row disappears. Delete is only shown for users with write permission on the server — regular members see only View Details.
Deleting a custom MCP server doesn’t remove references to its tools from existing agents or workflows. Those references will start failing at call time. Audit usage before removing a server that’s in active production use.

​
Using Custom MCP Server Tools

Once a server is registered, its tools behave identically to every other tool in Pinkfish:
  • Agents can be configured to use them in the agent builder’s tool picker.
  • Workflows (both guided and agent mode) invoke them through the slash menu.
  • Tool names follow the registered service key as a prefix, which keeps names unique across servers and Pinkfish’s own catalog.
To test a tool, the easiest path today is to use the connection test modal on any Connection linked to the server — that exposes the same parameter form and response viewer.

​
Relationship to Connections

It’s worth being explicit about the three things that live on the Tools → MCPs category:
SurfaceWhat it isWhen to use
ConnectionsAn established link to one instance of an app (one Salesforce org, one Slack workspace) with its credentials. Each connection points at an MCP server.Whenever an agent needs to act on a specific account.
Embedded ServicesPinkfish’s built-in MCP servers (web search, code exec, etc.). Always available; no connection needed.Whenever you need a generic capability that doesn’t tie to a customer’s account.
Custom MCP Servers (this page)The definitions of MCP servers your org has generated or registered. One row here can back many connections.Whenever you add new tools to your org — either by generating from an OpenAPI spec or by registering an external server.

​
Notes

  • The list paginates at 50 rows; searching filters by name and description.
  • Servers generated from a custom integration inherit the integration’s label and description, but you can rename them from the details panel.
  • Tool execution logs for custom MCP servers appear in the standard Monitor view alongside other tool calls.