Connect Remote MCP Servers with Elitea

​

Introduction

• Run independently on remote infrastructure
• Are accessed via HTTP/HTTPS APIs
• Support multiple concurrent connections
• Can be shared across teams and organizations
• Require network-based authentication (Bearer tokens, OAuth 2.0)

• Access cloud-based services like GitHub, Figma, Atlassian (Jira/Confluence)
• Use enterprise tools deployed on corporate infrastructure
• Share tool access across multiple ELITEA projects and teams
• Scale tool usage without local resource constraints
• Centralize authentication and access control

​

Remote vs Stdio MCP Servers

• Cloud-based integrations (GitHub, Figma, Atlassian)
• Enterprise SaaS tools requiring OAuth authentication
• Team-wide tool access shared across multiple users
• No local installation requirements
• Centralized credential management

• Local development tools (file system, browser automation)
• Custom tooling specific to your machine
• Minimal network latency for time-sensitive operations
• Tools requiring local system access

​

Prerequisites

• ✔️ Remote MCP Server URL: The HTTP/HTTPS endpoint for the MCP server
  • Example: https://api.githubcopilot.com/mcp/ or https://mcp.atlassian.com/v1/sse
• ✔️ Authentication Credentials: Depending on the server:
  • Bearer token (API key)
  • OAuth 2.0 client credentials (Client ID, Client Secret)
  • Custom authentication headers
• ✔️ ELITEA Project Access: Permissions to create and configure MCPs in your project
• ✔️ Network Access: Ability to reach the remote MCP server (check firewall/proxy settings)

• ELITEA account with toolkit creation permissions
• Network connectivity to remote MCP endpoints
• Valid authentication tokens for the MCP services you want to use

​

Authentication Methods

​

Bearer Token (API Key)

{
  "headers": {
    "Authorization": "Bearer your-api-token-here"
  }
}

• URL: MCP server endpoint (entered in separate field)
• Headers: JSON object with Authorization header

• API key-based services
• Internal corporate MCP servers
• Development and testing environments

​

OAuth 2.0 Client Credentials

1. Click “Get / Sync tools” in ELITEA MCP configuration
2. If OAuth is required, authorization modal appears
3. User clicks “Authorize” and completes OAuth flow in browser
4. ELITEA stores access token and refresh token
5. Token automatically refreshed when expired

• URL: MCP server endpoint (entered in separate field)
• Client ID: OAuth application client identifier
• Client Secret: OAuth application secret
• Scopes: OAuth permission scopes (space-separated or array)

• Initial discovery triggers OAuth flow
• Authorization modal shows OAuth metadata
• One-click authorization
• Automatic token management
• Re-authorization option available

• ✔️ Authorization Code Flow
• ✔️ PKCE (Proof Key for Code Exchange)
• ✔️ Refresh Tokens
• ✔️ Dynamic Client Registration (DCR)
• ✔️ Automatic token refresh
• ✔️ Multiple MCP server authentication

​

Custom Authentication Headers

{
  "headers": {
    "X-API-Key": "your-custom-key",
    "X-Client-ID": "your-client-id",
    "X-Project": "project-name"
  }
}

• URL: MCP server endpoint (entered in separate field)
• Headers: JSON object with custom authentication headers

• Internal tools with proprietary auth
• Multi-header authentication requirements
• Services requiring additional metadata headers

​

Remote MCP Configuration

​

Step-by-Step Setup in ELITEA

1. Navigate to MCPs in the left sidebar
2. Click + Create button
3. Select Remote MCP type from the form

• Name: Give your MCP a descriptive name (e.g., “GitHub MCP”, “Atlassian Integration”)
• Description: Optional - describe what this MCP provides

• URL (required): Enter the full HTTP/HTTPS endpoint
  • Example: https://api.githubcopilot.com/mcp/
  • Example: https://mcp.atlassian.com/v1/sse

• Headers (optional): JSON object with authentication headers
  • For Bearer token:
    {
      "Authorization": "Bearer ghp_yourGitHubTokenHere"
    }
    
  • For custom headers:
    {
      "X-API-Key": "your-key",
      "X-Custom-Header": "value"
    }
    

• Timeout (optional): Request timeout in seconds (default: 60, range: 1-3600)
• Enable Caching: Cache tool schemas for better performance (default: enabled)
• Cache TTL: Cache time-to-live in seconds (default: 300, range: 60-3600)

1. After entering URL (and headers if needed), click Get / Sync tools
2. ELITEA will connect to the remote MCP server
3. If OAuth is required:
   • Authorization modal appears
   • Click Authorize
   • Complete OAuth flow in new browser tab
   • Return to ELITEA - tools will load automatically
4. Available tools appear in the tools list

• By default, all tools are enabled
• Uncheck specific tools to exclude them
• Use Selected Tools field to filter tools by name

1. Review your configuration
2. Click Save
3. MCP is now available for use in agents, pipelines, and chats

​

Configuration Fields Reference

​

Example 1: GitHub Remote MCP Integration

• Repository analysis and code review
• Issue and pull request management
• Automated PR creation and updates
• Code search across repositories
• Branch and commit operations

​

Prerequisites

• GitHub Account with appropriate permissions
• Authentication credentials (choose one):
  • Personal Access Token for Bearer token authentication, OR
  • GitHub Copilot MCP OAuth credentials (Client ID and Client Secret) for OAuth flow
• Repository access for the tools you want to use

​

Obtaining GitHub Credentials

1. Go to GitHub Settings → Developer settings → Personal access tokens
2. Click Generate new token → Generate new token (classic)
3. Configure token:
   • Note: “ELITEA MCP Access”
   • Expiration: Choose appropriate duration
   • Select scopes:
     • ✔️ repo (Full control of private repositories)
     • ✔️ read:org (Read org and team membership)
     • ✔️ workflow (Update GitHub Actions workflows)
     • ✔️ read:user (Read user profile data)
4. Click Generate token
5. Copy the token immediately - you won’t see it again!

1. Contact GitHub or your organization’s GitHub administrator to obtain:
   • Client ID: OAuth application client identifier
   • Client Secret: OAuth application secret
2. Ensure the OAuth app has appropriate scopes (same as above)
3. Confirm the OAuth app’s Authorization callback URL is set to ELITEA’s redirect URI:
   https://<your-elitea-host>/mcp-auth-callback
   
   For example, on the ELITEA cloud instance: https://next.elitea.ai/mcp-auth-callback This value must be registered in the GitHub OAuth App settings under Authorization callback URL. If it doesn’t match, GitHub will reject the OAuth flow with a redirect URI mismatch error.

​

Configure GitHub MCP

• Name: GitHub MCP
• Description: GitHub repository management and automation tools

• URL: https://api.githubcopilot.com/mcp/

• Timeout: 90 seconds (GitHub operations can be slower)
• Enable Caching: ✔️ Enabled
• Cache TTL: 600 seconds (10 minutes)

Method 1: Bearer Token (recommended for individual use)

• Headers:
  {
    "Authorization": "Bearer ghp_your_github_token_here"
  }
  
• Client ID: Leave empty
• Client Secret: Leave empty
• Scopes: Leave empty

1. Click Get / Sync tools button
2. ELITEA connects directly to GitHub MCP server
3. Tools load immediately if token is valid
4. No additional authorization required

Method 2: OAuth (recommended for team/enterprise)

• Headers: {} (leave empty)
• Client ID: Your GitHub OAuth application client ID
• Client Secret: Your GitHub OAuth application client secret
• Scopes: Define required OAuth scopes based on your needs:

admin:repo_hook, admin:ssh_signing_key, audit_log, codespace, copilot, delete:packages, delete_repo, gist, notifications, project, repo, user, workflow, write:discussion, write:network_configurations, write:packages

1. Click Get / Sync tools button
2. Authorization modal appears automatically where you can provide or modify:
   • Client ID: OAuth application client identifier
   • Client Secret: OAuth application secret
   • Scopes: Required OAuth permission scopes
3. Click Authorize to proceed
4. GitHub OAuth page opens in new browser tab
5. Review and approve requested permissions
6. GitHub redirects back to ELITEA
7. Tools load automatically after successful authorization

​

Example 2: Atlassian Remote MCP Integration

• Jira issue tracking and project management
• Sprint planning and board management
• Confluence documentation generation
• Cross-platform reporting (Jira + Confluence)
• Automated ticket creation from incidents

​

Prerequisites

• ✔️ Atlassian Account with access to Jira and/or Confluence
• ✔️ Atlassian Cloud site with Jira, Confluence, and/or Compass
• ✔️ Site access to your Atlassian cloud instance
• ✔️ Product access: Users need access to Atlassian products they want to integrate
• ✔️ First-time setup: The first user to complete OAuth consent flow must have access to all requested products
• ✔️ Appropriate permissions for the operations you want to perform
• ✔️ Modern browser for completing OAuth 2.1 authorization flow

​

Configuring Atlassian Rovo MCP Server Domain Access

1. Go to Atlassian Administration
2. Select your organization if you have more than one
3. Navigate to Apps → AI settings → Rovo MCP server

1. Click Add domain
2. Enter your domain with required protocol format: (e.g, https://next.elitea.ai/**)
3. Click Add to save

1. Deselect Allow Atlassian supported domains
2. Only your manually added domains will be allowed

​

Step-by-Step Setup

• Name: Atlassian MCP
• Description: Jira and Confluence integration for project management and documentation

• URL: https://mcp.atlassian.com/v1/mcp !!! info “Atlassian Rovo MCP Endpoint” The official Atlassian Rovo MCP endpoint is https://mcp.atlassian.com/v1/mcp (recommended). The legacy /sse endpoint is still supported but Atlassian recommends updating to /mcp for new configurations.

• Timeout: 120 seconds (Atlassian operations can be slow)
• Enable Caching: ✔️ Enabled
• Cache TTL: 300 seconds (5 minutes)

• Headers: {} (leave empty)
• Client ID: (leave empty)
• Client Secret: (leave empty)
• Scopes: (leave empty)

1. Click Get / Sync tools button
2. Authorization modal appears automatically
3. Click Authorize to proceed
4. Atlassian OAuth page opens in new browser tab
5. Select your site and approve requested permissions
6. Atlassian redirects back to ELITEA
7. Tools load automatically after successful authorization

​

Testing MCP Tools

1. Navigate to MCPs → Click on your configured MCP
2. Locate the TEST SETTINGS panel displaying all available tools
3. Select a tool from the list to open its parameter form
4. Fill in required parameters (e.g., for github_create_issue: repository, title, body)
5. Click Run to execute the tool with your configured authentication
6. Review results in the output panel and verify in the target system

​

Use Remote MCP in Agents, Pipelines, and Chat

​

In Agents:

1. Navigate to Agents: Open the sidebar and select Agents.
2. Create or Edit Agent: Click + Create for a new agent or select an existing agent to edit.
3. Add Remote MCP:
   • In the “TOOLKITS” section of the agent configuration, click the “+MCP” icon
   • Choose your Remote MCP from the list (e.g., “GitHub MCP”, “Atlassian MCP”)
   • The MCP will be added to your agent with all configured tools available
4. Authorization (if required):
   • If the MCP requires OAuth authentication and you’re not already connected, a Log In button will appear next to the MCP
   • Click Log In to open the authorization modal
   • Complete the OAuth flow without leaving the agent editor
   • Once authorized, the MCP is ready to use

​

In Pipelines:

1. Navigate to Pipelines: Open the sidebar and select Pipelines.
2. Create or Edit Pipeline: Either create a new pipeline or select an existing pipeline to edit.
3. Add Remote MCP:
   • In the “TOOLKITS” section of the pipeline configuration, click the “+MCP” icon
   • Choose your Remote MCP from the list (e.g., “GitHub MCP”, “Atlassian MCP”)
   • The MCP will be added to your pipeline with all configured tools available for use in pipeline nodes
4. Authorization (if required):
   • If the MCP requires OAuth authentication and you’re not already connected, a Log In button will appear next to the MCP
   • Click Log In to open the authorization modal
   • Complete the OAuth flow without leaving the pipeline editor
   • Once authorized, the MCP is ready to use in pipeline nodes

​

In Chat:

1. Navigate to Chat: Open the sidebar and select Chat.
2. Start New Conversation: Click +Create or open an existing conversation.
3. Add Toolkit to Conversation:
   • In the chat Participants section, look for the MCP element
   • Click “+MCP” to add the MCP
   • Choose your Remote MCP from available options (e.g., “GitHub MCP”)
   • The MCP will be added to your conversation with all tools available
4. Authorization (if required):
   • If the MCP requires OAuth authentication and you’re not already connected, a Log In button will appear next to the MCP in the Participants section
   • Click Log In to open the authorization modal
   • Complete the OAuth flow without leaving the chat interface
   • Once authorized, the MCP is ready to use in your conversation
5. Use MCP in Chat: You can now directly interact with your remote MCP by asking questions or requesting actions that will trigger the MCP tools.

​

Best Practices

​

Troubleshooting

​

FAQ