Skip to main content
MCP Registry Connectors connect to published services on mcp.run. Browse, search, and configure pre-built MCP tools.

​
What is MCP Registry?

mcp.run is a registry of pre-built MCP servers. Instead of building your own REST connector or custom MCP, use existing implementations. Examples:
  • Airtable - Spreadsheet operations
  • GitHub - Repository management
  • Linear - Issue tracking
  • Notion - Database operations
  • Slack - Chat and messaging

​
Creating Registry Connector

1

Start Creation

  1. Connectors > Create Connector
  2. Choose MCP Registry
2

Search Service

  1. Search for service (e.g., “Airtable”)
  2. Click to view details
  3. Check required configuration
3

Configure Environment

Provide required environment variables:
  • API Keys - Service credentials
  • URLs - Endpoint configuration
  • Other vars - Service-specific settings
4

Authorize (if OAuth)

Some services use OAuth:
  1. Click Authorize
  2. Grant permissions
  3. Confirm approval
5

Test and Save

  1. Test connection works
  2. Verify tools available
  3. Save connector

​
Finding Services

​
Browse Registry

  1. Connectors > Create Connector > MCP Registry
  2. Browse available services
  3. View documentation for each
Search by:
  • Service name (Airtable, GitHub, etc.)
  • Category (CRM, Databases, Communication)
  • Features (API, webhooks, etc.)
ServiceCategoryAuthCost
AirtableSpreadsheetsAPI KeyFree tier available
GitHubDevelopmentTokenFree tier available
LinearProject MgmtAPI KeyFree tier available
NotionDatabasesTokenFree tier available
SlackCommunicationTokenFree tier available

​
Configuration

Each service requires different setup.

​
Example: Airtable

  1. Get your Airtable API key from https://airtable.com/account/api
  2. In connector setup, paste API key
  3. Provide base ID (from Airtable)
  4. Test connection
  5. Save

​
Example: GitHub

  1. Generate personal access token at https://github.com/settings/tokens
  2. Paste token in connector setup
  3. Verify permissions include needed scopes
  4. Test connection
  5. Save

​
Example: Slack

  1. Create app at https://api.slack.com/apps
  2. Get Bot Token (starts with xoxb-)
  3. Paste in connector setup
  4. Grant necessary permissions
  5. Test connection
  6. Save

​
OAuth Flow

Some services use OAuth 2.0:
  1. Click Authorize
  2. Redirected to service login
  3. Grant permissions
  4. Return to Noorle with token
  5. Token stored securely (encrypted)
No need to share API key directly.

​
Environment Variables

Store sensitive config: 
{
  "env": {
    "AIRTABLE_API_KEY": "encrypted_value",
    "AIRTABLE_BASE_ID": "appXYZ123",
    "NOTION_API_KEY": "encrypted_value"
  }
}
All values encrypted at rest (AES-256-GCM).

​
Available Tools

Each service provides tools (operations): Airtable tools:
  • List records
  • Get record
  • Create record
  • Update record
  • Delete record
GitHub tools:
  • Get repository
  • List issues
  • Create issue
  • Get commits
  • Merge pull request
View available tools when configuring connector.

​
Rate Limits

Service-dependent. Common limits:
  • Airtable: 5 req/sec
  • GitHub: 60 req/hour (auth), 10 req/min (unauthenticated)
  • Notion: 3 req/sec
Noorle enforces these limits automatically.

​
Cost

For current pricing details, see Pricing. Service costs vary - many registry services offer free tiers, while others are paid. Monitor in Account > Usage dashboard.

​
Testing Connection

  1. Open connector
  2. Click Test
  3. Select a tool
  4. Provide sample input
  5. Execute
  6. Verify response

​
Troubleshooting

​
”Authentication Failed”

  • Verify API key/token is correct
  • Check key hasn’t expired
  • Confirm key has required permissions
  • Try re-authorizing OAuth flow

​
”Tool Not Found”

  • Service may have been updated
  • Re-create connector with latest version
  • Check tool name in error message

​
”Rate Limit Exceeded”

  • Slow down request rate
  • Upgrade service tier
  • Use caching if possible

​
”Connection Refused”

  • Service may be down
  • Check status page
  • Try again later

​
Switching Services

Update which registry service a connector uses:
  1. Open connector
  2. Click Change Service
  3. Select new service
  4. Reconfigure
  5. Test and save

​
Next Steps