Custom MCP server
Add any remote MCP server's tools to your Plugsight MCP servers, signed in with OAuth, a token or headers, with changes behind your approval.
Updated
Add any remote MCP server on a public https address: your own, an internal one, or a service that offers an MCP server Plugsight has no connector for. Plugsight connects to it, lists its tools and offers them in your Plugsight MCP servers, next to your other accounts. Your AI app then needs only Plugsight, and the same switches and approvals apply to every change.
What your AI can do
- Use the server's tools: every tool the server lists (up to 100) becomes a tool of your MCP server, named after the connection, like
notes__search_notesfor a connection called "Notes". - Read straight away: tools the server marks read-only work whenever the connection is in your MCP server.
- Make changes, with your approval: every other tool counts as a change. It works only when you allow changes, and each call waits for your approval in the chat.
- Refresh the tools: your AI can ask Plugsight to list the server's tools again, for example after the server adds one.
Example questions
- "Search my notes server for anything about the Q3 launch."
- "Using the Notes tools, create a note with today's meeting actions."
- "Which tools does the Notes server have, and which of them make changes?"
- "Refresh the Notes server's tools and tell me what's new."
What you need
- The Pro or Agency plan. On Free, the Custom MCP server tile shows On Pro: upgrade to connect. See Plans.
- The server's remote MCP address, from its documentation. It starts with https:// and often ends in /mcp. Older servers' addresses can end in /sse; that works too.
- How it signs you in: most servers ask you to sign in with them (OAuth); others take a token, or a header with a key.
Only connect servers you trust. Your AI reads what the server's tools send back, and the server writes its own tool descriptions. Plugsight marks those descriptions as the server's own words and never lets them change its rules, but a server could still try to mislead your AI.
Connect a custom MCP server
- In Plugsight, open Connections, click Add connection and choose Custom MCP server (any remote MCP server) in the catalog.
- Type the Server address, like https://mcp.example.com/mcp.
- Optionally give the connection a Name, such as "Notes". It also starts the names of the server's tools, so keep it short.
- Under How Plugsight signs in, choose one:
- Sign in with the server (OAuth): click Sign in. You go to the server's own sign-in page, then come back to Connections. Plugsight finds the server's sign-in and registers itself there; if the server doesn't allow that, see Use your own OAuth client.
- Bearer token: paste the Token. It's sent as "Authorization: Bearer" and the token.
- Headers: type each header's name and value, such as X-API-Key and your key. Click Add header for another.
- No sign-in: for servers anyone can use.
- For every choice but OAuth, click Test connection & save.
Plugsight connects to the server and lists its tools before saving. When it works, you see a message like "Connected Notes (mcp.example.com), id "notes". It has 6 tools: 4 that only read, and 2 that can make changes (off until you allow changes)."
Then add the connection to an MCP server, refresh the tools list in your AI app and start a new chat.
Use your own OAuth client
Some servers don't let apps register themselves. Then, in the server's settings or documentation, create an OAuth client with the redirect address shown under Use my own OAuth client (it ends in /auth/custom-mcp/callback). Back in Plugsight, choose Sign in with the server (OAuth), tick Use my own OAuth client, type its Client ID and Client secret, and the Scope if the server needs one, then click Sign in.
Connect it again
To change the token or headers, or to sign in again, connect it again with the same Server address and Name: Plugsight replaces the sign-in. With a different Name, it's a second connection, which is how you connect the same server twice, for example with two accounts.
What it can and can't change
Tools the server marks read-only always work while the connection is in your MCP server. Plugsight decides this from the server's own read-only mark, so a tool without that mark counts as a change, whatever its description says.
Every other tool needs all of these:
- Your plan includes changes (Pro and Agency do).
- The connection's switch on Connections says Can make changes. It starts as Read-only for every server you connect.
- Allow changes is ticked on the MCP server your AI app uses.
- Custom APIs and MCP servers isn't paused on Permissions.
- You approve the exact call in the chat.
What Plugsight never does, whatever you allow:
- It never connects to private or local networks, plain http addresses or other ports, for the server and its sign-in alike, and never follows redirects.
- It never shows your token, headers or sign-in to your AI. They're stored encrypted, and cut from anything the server sends back. The server's address is stored encrypted too: the app shows only its host.
- It never lets a tool's description change how the tool is treated: descriptions are shown as the server's own words, and cut short.
To cut access, remove the connection on Connections, and sign Plugsight out or delete its token at the server's end.
Limits
- Public https addresses on the standard port only, with no query string.
- Up to 100 tools per server. A server with more offers its first 100, and says so.
- Plugsight keeps each server's tool list for a few minutes, and on the connection, so a server that's slow or down doesn't hide its tools. While it can't be reached, your AI is told how old the list is.
- Each call has 60 seconds. Plugsight passes on text only (images and files are described, not passed on), up to 100,000 characters; anything longer is cut, and your AI is told so.
- Tool descriptions are cut to 1,000 characters, and the descriptions inside a tool's argument list to 500. A tool whose argument list is very large (or one past a server's total for argument lists) is offered without it, and your AI is told to give the arguments the server expects.
Troubleshooting
Custom MCP server connections are on the Pro plan. Upgrade under Billing to connect your own MCP servers.
What it means: Your plan doesn't include custom MCP servers.
How to fix it: Upgrade under Billing. See Plans.
The server address must start with https://. Plugsight only signs in over encrypted connections.
What it means: The address starts with http://, so your sign-in would travel unencrypted.
How to fix it: Use the server's https:// address. If it has none, Plugsight can't connect to it.
That address isn't a public website. Enter the MCP server's public https address, like https://mcp.example.com/mcp.
What it means: The address points to a private or local network, which Plugsight never calls.
How to fix it: Use the server's public address on the internet.
No MCP server answered at that address on [host] (HTTP …). Check the address: it often ends in /mcp.
What it means: Something answered at that address, but not an MCP server.
How to fix it: Copy the remote MCP address from the server's documentation again. It's often the site's address followed by /mcp or /sse.
[host] doesn't let apps register themselves. In the server's settings or documentation, create an OAuth client with the redirect address …, then tick Use my own OAuth client and enter its client ID (and secret).
What it means: The server's sign-in needs a client made for Plugsight in advance.
How to fix it: Follow Use your own OAuth client.
This sign-in was started in another browser, replaced by a newer one, or took too long. Start it again from the custom MCP server page.
What it means: The sign-in must finish in the same browser that started it, within 30 minutes. A browser has one sign-in at a time: starting another one cancels the first.
How to fix it: Open the custom MCP server page again and click Sign in.
The MCP server turned the saved sign-in away (HTTP 401).
What it means: The server no longer accepts the token or headers. The connection shows Reconnect needed.
How to fix it: Get a new token or key from the server, then connect it again with the same Server address and Name.
The MCP server's sign-in expired or was revoked.
What it means: The OAuth sign-in can't be renewed any more, for example because you signed Plugsight out at the server's end.
How to fix it: Connect it again and sign in.
Changes are off for "[connection]". Allow them under Connections first.
What it means: The connection's switch is Read-only, so your AI can use only the tools the server marks read-only.
How to fix it: On Connections, click the switch so it says Can make changes.
Custom MCP server changes are paused (Permissions page).
What it means: Changes through custom MCP servers and Custom APIs are paused for every connection.
How to fix it: On Permissions, resume Custom APIs and MCP servers. See Pause changes.