Other Clients

Any MCP client can connect. There are two cases.

Clients that accept a remote URL

If your client supports remote MCP servers over HTTP, point it at the endpoint:

https://engine.catchintent.com/mcp

The client opens a browser for the CatchIntent sign-in and consent.

Clients that only support stdio

Some clients only launch local (stdio) MCP servers. Bridge to the hosted server with mcp-remote:

npx -y mcp-remote https://engine.catchintent.com/mcp

In the client's MCP config, set the command to npx and the args to -y mcp-remote https://engine.catchintent.com/mcp. The bridge handles the OAuth sign-in and caches the token.

Permissions

You choose read, write, or push-to-CRM access at sign-in, the same as every other client. Start read-only. See the tools reference.

If a client supports remote MCP natively, use that. The bridge is only for stdio-only clients.