Connectors
Connect Agents to Any Service
Three connector types to integrate with any external API or MCP server. Auto-generated tools from OpenAPI specs, community servers from the MCP registry, and custom MCP endpoints.
Three Connector Types
One integration model, any service
REST / OpenAPI
Import any OpenAPI 3.x or Swagger 2.0 spec (JSON or YAML, up to 2 MB). Noorle parses operations, extracts parameters, and auto-generates MCP tools — up to 200 per connector.
Auto-Generated Tools
- Tool names from operationId or auto-generated from method + path
- Descriptions from spec summary and description fields
- Path, query, header, and body parameters mapped automatically
- Validation: pattern, min/max, enum constraints from schema
Request & Response
- GET, POST, PUT, PATCH, DELETE
- JSONPath response extraction for nested values
- Binary responses base64 encoded with metadata
- Retry with exponential backoff on 5xx and network errors
Max Operations
200 per connector
Spec Size
Up to 2 MB
Timeout
300s (configurable)
Fuzzy Matching
Jaro-Winkler (0.7)
MCP Registry
Browse and connect MCP servers from the official registry. Select a server by name and version, and Noorle auto-configures transport, auth, and tool discovery from the registry manifest.
Auto-Configuration
- server.json fetched and cached from registry
- Transport type auto-detected from manifest
- Environment variables from registry supported
- Semantic versioning with specific version pinning
OAuth 2.1 Support
- Dynamic client registration
- PKCE (Proof Key for Code Exchange)
- Automatic token refresh with distributed locking
- .well-known/oauth-authorization-server discovery
Registry
1,000+ servers
Cache
Local SQLite
Discovery
Dynamic (MCP protocol)
Auth
None, Bearer, OAuth 2.1
Custom MCP
Connect your own MCP-compatible servers directly. Specify transport URL and headers manually, inject encrypted environment variables, and discover tools dynamically via the MCP protocol.
Configuration
- HTTP/HTTPS and SSE transport
- Custom headers (encrypted storage)
- Encrypted environment variables injected at connection time
Tool Discovery
- Dynamic via MCP list_tools protocol
- Full JSON Schema for inputs and outputs
- Bearer and OAuth 2.1 auth support
Security
Encrypted Credentials. Scoped Access.
Connector secrets are encrypted at rest and decrypted only within request-scoped variables that are zeroed on drop
Bearer tokens, OAuth secrets, access tokens, API keys, headers, and environment variables all encrypted at rest.
Different MCP gateways can have different connectors enabled. Namespace uniqueness enforced per gateway per account.
Credentials decrypted only within request scope. Sensitive values zeroed out immediately after use.
Automatic token refresh with distributed locking to prevent concurrent refresh storms. Permanent vs transient error classification.
Getting Started
Add a Connector in Minutes
Choose Type
Import an OpenAPI spec, browse the MCP registry, or configure a custom MCP server endpoint.
Configure Auth
Set up authentication — none, bearer token, or OAuth 2.1. Credentials are encrypted automatically.
Assign to Gateways
Enable the connector on specific MCP gateways or agents. Control which tools are exposed where.
Agents Use Tools
Tools are automatically discovered and available to agents. Fuzzy matching helps agents find the right tool even with typos.
Reliability
Built-in Error Handling
Automatic retries, validation, and helpful error messages
Network errors and 5xx responses are retried with exponential backoff (500ms min, 2s max). Client errors (4xx) fail immediately.
Schema-based validation before HTTP calls. Missing required params, type mismatches, and constraint violations caught early.
Jaro-Winkler similarity matching suggests correct tool and parameter names when agents make typos. Up to 3 suggestions.
Frequently Asked Questions
How does OpenAPI import work?
Upload an OpenAPI 3.x or Swagger 2.0 spec (JSON or YAML). Noorle parses all operations, extracts parameters and schemas, and generates MCP tools automatically. Up to 200 operations per connector, 2 MB max spec size.
What is the MCP Registry?
A community catalog of MCP-compatible servers. Browse servers by name, select a version, and Noorle auto-configures transport and auth from the registry manifest. Cached locally for fast access.
How are credentials stored?
All sensitive values (tokens, secrets, API keys, headers, environment variables) are encrypted with AES-256-GCM at rest. Decrypted only within request-scoped variables that are zeroed out immediately after use.
Can different gateways have different connectors?
Yes. Connectors are assigned per gateway with individual enable/disable flags. Each gateway can expose a different set of connectors to its clients.
What happens when an API call fails?
Network errors and server errors (5xx) are retried once with exponential backoff. Client errors (4xx) fail immediately so the agent sees the actual error. OAuth tokens are refreshed automatically on expiration.
How does fuzzy matching work?
When an agent calls a tool name that does not exist, Noorle uses Jaro-Winkler similarity (threshold 0.7) to suggest up to 3 similar tool or parameter names. Works across snake_case and camelCase naming.
Connect Your Agents to Everything
All connector types available. Import an OpenAPI spec or browse the MCP registry in minutes.