Custom Connectors

What is a custom connector?

A custom connector is any API or MCP server connection you configure manually rather than using a pre-built Marketplace connector. Custom connectors give you full control over the base URL, credentials, and documentation associated with the connection. They are the right choice for internal APIs, proprietary tools, and any service not yet in the Marketplace.

When to build a custom connector

• Your internal API is not available in the Marketplace
• You need a third-party service with non-standard authentication
• You want to connect to an MCP server you host yourself
• You need separate credential configurations for the same service, such as staging vs. production environments

Saving API knowledge

When building automations against a custom API, you will learn things about it — pagination patterns, response formats, required headers, quirky error handling, rate limits. Save this knowledge using the manage_knowledge tool, associating it with the connection by name. Future automations using the same connection will read this knowledge first, avoiding repeated trial-and-error.

Blacklisted URLs

For security, Chase Agents blocks connections to certain URL patterns to prevent automations from probing internal infrastructure. The following are always blocked:

• localhost and 127.0.0.1
• Private IP ranges: 192.168.x.x, 10.x.x.x, 172.16.x.x
• IPv6 loopback: ::1
• Link-local addresses: 169.254.x.x
• Internal domains ending in .local or .internal
• Local file protocol (file://)

Self-hosted MCP servers

If you run your own MCP server, add it as a connection by providing its URL. All tools the server exposes become available in your workspace. Use read_resource with type mcp-server and the connection name to see the full tool catalog and input schemas.