Skip to main content

Documentation Index

Fetch the complete documentation index at: https://docs.runlayer.com/llms.txt

Use this file to discover all available pages before exploring further.

​
What is Runlayer?

Runlayer is a secure MCP platform that lets you connect AI clients like Claude, ChatGPT, and Cursor to the tools and resources you use every day. Think of connectors as managed MCP servers that give AI clients new skills like opening a PR in GitHub, pulling a ticket from Jira, or researching a deal in Salesforce. Key Benefits:
  • One-Click Setup: Install and connect connectors to any AI client quickly
  • Team-Wide Access: Approved connectors are automatically shared across your organization
  • Cross-Platform: Configure once and use the same connector in Claude, Cursor, ChatGPT, and more
  • Full Visibility: All MCP activity is logged, secured, and controlled by your admins

​
Getting Started

​
First Login

Sign In
  1. Navigate to your organization’s Runlayer URL (provided by your admin)
  2. Click “Sign In” - You’ll be redirected to your organization’s Single Sign-On (SSO) page
  3. Log in with your work credentials - Same username and password you use for other company tools
My connectors After logging in, you’ll see the main dashboard with these key sections:
  • My connectors: Browse available connectors, request access, and open existing ones
  • Plugins / Skills / Agents / Deploy: Build reusable AI workflows on top of your connectors
  • Audit Logs: View activity history
  • Settings: Manage your profile and preferences
Admin users also see Analytics and additional management options. If you need admin access, contact your IT department.

​
Understanding MCP Servers

What is an MCP Server? An MCP server is like a plugin that extends what AI assistants can do. For example:
  • GitHub MCP: Lets AI read and manage your code repositories
  • Google Drive MCP: Gives AI access to your documents
  • Slack MCP: Allows AI to read messages and post updates
  • Database MCP: Connects AI to your company’s databases
Key Concepts:
  • Server: The MCP plugin itself (e.g., “GitHub Integration”)
  • Tools: Actions the MCP can perform (e.g., “create issue”, “search code”)
  • Resources: Data the MCP can access (e.g., repository files, issues)
  • Status:
    • Active - Ready to use
    • Pending - Waiting for admin approval
    • Inactive - Disabled or not configured
    • Rejected - Not approved for use

​
Finding Connectors

My connectors The My connectors page shows the connectors available in your workspace:
  1. Open My connectors in the left sidebar
  2. Browse or search for connectors by name
  3. Click on any connector to see details:
    • What it does
    • What tools it provides
    • What data it can access
    • Security considerations
  4. Click “Add connector” or “Request new” to start setup (see section below)

​
Connecting Connectors to Your AI Tools

You can connect existing connectors to Claude, ChatGPT, Cursor, or other AI tools. MCP Clients

​
Installation Steps

1

Open the Connector Details

Click on any active connector in My connectors
2

Select Your AI Tool

Choose your client from the dropdown (see supported clients below)
3

Complete Setup

Follow the instructions to complete the setup in your AI tool

​
Supported AI Tools & Clients

Runlayer provides tailored setup instructions for each of these clients: IDEs & Code Editors:
  • Cursor - One-click connect button
  • VS Code - One-click connect button
  • Windsurf - Configuration file setup
  • GitHub Copilot - Configuration file setup
AI Assistants:
  • Claude Desktop - Configuration file setup
  • Claude Code - CLI command setup
  • ChatGPT - Web UI connector setup
  • Codex - Proxy URL and API key setup
Terminal & CLI Tools:
  • Warp - Configuration file setup
  • Gemini CLI - Configuration file setup
  • OpenCode - Configuration file setup
Automation & Integration:
  • Gumloop - Proxy URL and API key setup
  • Raycast - Configuration file setup
SDKs (for developers):
  • TypeScript SDK - Code-based integration
  • Python SDK - Code-based integration
  • Instructions for any MCP-compatible client
Security Note: Your API key provides access to the connector’s MCP server. Never share your API key or configuration files publicly.

​
Requesting a New Connector

When you need a connector you don’t currently have access to, submit a request to your administrator for approval.

​
When to Request a Connector

Request a new connector when:
  • You need capabilities not available in your current connectors
  • You want to connect AI to a specific data source or API
  • Your workflow requires automation that a connector can provide
  • You’re following documentation that requires a specific connector

​
Before You Request

1

Check Existing Connectors

Browse My connectors to see if what you need already exists. You might just need access to an existing connector.
2

Prepare Justification

Be ready to explain:
  • What problem you’re solving
  • Why this specific connector is needed
  • What data it will access
  • Expected business value
3

Gather Technical Details

If requesting a custom connector, collect:
  • Server URL or connection details
  • Documentation link
  • Authentication requirements
  • Any configuration settings
Add Server

​
Request an Existing Connector

Best for: Standard connectors like GitHub, Slack, PostgreSQL, and other common tools.
1

Open My Connectors

Navigate to My connectors and find the connector you need
2

Click 'Add connector' or 'Request new'

On the connector card or details page, start the setup flow
3

Configure Settings

Fill in any required configuration:
  • API keys for external services
  • Database connection strings
  • Custom parameters
Many standard connectors are pre-configured and need minimal setup.
4

Add Justification

Explain why you need this connector and what you’ll use it for
5

Submit Request

Click “Submit” - the request goes to your IT admin for approval
6

Wait for Approval

You’ll receive a notification when your admin reviews the request
Note: Standard connectors are typically approved faster because they already match a known connector template.

​
Request a Custom Connector

Best for: Internal or one-off MCP servers that are not already available in Runlayer.
1

Open My Connectors

Click My connectors in the sidebar, then start a new connector request
2

Fill Basic Information

  • Name: Descriptive name (e.g., “Company Knowledge Base MCP”)
  • Description: What this connector does in 1-2 sentences
  • Category: Choose the appropriate category
3

Configure Connection

  • URL: The MCP server address (get this from the MCP developer)
    • Example: https://mcp.example.com
    • Or internal: http://internal-mcp.company.local:3000
  • Transport Type: Usually “Streamable HTTP” or “SSE”
4

Add Authentication (if needed)

  • Select auth type: OAuth, API Key, or None
  • Provide credentials if required
  • Configure OAuth settings if applicable
5

Set Environment Variables

Add any required configuration as key-value pairs
6

Submit for Review

Submit the request so administrators can review it
Note: Custom connectors require thorough security review by your admin team.

​
After Submission

Approval Once submitted:
  1. Status shows “Pending” in My connectors
  2. Administrators are notified automatically
  3. You receive a notification with a request ID
  4. Wait for review - Check back for updates

​
Requesting Access to Existing Connectors

If a connector exists but you don’t have access:
1

Verify It's Active

Check the connector status is “Active” (not Pending or Inactive)
2

Contact Your Administrator

Send a message to your admin or use your organization’s request system
3

Provide Context

Explain:
  • Which connector you need access to
  • Why you need it for your work
  • What tools you’ll use it with
4

Wait for Policy Update

Admin will create an access policy for you

​
Viewing Audit Logs

Audit Logs Every action in Runlayer is logged for security and compliance:
  1. Navigate to Audit Logs in the sidebar
  2. Filter by:
    • Date range
    • Action type (created, deleted, accessed, etc.)
    • User
    • Resource (specific connector / MCP server)
  3. Click on any log entry to see full details

​
Additional Resources

Admin Handbook

If you’re an admin, see the complete admin guide

Security Best Practices

Comprehensive security guidelines for MCP usage

Adding Custom MCPs

Technical guide for creating and deploying custom MCP servers

Quick Start

Deploy and configure Runlayer for your organization

​
Common Questions

Use Request new or contact your admin. Provide as much detail as possible:
  • Link to MCP documentation
  • What business problem it solves
  • What data it needs to access
  • Why existing connectors don’t work
Having connection issues or errors? See the MCP Troubleshooting Guide for step-by-step diagnostics and fixes.

​
Getting Help

  • Audit Logs: Check logs for error details and activity history
  • Documentation: Browse the full docs at your Runlayer instance
  • Email/Slack us: support@runlayer.com
  • Admin Contact: Reach out to your Runlayer admin for connector-specific questions