Connect Custom MCP

OAuth or API keyRemote MCP server

Add Pluggzy to Custom MCP. You sign in on pluggzy.com and choose what Custom MCP may do; your passwords never go through the chat.

1
Add a remote MCP server
In your client's MCP settings, add a server named Pluggzy with this link.
MCP server URLhttps://pluggzy.com/mcp
2
Sign in with OAuth, or send an API key
Clients with MCP OAuth find the sign-in automatically. Otherwise, send your key as an Authorization: Bearer header, as in the config below, or paste the endpoint with your key appended (…/mcp/<API_KEY>). Reading is on by default; sending is opt-in.

Or add it from the command line

Any client that supports remote MCP servers over Streamable HTTP can connect.

JSON · API key

{
  "mcpServers": {
    "pluggzy": {
      "type": "http",
      "url": "https://pluggzy.com/mcp",
      "headers": {
        "Authorization": "Bearer <API_KEY>"
      }
    }
  }
}

Try your first request

Paste this into Custom MCP after connecting. Your app uses the permissions you approved.

Find conversations in my LinkedIn inbox waiting for a reply.

If something’s off

I don’t see where to add a serverSome plans and workspaces let only admins add connectors or servers. Ask your admin to allow Pluggzy, or check the app’s help center.

The sign-in window closed before I finishedRemove Pluggzy from Custom MCP, add it again and sign in. Nothing is half-saved.

Custom MCP says it isn’t allowed to sendYou left sending off. Remove the app under Connected apps, connect again, and allow Send messages & invitations.

A tool answers “Wait 38s”That’s the human pace at work, not an error in Custom MCP. See the channel’s Safety limits.

Add a remote MCP server

Sign in with OAuth, or send an API key

Or add it from the command line

If something’s off