← ClaudeAtlas

right-mcplisted

Finds and adds MCP servers for this Right Agent agent. Searches for OAuth-capable endpoints first (Claude Code / Codex integration docs), falls back to API-key endpoints. All management goes through the user's Telegram dashboard MCP view — the agent never handles credentials directly. Use when the user asks to add, connect, or set up an MCP server or integration.
onsails/right-agent · ★ 22 · AI & Automation · score 77
Install: claude install-skill onsails/right-agent
@known-endpoints.yaml # /right-mcp -- Add MCP Server ## When to Activate Activate this skill when: - The user asks to add, connect, or set up an MCP server or integration - The user asks about connecting a third-party service via MCP - The user names a specific service and wants it added (e.g. "add Composio", "connect Linear") ## Architecture You have NO direct MCP management access. All management goes through the user's Telegram dashboard MCP view. Telegram `/mcp` opens that dashboard view. Here's what happens behind the scenes: - The **Right Agent MCP Aggregator** proxies all MCP traffic, stores tokens, and refreshes OAuth automatically. You never see or handle credentials. - The dashboard add flow auto-detects authentication: 1. Tries OAuth AS discovery on the URL and offers OAuth when discovered 2. Detects query-string auth (key embedded in URL) and can register as-is 3. For other URLs, detects header auth and asks the user for credentials in the dashboard - The dashboard starts browser-based OAuth, removes servers, and lists all servers with status. The built-in `right` server is protected. ## Procedure ### Step 1: Check current servers Call `mcp__right__rightmeta__mcp_list()` DIRECTLY by name — do NOT use ToolSearch (it does not index MCP tools) and do NOT delegate to a subagent (subagents have no MCP access). If the requested service is already connected, tell the user and stop. If the tool call fails, skip this step and continue. ### Step 2: Check