Connectors
Add a custom connector or a remote MCP server
Beyond the released integrations you can register your own connector: an HTTPS service described by OpenAPI 3, or a remote MCP server, with credentials stored encrypted and bound to your account.
Last updated 20 September 2026
Adding one
- 1Open the Connectors panel and use the + in the header: Custom connector, or MCP server.
- 2Provide the base URL and the OpenAPI 3 description, or the MCP endpoint.
- 3Enter credentials. They are stored encrypted and bound to your account, never returned to the client.
- 4Review the discovered operations and set Allow, Ask or Deny for each one.
Built-in safeguards
- Private and local network hosts are refused, which blocks the usual request-forgery paths.
- Discovered schemas are slimmed, so an oversized description cannot flood the request.
- Rate limits and revisions apply per connector.
- Provider responses are treated as untrusted data, so text coming back from a tool cannot issue new instructions.
Primary sources
Frequently asked questions
Does a custom connector see my other services?
No. Each connector runs its own operations under its own credentials and permission policy.
Can an MCP tool act without asking?
Only if you set that operation to Allow. Uncertain or consequential effects stop for approval.
Related guides
How connectors work, and when the browser is used insteadConnectors call a service API through the backend; browser actions use the website interface. Learn how resolvenengine decides which path a request takes.Allow, Ask, Deny: the permission model explainedSet a policy for every single operation, require approval for writes, and understand why a denial is never bypassed.
Try it in your own Chrome
Pro is $19 USD per month and uses your own AI API key, so the provider bills model usage at their own rate.