"Telegram login" matching MCP tools:

• bookA

  Aurinia — book across venues via your AI assistantA

  REAL action: book at a network venue on the user's behalf. provider_id + item (the venue interprets it). Doctor: item={date,time}. Hostel: item={check_in,check_out,guests,promo_code?} — do NOT ask for name/contact: identity comes from a one-time Telegram consent. Spa: item={date,time,procedure}. Hostel: book returns a HOLD with payment_url; the booking is finalized by PAYMENT, not by this call. CONSENT: do NOT ask for approval up front — just call book. ONLY if the call returns consent_url/telegram.consent_url (linked=false = not yet authorized at this venue) do you show that link to the user for a one-tap approval in Telegram, then retry. If consent_url_native (tg://...) is present, try to open it on the user's device (open/xdg-open/Start-Process — launches Telegram directly if installed). BUT tg:// fails SILENTLY without Telegram — so ALWAYS also show the user consent_url (https): t.me opens the app or offers to install it. Open once, then retry. If already authorized (consent given earlier) book succeeds IMMEDIATELY, with no prompts. Never ask for consent when you already have it.

  ConnectorNo auth

• web_session_listA

  Local MCPB

  Lists your web-automation login profiles: every SAVED login (persisted on disk, so web_login/web_navigate can reopen it without signing in again) plus which are currently OPEN. Each entry has `saved` (a persisted profile exists) and `open` (its window is live now, with url + title). Use it to check whether a login a recipe needs already exists before running it, instead of opening it and failing.

  ConnectorOAuth

• authenticateA

  1inch MCPA

  Call this to start or confirm 1inch Business login. HTTP 401 means you are still anonymous (initialize 200 is not login). After OAuth, call again until the result is authenticated: true with organizationId. Then use swap, orderbook, product_api, or debug. Do not treat a PaymentRequired / x402 result as login.

  ConnectorNo auth

• x711_agent_telegramA

  x711A

  Agent-to-agent messaging via Telegram — the fastest real-time channel between agents. Two modes: (1) Direct DM: provide target_agent_id to deliver a private message to that agent's operator on Telegram (they must have registered their Telegram via /api/agent/set-contact). (2) Group broadcast: omit target_agent_id to post to @x711criptic, the live x711 agent community on Telegram — all operators monitoring the group see your message instantly. Requires API key. Returns: { delivered, method: 'direct'|'group', to, note }. Cost: $0.02.

  ConnectorNo auth

• x711_agent_telegramA

  x711 — Universal Agent Gas StationB

  Agent-to-agent messaging via Telegram — the fastest real-time channel between agents. Two modes: (1) Direct DM: provide target_agent_id to deliver a private message to that agent's operator on Telegram (they must have registered their Telegram via /api/agent/set-contact). (2) Group broadcast: omit target_agent_id to post to @x711criptic, the live x711 agent community on Telegram — all operators monitoring the group see your message instantly. Requires API key. Returns: { delivered, method: 'direct'|'group', to, note }. Cost: $0.02.

  ConnectorNo auth

• list_examplesA

  EpsilonA

  List runnable Epsilon integration examples (Python cron DCA, LangChain tools, Vercel AI SDK tools, Telegram bot). Fetch full source with get_example. No API key required.

  ConnectorAPI key

• secureflows_build_login_urlA

  secure-flowsA

  Builds a correct hosted-login redirect URL. Needs no secureFlows token — safe to call at app-scaffolding time, before any user session exists, which is the phase most secureFlows integration mistakes happen in. Always targets /app/sessions/login (session apps). Never builds the legacy /app/login console URL, which returns a firebaseToken your SecureFlowsCallback handler cannot consume and causes an infinite redirect loop. Use this instead of hand-building the URL with URLSearchParams — hand-built login URLs are the #1 source of the login-loop and stale-renewal bugs documented in SKILL.md.

  ConnectorNo auth

• secureflows_build_login_urlA

  secureflows-mcpA

  Builds a correct hosted-login redirect URL. Needs no secureFlows token — safe to call at app-scaffolding time, before any user session exists, which is the phase most secureFlows integration mistakes happen in. Always targets /app/sessions/login (session apps). Never builds the legacy /app/login console URL, which returns a firebaseToken your SecureFlowsCallback handler cannot consume and causes an infinite redirect loop. Use this instead of hand-building the URL with URLSearchParams — hand-built login URLs are the #1 source of the login-loop and stale-renewal bugs documented in SKILL.md.

  ConnectorNo auth

• ask_human_verdictA

  Veredicto HumanoA

  Pagá $0.10 USDC en Base por el juicio subjetivo/cultural de una persona real (no un LLM) sobre una pregunta — especializado en contexto argentino. Sin pago adjunto devuelve los requisitos de pago x402; con el pago, crea el ticket y devuelve {ticket, resultToken, poll}. La respuesta del humano llega de forma asíncrona (minutos u horas) y vuelve a vos, el agente, por get_human_verdict: no llega por Telegram (Telegram es solo cómo la persona recibe la pregunta).

  ConnectorNo auth

• delete_connectionA

  BowmarkA

  Start deleting a saved login by the `id` `list_connections` returned. **This does not delete anything by itself:** a delete cannot be undone, so the USER confirms it, signed in on their Bowmark dashboard. It returns `confirmUrl` — give that link to the user; it opens a "Delete this login?" box with the login named, and the login is gone only after they press Delete there. Nothing you can call completes it for them. Only call this when the user asked to remove a saved login. To sign out of a site, use `logout_connection` instead. Never call it to "fix" a connection that is merely stale — `needs_reauth`/`expired` recover with a new sign-in, which refreshes the SAME login in place and needs no confirmation.

  ConnectorNo auth

• telegram_send_mediaA

  Lemma TelepathA

  Send a photo, document, video, audio or voice message to a real person or group from the user's Telegram. Irreversible and immediately visible — confirm the recipient and what is being sent before calling. Give exactly one source: • from_chat_id + from_message_id — forward a file that is already in the archive. Costs no upload and has no size limit, because Telegram already holds the file. Works only for messages the collector saw live; imported history has no file id. • url — a public http(s) link that Telegram fetches itself. In a private chat this is sent as the user. In a group there is no business connection, so it is sent as the bot — say so if that matters.

  Connector

  Destructive

  OAuth

• create_telegram_templateA

  QuintaDBB

  Створити Telegram-шаблон повідомлення. Вставляй 'html_name' поля в body БЕЗ жодних дужок (напр. Full Name). Отримай html_name через get_form_fields.

  ConnectorNo auth

• create_telegram_templateA

  QuintaDBB

  Створити Telegram-шаблон повідомлення. Вставляй 'html_name' поля в body БЕЗ жодних дужок (напр. Full Name). Отримай html_name через get_form_fields.

  ConnectorNo auth

• create_telegram_templateA

  QuintaDBB

  Створити Telegram-шаблон повідомлення. Вставляй 'html_name' поля в body БЕЗ жодних дужок (напр. Full Name). Отримай html_name через get_form_fields.

  ConnectorNo auth

• get_developer_profileA

  DevGlobeA

  Use when the user names a GitHub login or selects one DevGlobe search result and needs its public profile and contribution evidence. No authentication is required. Example: {"login":"sajeetharan"}.

  ConnectorNo auth

• messages_press_buttonA

  DialogBrainB

  Press a button under a message in a Telegram chat, as the connected Telegram account: the inline menus bots such as @BotFather reply with. Name the button by its exact label. Returns the message as it looks after the press (bots usually edit it into the next menu) and anything the bot sent after it, each with its own buttons and a message_id you can pass back to press the next one. Refused: buttons that need the account's cloud password (the owner confirms those in the Telegram app), and buttons that share a phone number or location, pay, or open a web app. A link button is not pressed; its URL is returned. A label that matches no button returns the buttons that exist. Get the message_id from messages.read_history. Telegram user accounts only; a bot account cannot press buttons.

  Connector

  Destructive

  API key

• messages_press_buttonA

  dialogbrainB

  Press a button under a message in a Telegram chat, as the connected Telegram account: the inline menus bots such as @BotFather reply with. Name the button by its exact label. Returns the message as it looks after the press (bots usually edit it into the next menu) and anything the bot sent after it, each with its own buttons and a message_id you can pass back to press the next one. Refused: buttons that need the account's cloud password (the owner confirms those in the Telegram app), and buttons that share a phone number or location, pay, or open a web app. A link button is not pressed; its URL is returned. A label that matches no button returns the buttons that exist. Get the message_id from messages.read_history. Telegram user accounts only; a bot account cannot press buttons.

  Connector

  Destructive

  API key

• messages_press_buttonA

  dialogbrainB

  Press a button under a message in a Telegram chat, as the connected Telegram account: the inline menus bots such as @BotFather reply with. Name the button by its exact label. Returns the message as it looks after the press (bots usually edit it into the next menu) and anything the bot sent after it, each with its own buttons and a message_id you can pass back to press the next one. Refused: buttons that need the account's cloud password (the owner confirms those in the Telegram app), and buttons that share a phone number or location, pay, or open a web app. A link button is not pressed; its URL is returned. A label that matches no button returns the buttons that exist. Get the message_id from messages.read_history. Telegram user accounts only; a bot account cannot press buttons.

  Connector

  Destructive

  API key

• telemost_ads_networksA

  telemost-mcp-serverA

  Telegram advertising data: available ad networks and their minimum deposits, compare where to run campaigns. Returns a JSON envelope {ok, data, meta}.

  ConnectorNo auth

• generate_otpA

  MyOTP.AppA

  Send a one-time password (OTP) to a phone number via SMS, WhatsApp, or Telegram. MyOTP.App generates the code, formats the message, picks the best carrier route, and delivers it. Returns a `message_id` (UUID) — keep it; you'll pass it to `verify_otp`, `check_otp_status`, or `extend_otp` later. Each call deducts credits from the account balance; the per-message cost varies by destination country and channel and is returned in the `cost` field. Use this whenever an app needs to verify someone's phone — signup, login 2FA, password reset, transaction confirmation, etc.

  ConnectorNo auth

• list_messenger_channelsA

  TuqoA

  List the project owner's Telegram and MAX channels and groups: candidates for set_site_subscribers_access. Read-only; channels are added and verified in the panel profile.

  ConnectorOAuth