OpenTag

Integrations

Custom MCP servers

Point OpenTag at an MCP server of your own: an internal tool, a vendor's server, or your own data.

MCP is an open standard for exposing a tool to an AI agent. A lot of vendors now ship an MCP server, and internal systems can run one too. Point OpenTag at any of them and it can use that tool like a built-in.

This is the answer to most "do you integrate with X?" questions.

Adding one

1

Get the server URL

A vendor's server has a published URL. An internal one is wherever your team runs it. It needs to be reachable from the internet.

2

Add it in Integrations

app.tryopentag.com → Integrations → add an MCP server, and paste the URL.

3

Authorise

If the server uses OAuth, OpenTag discovers that and sends you to its sign-in. If it uses a token, paste it. It goes to the credential vault, not to a log.

4

Try it

Ask OpenTag for something that needs it. It'll tell you which tools the server exposed and use them.

What OpenTag does with the tools it finds

A server advertises a set of tools. OpenTag reads them and uses the ones the job needs.

Two things constrain that:

Read and write are distinguished. Where a server offers both and read-only is a meaningfully narrower grant, you're offered that choice when you connect.

Writes still stop at approvals. A tool from your own MCP server that changes something irreversible hits the same gate as a built-in integration. The fence is in the runtime, so it doesn't matter where the tool came from.

You are vouching for the server

A custom MCP server is a tool you're handing your agent. Connect servers from vendors you'd already trust with the same data, or ones your own team runs. A server you don't control can return anything, including content designed to influence what OpenTag does next.

Internal servers

If your team runs an MCP server over an internal system (your warehouse, an ops tool, a service with no public integration), OpenTag can use it like any other connection.

Worth knowing:

  • It must be reachable from the internet. OpenTag runs in the cloud, not on your network.
  • Authenticate it. An unauthenticated server is a public one.
  • Scope the token to what OpenTag actually needs.

Removing one

Integrations → Disconnect. OpenTag stops reaching it immediately and stops offering its tools.

Help with a specific server

team@tryopentag.com, with the server you're trying to connect. If it's a vendor server that doesn't work cleanly, we'd like to know: that's usually a bug we can fix for everyone.