Pylon MCP server

What the model can do

Pylon B2B support: issues by state, assignee, account, tag or date with their messages and internal notes, accounts, contacts, tasks, team members, teams, issue statuses and knowledge-base articles. Can reply to a customer, draft a reply, add an internal note, create, update, snooze, merge or delete issues, add followers, create or update accounts and contacts, create, update and comment on tasks, create or update knowledge-base articles and invite a teammate.

Reads

• pylon_search_issuesPylon issues (support conversations and tickets) matching a state, assignee, account, requester, tag, words in the title or body…
• pylon_get_issueOne Pylon issue by id or by its number, with its messages oldest first: customer messages and internal notes (marked internal)…
• pylon_list_accountsPylon accounts (the customer companies): name, domain, type, owner, tags and latest customer activity.
• pylon_list_contactsPylon contacts (people at customer accounts): name, email, account and portal role.
• pylon_list_tasksPylon tasks: title, status (not_started, in_progress, completed), assignee, due date, account and project.
• pylon_list_usersPeople on the Pylon team (agents): id, name, email, role and status.
• pylon_list_kb_articlesPylon knowledge-base articles: title, whether published, URL and the published text cut to 800 characters.
• pylon_list_issue_statusesThe organisation's issue statuses: label, slug (what pylon_update_issue takes as state), category and whether archived.
• pylon_list_teamsPylon teams: id and name, with the number of members.

Acts, when you ask

These change something in Pylon. The model is told to use them only when you ask for exactly that, and each one is granted by name: per team on a shared connection, by the owner on a personal one.

• pylon_add_issue_noteAdds an internal note to a Pylon issue: context, what was checked, a hand-off.
• pylon_create_internal_issueCreates an internal Pylon issue on a customer account, for work the team needs to track ("investigate usage spike at Acme").
• pylon_create_taskCreates a Pylon task (an internal to-do) with a title and optionally details, an assignee, a due date, an account or a project.
• pylon_comment_on_taskAdds an internal comment to a Pylon task, visible only to your team.
• pylon_reply_to_issueSends a customer-facing reply on a Pylon issue.
• pylon_create_draft_replySaves a private draft customer reply on a Pylon issue without sending it.
• pylon_update_issueChanges a Pylon issue's state (new, waiting_on_you, waiting_on_customer, on_hold, closed or a custom slug from pylon_list_issue_statuses), assignee…
• pylon_snooze_issueSnoozes a Pylon issue until a future date and time, when it comes back to the queue.
• pylon_issue_followersAdds or removes followers on a Pylon issue: teammates by user id and customer contacts by contact id (at most 20 each).
• pylon_merge_issuesMerges duplicate Pylon issues (at most 20, all on the same account) into a primary issue, which keeps its id and receives their messages.
• pylon_delete_issuePermanently deletes a Pylon issue and its messages.
• pylon_create_accountCreates a Pylon account (a customer company) with a name and optionally its domains, type, owner and tags.
• pylon_update_accountUpdates a Pylon account's name, owner, domains (the list given replaces the old one), type (customer or partner), tags…
• pylon_create_contactCreates a Pylon contact (a person at a customer account) with a name and optionally an email and account.
• pylon_update_contactUpdates a Pylon contact's name, email (replaces all of their addresses with this one) or account (move them, or remove_from_account).
• pylon_update_taskUpdates a Pylon task's title, details, status, assignee, due date or project.
• pylon_create_kb_articleCreates a knowledge-base article in Pylon as an unpublished draft (customers cannot see it until someone publishes it).
• pylon_update_kb_articleEdits a Pylon knowledge-base article.
• pylon_invite_userInvites a person to the Pylon organisation: creates their user and emails them an invitation.

Connect it

First connect Pylon on Dashboard → Connections, then add Memtro to your client once. The Pylon tools appear alongside the tools of everything else you have connected; nothing is configured per connector.

claude plugin marketplace add memtro-org/claude-memtro
claude plugin install memtro@memtro --config api_key=sk-memtro-...

{
  "mcpServers": {
    "memtro": {
      "url": "https://platform.memtro.com/api/mcp",
      "headers": {
        "Authorization": "Bearer sk-memtro-..."
      }
    }
  }
}

{
  "mcp": {
    "memtro": {
      "type": "remote",
      "url": "https://platform.memtro.com/api/mcp",
      "headers": {
        "Authorization": "Bearer sk-memtro-..."
      }
    }
  }
}

Who may use it

The key identifies the person, and the server offers that person the tools they may use everywhere else in Memtro. A shared Pylon connection is used by the teams an administrator granted it to, tool by tool, on the Permissions page; a personal connection is used by its owner alone, and its tools that act stay off until the owner allows them. See Teams and permissions and Connectors.

Ask it like this

• › What open issues does Acme have, and who is on them?
• › Which issues have been waiting on us since Friday?
• › What did Northwind say in their latest ticket?
• › Reply on issue 482 that the fix ships Thursday
• › Merge Globex's two duplicate login issues into the older one

Questions

Is this an official Pylon MCP server?

No. It is Memtro's MCP server with Memtro's Pylon connector behind it: the connector reads Pylon through its API with the credentials you connect on Dashboard → Connections, and Pylon publishes nothing here. The same endpoint carries every other system you connect and Memtro's memory tools.

What does it cost?

Nothing on top of Memtro. One price per organisation by its number of users, from $50 a month for up to 10 users after a 7-day free trial, with every connector, the MCP server, jobs and memory included. You bring your own model keys.

Can it change anything in Pylon?

Only when you ask, and only what it has been granted: add an internal note to an issue; create an internal issue on an account (no customer is contacted); create a task; add an internal comment to a task; reply to a customer on an issue (they receive it); save a private draft reply on an issue (not sent); change an issue's state, assignee, team, title, type or tags; snooze an issue until a time; add or remove followers on an issue; merge duplicate issues into one (permanent, an optional closing message reaches each customer); delete an issue (permanent); create a customer account; update an account's name, owner, domains, type, tags or disabled flag; create a contact on an account (no portal access unless asked); update a contact's name, email or account; update a task's title, details, status, assignee, due date or project; create a knowledge-base article as an unpublished draft; edit a knowledge-base article, publishing only when asked; invite a person to the Pylon organisation (emails an invitation). Every other tool reads, searches or lists. An administrator grants each acting tool by name per team, and a personal connection acts only after its owner allows it.

Which clients work?

Any MCP client that speaks Streamable HTTP: Claude Code, Cursor, Claude Desktop, OpenCode, Codex, Zed, Windsurf, Cline and the Anthropic and OpenAI SDKs. There is no local process to run; the server is remote and authenticated with your key.

Other MCP servers · Support

• Help Scout MCP server
• Zendesk MCP server
• Intercom MCP server
• Freshdesk MCP server
• Front MCP server
• Zoho Desk MCP server