Custom MCP servers
Connect another remote tool server and understand its authentication and permission limits.
Connect a server
MCP lets an app expose tools to OpenTag. Use a built-in integration where available; for another server, open Integrations and add a custom MCP connection.
Enter the server's supported remote URL and complete its authentication. Depending on the server, this can be a provider sign-in or a token entered in the secure form. A local-only server on your laptop is not automatically reachable from OpenTag's cloud environment.
Review the access
The server's tool catalogue defines what it can do. Connection sharing decides who can use it, and the configured tool access limits available operations.
Do not assume a tool is read-only because its name sounds like a search. Unknown custom tools are treated as operations that may have effects. Hosted approval policy does not put a human approval card in front of every such call.
Use provider-side permissions and a narrowly scoped account when you need a firm boundary. See Approvals.
Try a bounded request
Ask for one known record or a small operation with an easily checked result. Confirm that OpenTag used the intended server and account before relying on a broader workflow.
Only connect a server you trust with the information and authority involved. Its outputs become material OpenTag may use while doing the job.
Repair or remove it
Failed custom connections remain visible in Integrations. Use Reconnect when offered, correct the server URL or update authentication as appropriate. Disconnect when you no longer want its tools available.
For a server that will not connect, contact support with its public documentation and the visible error, without credentials.