Loading page content
Connect a public remote MCP server to your Tap workspace. Discover its tools, resources and prompts, then choose how Tap can use them.
A clear path from your first connection to your next task.
Open custom setup in Integrations and enter the server’s final public HTTPS address.
Follow the server’s requirements for sign-in, a bearer token, credential headers or no authentication.
Review discovered tools, resources and prompts. Set Ask, Auto or Don’t ask for each tool.
Use a publicly reachable HTTPS server supporting Streamable HTTP or the supported legacy HTTP+SSE transport. Tap’s custom connection does not run local stdio servers or provide a local-server bridge.
Yes. Connections belong to you within your Tap buyer workspace. You can manage each connection separately, including its credentials, available capabilities and tool permissions.
Ask requests approval before every tool call. Don’t ask permits calls without that confirmation, including supported changes. Auto evaluates each call and asks when the result is uncertain or consequential. Provider access limits still apply.