HELPETO MCP

Move from a customer ticket to the project that can fix it.

Helpeto's remote MCP server gives Codex and Claude structured, permission-checked access to the support context you choose. The coding agent stays in your repository; Helpeto supplies the ticket, thread, metadata, and safe workflow actions.

helpeto · MCPOAuth 2.1

$ codex mcp add helpeto --url https://www.helpeto.com/mcp

OAuth connected · North Studio

> Find waiting tickets tagged bug

HLP-000184

Checkout fails after address update

waiting · bug · 14m

search_ticketsget_ticketadd_internal_note
Ticket context comes from Helpeto; the coding agent works in the repository you opened.
OAuth 2.1 authorization
Workspace-scoped ticket tools
Audited read and write actions

INSTALLATION

Connect Helpeto in about five minutes.

Choose the client you use. Helpeto opens a secure browser sign-in, asks which workspace to connect, and returns you to the project where the fix will be made.

CodexClaude Code
No API key to pasteNo server to operate
  1. 01

    Add the remote server

    Run this once in Terminal. Codex App, CLI, and the IDE extension share the same MCP configuration.

    codex mcp add helpeto --url https://www.helpeto.com/mcp
  2. 02

    Authorize your workspace

    A browser window opens. Sign in to Helpeto, choose a workspace, review the permissions, and approve.

    codex mcp login helpeto
  3. 03

    Confirm the connection

    List configured servers, or type /mcp inside Codex to see Helpeto and its available tools.

    codex mcp list

What happens next?

You can revoke the connection anytime from Helpeto → Settings → Developer MCP.

  • 1Helpeto returns only tickets from the workspace you approved.
  • 2The coding agent reads the ticket context while working in your already-open project.
  • 3Customer replies require explicit confirmation; deletion stays unavailable and every write is audited.
01

CONNECT

One remote endpoint, no server for you to operate

Add https://www.helpeto.com/mcp to a compatible MCP client and sign in through Helpeto. OAuth binds the connection to your user, selected workspace, role, and approved scopes; long-lived secrets are never pasted into project files.

  • Streamable HTTP transport
  • PKCE-protected browser authorization
  • Codex and Claude Code support
  • Revocable connections in workspace settings
02

CONTEXT

Let the agent search first, then open only the relevant ticket

The agent can filter by status, assignee, unread state, tag, time, or text before loading a full thread. Ticket reads include customer context, messages, attachment metadata, activity, category, and labels without dumping the whole support database into a prompt.

  • Search waiting, open, or assigned tickets
  • Read the latest structured conversation window
  • See attachment names and content types
  • Keep customer content marked as untrusted data
03

BUILD

Fix the bug where the code already lives

After understanding the ticket, Codex or Claude can inspect the repository you opened, reproduce the problem, implement a fix, run tests, and prepare a pull request. Helpeto does not clone repositories, execute customer code, or host coding sandboxes.

04

GUARDRAILS

Useful writes with explicit approval for customer replies

Authorized support members can add a private investigation note, move a ticket between open, waiting, and closed, or send a real reply through the connected mailbox after approving its exact text. The reply tool targets the ticket's latest inbound sender and requires an explicit confirmation flag. Deletion stays unavailable, and every call is tenant-scoped, rate-limited, permission-checked, and written to an audit trail.

HELPETO

Give your coding agent the ticket context, not a copied paragraph.

Create a Helpeto workspace, connect your support inbox, and add the remote MCP endpoint from developer settings.

Start free