Custom APIs and MCP servers · Claude
Connect Custom MCP server to Claude
Add any remote MCP server's tools to Plugsight, so your AI app needs one connection, and every change goes through the same switches and approvals. Plugsight links Custom MCP server to Claude in a few minutes, with no code and no exports.
What you can ask Claude about Custom MCP server
How to connect Custom MCP server to Claude
- Create a free Plugsight account.
- Choose Custom MCP server, enter the server's https address and how Plugsight signs in: with the server's own sign-in (OAuth), a bearer token, or headers such as an API key.
Then add Plugsight to Claude
- In Plugsight, open MCP servers, create one and copy its URL.
- On the Claude website (adding a connector doesn't work in the desktop or phone app), go to claude.ai/customize/connectors, click + Add and choose Add custom connector.
- Enter a name and paste the URL, click Continue twice, then Add and Connect.
- Sign in to Plugsight and approve access for that MCP server.
- In a chat, click + → Connectors and make sure Plugsight is switched on. Once added on the website, it works in the desktop and phone apps too.
Claude signs in to Plugsight with OAuth: you approve it once, no keys to copy. Custom connectors work on every Claude plan; the free plan allows one. On Team and Enterprise, an owner adds the connector for the organisation first.
Full steps and troubleshooting in the docs: Claude.
Custom MCP server data available
- Every tool the server lists (up to 100), named after the connection, with the server's own arguments
- Tools the server marks read-only, whenever the connection is in your MCP server
- Every other tool, when you allow changes and approve each call
- A fresh list of the server's tools on request
Why use Custom MCP server in Claude
- Long, careful analysis of large tables
- Artifacts for charts and reports from your data
- Works on web, desktop and mobile
Questions about Custom MCP server and Claude
How do I connect Custom MCP server to Claude?
Create a free Plugsight account and connect Custom MCP server: Choose Custom MCP server, enter the server's https address and how Plugsight signs in: with the server's own sign-in (OAuth), a bearer token, or headers such as an API key. Then add Plugsight to Claude: In Plugsight, open MCP servers, create one and copy its URL. On the Claude website (adding a connector doesn't work in the desktop or phone app), go to claude.ai/customize/connectors, click + Add and choose Add custom connector. Enter a name and paste the URL, click Continue twice, then Add and Connect. Sign in to Plugsight and approve access for that MCP server. In a chat, click + → Connectors and make sure Plugsight is switched on. Once added on the website, it works in the desktop and phone apps too.
Can Claude read my Custom MCP server data?
Yes, once connected. Claude can see: Every tool the server lists (up to 100), named after the connection, with the server's own arguments; Tools the server marks read-only, whenever the connection is in your MCP server; Every other tool, when you allow changes and approve each call; A fresh list of the server's tools on request. For example, ask: "Search my notes server for anything about the Q3 launch."
Which Claude plans work?
Custom connectors work on every Claude plan; the free plan allows one. On Team and Enterprise, an owner adds the connector for the organisation first.
How does Claude sign in to Plugsight?
Claude signs in to Plugsight with OAuth: you approve it once, no keys to copy.
Can Claude change anything in Custom MCP server?
Only if you allow it. Reading is always on; sending or making changes is off until you switch it on for this connection and your MCP server, and each action then needs your approval in the chat.
Is the Custom MCP server connector free?
Custom MCP server is on the Pro plan ($29 a month, or $290 a year), which also adds more connections and the marketing sources. The Free plan covers email, helpdesk, calendar, contacts, files, stores and email marketing.
Good to know
- Only public https addresses: Plugsight never calls private or local networks, and never follows redirects.
- Tokens, headers and sign-ins are encrypted, and cut from anything your AI sees.
- A tool counts as a change unless the server marks it read-only; changes are off until you allow them, and each one waits for your approval in the chat.
- Tool descriptions are shown as the server's own words, cut short, and never change how Plugsight treats a tool.
Related guides
Connect Custom MCP server to Claude
Free plan, no credit card. Set up in about five minutes.
Updated