Pylon MCP
for LuumenAI

Pull Pylon ticket, contact, and account context into the terminal

Ask who reported an issue, what the account looks like, and how the thread went — PYLON_MCP_GET_ISSUE, PYLON_MCP_GET_ISSUE_MESSAGES, PYLON_MCP_SEARCH_ACCOUNTS, and PYLON_MCP_GET_ACCOUNT answer from the terminal. Filing with PYLON_MCP_CREATE_ISSUE is the same. Every Pylon call here is classified as a write, so by default it is previewed, approved, and logged. Connection is via OAuth with dynamic client registration.

Book a DemoDownload Luumen

The Pylon MCP toolbox

12 tools: 0 read, 12 write. Reads answer instantly. Writes require approval by default. Everything is logged.

  • WriteCreate issueCreate a new issue/ticket in Pylon. Approval by default
  • WriteGet accountGet full details for a Pylon customer account. Approval by default
  • WriteGet contactGet full details for a Pylon contact (customer). Approval by default
  • WriteGet issueGet full details for a Pylon support issue/ticket. Approval by default
  • WriteGet issue messagesGet the full message history for a Pylon issue. Approval by default
  • WriteGet meGet the currently authenticated user's details. Approval by default
  • WriteGet userGet full details for a Pylon user (team member). Approval by default
  • WriteSearch accountsSearch for customer accounts in Pylon. Approval by default
  • WriteSearch issuesSearch for issues/tickets in Pylon. Approval by default
  • WriteUpdate accountUpdate an existing customer account in Pylon. Approval by default
  • WriteUpdate issueUpdate an existing issue/ticket in Pylon. Approval by default
  • WriteUpload account filesUpload one or more files (e.g. Approval by default

Questions

How does LuumenAI connect to Pylon MCP?

Authorize once with OAuth 2.0. Luumen lists the scopes each action needs before you approve the connection, and credentials never appear in the chat.

Can LuumenAI change things in Pylon MCP on its own?

Read actions answer immediately. Anything that writes — create issue, get account, get contact, get issue, and more — is shown as a plan and requires approval by default. Administrators configure that per tool, so you decide exactly which actions can ever run unattended.

Who gets access to the integration?

You decide. Actions are granted per agent, skill, and team, and per environment — production is not staging. Read access can be broad while writes stay narrow.

Is there an audit trail?

Every call to Pylon MCP — read or write, approved or declined — is recorded with the actor, the input, and the result, and can be linked to the ticket or change record.

All integrations
Adobe Marketing Agent MCPAdobe Experience Platform context, sandbox switches, and async task statusAffindaRead parsed documents, collections, and annotations — change them with approvalAgent MailGive the agent its own mailbox for reading threads and sending updatesAI/ML APIInspect assistants, threads, and runs — and change them as approved steps

Put Pylon MCP to work with Luumen

Connect in minutes. Every action scoped, approved, and audited from day one.

Book a DemoDownload Luumen