Connectors

A connector turns an external service into tools you can bind to agents and gateways. The platform holds the credentials encrypted and injects them at the host boundary — the model never sees the secret. Create them in the Portal under Connectors.

​

Three kinds

The “New connector” menu offers exactly those three.

​

Choosing between them

• Someone already publishes an MCP server for the service → MCP Registry.
• You run your own MCP server → Custom MCP.
• The service is a plain REST API with a spec → REST API.
• You need arbitrary logic, not a wrapper → a plugin. See the Build tab.

​

Transport

MCP connectors dial out over Streamable HTTP only. There is no SSE client and no stdio process execution — a registry entry that only ships a stdio transport is not something Noorle can run.

​

Credentials

Every secret a connector holds — bearer token, OAuth client secret, common headers — is stored as AES-256-GCM ciphertext and decrypted inside the runtime at call time. Three authentication shapes exist: See Authentication. A connector shows as Needs auth when an OAuth connector has no token yet, or when dynamic client registration is still in flight. Anything else is Ready.

​

Binding

Bind on the resource that will use it:

• Agent — Agents → (agent) → Capabilities, under “Connectors”.
• Gateway — Gateways → (gateway) → Capabilities.

Connector tools are namespaced like any other capability’s, and are Act tier across the board — the platform cannot tell a read from a write inside somebody else’s API. At Read-only autonomy every connector tool is denied.

​

Form limits

​

Next

• REST connectors
• MCP registry
• Custom MCP
• Authentication
• Parameter mapping