Skip to main content
A custom MCP connector points at a remote MCP server you operate. Use it for proprietary tooling, internal systems, or anything the registry does not cover.

​
Requirements

Your server must:
  • Speak MCP over Streamable HTTP. That is the only client transport Noorle has — no SSE client, no stdio.
  • Be reachable from the public internet over TLS. Noorle dials out to it; it does not run inside your network.
  • Implement tools/list and tools/call. Noorle consumes tools; prompts and resources are not surfaced.

​
Creating one

In the Portal, Connectors → New connector → Custom MCP. Provide the server URL, plus encrypted headers on the transport — where an API key or bearer token goes. They are stored as AES-256-GCM ciphertext. Servers that authenticate over OAuth, including dynamic client registration, are supported; the connector shows as Needs auth until the flow completes.

​
Idempotency

A connector may declare where Noorle’s stable idempotency key should travel — an HTTP header name, or a field in the MCP _meta object. Declaring it lets your server deduplicate a retried call. Leaving it unset means no provider-level claim, and retries look like fresh calls.

​
What you get

The server’s tools, namespaced under the connector’s namespace, bindable to agents and gateways. They are Act tier, kind-wide — Noorle cannot tell a read from a write inside your server.

​
Custom MCP or a plugin?

Plugins are covered in the Build tab.

​
Next