Skip to main content

Announcing StackOne Defender: leading open-source prompt injection guard for your agent Read More

Pylon MCP Server
for AI Agents

Production-ready Pylon MCP server with 52 extensible actions — plus built-in authentication, security, and optimized execution.

Pylon logo
Pylon MCP Server
Built by StackOne StackOne

Coverage

52 Agent Actions

Create, read, update, and delete across Pylon — and extend your agent's capabilities with custom actions.

Authentication

Agent Tool Authentication

Per-user OAuth in one call. Your Pylon MCP server gets session-scoped tokens with zero credentials stored on your infra.

Agent Auth →

Security

Agent Protection

Every Pylon tool response scanned for prompt injection in milliseconds — 88.7% accuracy, all running on CPU.

Prompt Injection Defense →

Performance

Max Agent Context. Min Cost.

Free up to 96% of your agent's context window to enhance reasoning and reduce cost, on every Pylon call.

Tools Discovery →

What is the Pylon MCP Server?

A Pylon MCP server lets AI agents read and write Pylon data through the Model Context Protocol — Anthropic's open standard for connecting LLMs to external tools. StackOne's Pylon MCP server ships with 52 pre-built actions, fully extensible via the Connector Builder — plus managed authentication, prompt injection defense, and optimized agent context. Connect it from MCP clients like Claude Desktop, Cursor, and VS Code, or from agent frameworks like OpenAI Agents SDK, LangChain, and Vercel AI SDK.

All Pylon MCP Tools and Actions

Every action from Pylon's API, ready for your agent. Create, read, update, and delete — scoped to exactly what you need.

Issues

  • Create Issue

    Create a new issue with specified title and body

  • List Issues

    Get a list of issues within a specified time range

  • Search Issues

    Search for issues by a given filter

  • Get Issue

    Get details of a specific issue by ID

  • Update Issue

    Update an existing issue by ID

  • Delete Issue

    Permanently delete an issue by ID (Admin only)

Issue Threads

  • Create Issue Thread

    Create a new internal thread on an issue

  • Get Issue Threads

    Get all threads on an issue

Contacts

  • Create Contact

    Create a new contact with specified email and optional metadata

  • List Contacts

    Get a paginated list of all contacts

  • Get Contact

    Get a contact by its ID

  • Search Contacts

    Search for contacts by a given filter

  • Update Contact

    Update an existing contact by ID

  • Delete Contact

    Permanently delete a contact by ID (Admin only)

Accounts

  • Create Account

    Create a new account with specified name and optional metadata

  • List Accounts

    Get a paginated list of all accounts

  • Get Account

    Get an account by its ID or external ID

  • Search Accounts

    Search for accounts by a given filter

  • Update Account

    Update an existing account by ID or external ID

  • Delete Account

    Permanently delete an account by ID (Admin only)

Custom Fields

  • List Custom Fields

    Get all custom field definitions for a specified object type

  • Get Custom Field

    Get a custom field definition by ID

  • Update Custom Field

    Update an existing custom field definition by ID

Feature Requests

  • Search Feature Requests

    Search or list feature requests with filters and semantic search

  • Get Feature Request

    Get a feature request by ID with optional evidence

  • Update Feature Request

    Update an existing feature request by ID

  • Delete Feature Request

    Permanently delete a feature request by ID

Articles

  • Create Article

    Create a new article within a knowledge base

  • Get Article

    Get a knowledge base article by ID

  • Update Article

    Update an existing knowledge base article by ID

  • Delete Article

    Permanently delete a knowledge base article by ID

Teams

  • Create Team

    Create a new team with name and optional members

  • List Teams

    Get a list of teams in the organization

  • Get Team

    Get a team by its ID

  • Update Team

    Update an existing team by ID

Users

  • List Users

    Get a list of users in the organization

  • Get User

    Get a user by its ID

  • Update User

    Update an existing user by ID

Other (14)

  • Create Internal Note

    Post an internal note on an issue thread

  • Get Organization Info

    Get details of the organization associated with the API token

  • Get Issue Messages

    Get all messages on an issue

  • Get Issue Followers

    Get the list of followers for an issue

  • List Knowledge Bases

    Get all knowledge bases in the organization

  • List Tags

    Get all tags in the organization

  • List Ticket Forms

    Get all ticket forms in the organization

  • List User Roles

    Get a list of all user roles

  • Update Multiple Accounts

    Update multiple accounts in bulk with specified properties

  • Delete Message

    Permanently delete a message from an issue

  • Reply To Issue

    Send a customer-facing reply on an issue

  • Redact Message

    Permanently redact a message's content

  • Snooze Issue

    Snooze an issue until a specified date and time

  • Manage Issue Followers

    Add or remove followers to/from an issue

Set Up Your Pylon MCP Server in Minutes

One endpoint. Any framework. Your agent is talking to Pylon in under 10 lines of code.

MCP Clients

Agent Frameworks

Claude Desktop
{
  "mcpServers": {
    "stackone": {
      "command": "npx",
      "args": [
        "-y",
        "mcp-remote@latest",
        "https://api.stackone.com/mcp?x-account-id=<account_id>",
        "--header",
        "Authorization: Basic <YOUR_BASE64_TOKEN>"
      ]
    }
  }
}

More Customer Support MCP Servers

Pylon MCP Server FAQ

Pylon MCP server vs direct API integration — what's the difference?
A Pylon MCP server and direct API integration serve different use cases. Direct API integration is for software-to-software — backend code calling Pylon. A Pylon MCP server is for AI agents — MCP clients like Claude and Cursor, plus framework agents built with OpenAI, LangChain, or Vercel AI — discovering and calling Pylon at runtime. StackOne provides both.
How does Pylon authentication work for AI agents?
Pylon authentication for AI agents works through a StackOne Connect Session. Create one via the dashboard or the SDK — you get an auth link and ready-to-paste config for Claude Desktop, Cursor, and other MCP clients. Your user authenticates their own Pylon account; StackOne handles token exchange, storage, and refresh. Credentials never reach the LLM, and each user is isolated via origin_owner_id.
Are Pylon MCP tools vulnerable to prompt injection?
Yes — Pylon MCP tools can be vulnerable to indirect prompt injection. Any tool that reads user-written content — documents, messages, tickets, records, or free-text fields — is a potential vector. StackOne Defender scans every tool response before it enters the agent's context — regex patterns in ~1ms, then a MiniLM classifier in ~4ms. 88.7% accuracy, CPU-only.
What is the context bloat of a Pylon agent and how do I avoid it?
Context bloat happens when Pylon tool schemas and API responses eat your Pylon agent's memory, preventing it from reasoning effectively. A single Pylon query can return a massive JSON response, and connecting multiple tools compounds the problem. Tools Discovery and Code Mode reduce context bloat — loading only relevant tools per query and keeping raw responses out of the agent's context.
Can I limit which actions my Pylon agent can access?
Yes — you can limit which actions your Pylon agent can access directly from the StackOne dashboard. Toggle actions on or off, or restrict them to specific accounts, with no code changes to your agent. Session tokens can be scoped to exact actions so if one leaks, exposure stays contained.
Can I create custom agent actions for my Pylon MCP server?
Yes — you can create custom agent actions for your Pylon MCP server using Connector Builder. It's an integration agent your coding assistant (Claude Code, Cursor, or Copilot) can invoke to research Pylon's API, generate production-ready connector YAML, test against the live API, and validate before you ship.
When should I NOT use a Pylon MCP server?
Skip a Pylon MCP server if your integration is purely software-to-software — direct Pylon API integration is simpler when no AI agent is involved. For deterministic, compliance-critical operations (financial transactions, regulatory reporting), direct API gives you predictable behavior without agent-driven decision-making. MCP shines when AI agents need to dynamically discover and call Pylon actions at runtime.
What AI frameworks and AI clients does the StackOne Pylon MCP server support?
The StackOne Pylon MCP server supports both. MCP clients (paste-and-go apps): Claude Desktop, Claude Code, Cursor, VS Code, Goose. Agent frameworks (code SDKs you build with): OpenAI Agents SDK, Anthropic, Vercel AI, Google ADK, CrewAI, Pydantic AI, LangChain, LangGraph, Azure AI Foundry.

Put your AI agents to work

All the tools you need to build and scale AI agent integrations, with best-in-class connectivity, execution, and security.