Skip to main content Announcing Tool Policies: AI agent permissions down to the field Read the announcement
Live 51 Actions

Tacton MCP Server
for AI Agents

Connect your AI agent to StackOne's Tacton MCP server and give it 51 MCP tools out of the box. Auth, tool execution, and security all managed.

Tacton logo
Tacton MCP Server
Built by StackOne StackOne
DrataGPLocalyzeFlipMindtoolsScreenloop

Coverage

51 Agent Actions

Agents can read, write, delete and run operations in Tacton. Extend your agent's capabilities with custom actions.

Authentication

Agent Tool Authentication

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

Agent Auth →

Security

Agent Protection

Every Tacton tool response scanned for prompt injection in milliseconds, with 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 Tacton call.

Tools Discovery →

What is the Tacton MCP Server?

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

All Tacton MCP Tools

Every StackOne action for Tacton, ready for your agent. Read, write, delete and run operations, scoped to exactly what you need.

Tickets

  • Create Ticket

    Create a new ticket in Tacton CPQ Administration.

  • List Tickets

    List tickets in Tacton CPQ Administration.

  • Get Ticket

    Retrieve a single ticket by id.

  • Update Ticket

    Update an existing ticket by id.

Ticket Integration Attributes

  • List Ticket Integration Attributes

    List integration attributes defined on a ticket.

  • Update Ticket Integration Attributes

    Add or remove integration attributes on a ticket from a raw XML document.

Product Modeling Assemblys

  • Create Product Modeling Assembly

    Create or replace an assembly in a ticket.

  • Get Product Modeling Assembly

    Retrieve an assembly defined in a ticket.

  • Delete Product Modeling Assembly

    Delete an assembly defined in a ticket.

Product Modeling Assembly By Names

  • Get Product Modeling Assembly By Name

    Retrieve an assembly defined in a ticket, by name.

  • Delete Product Modeling Assembly By Name

    Delete an assembly defined in a ticket, by name.

Product Modeling Attribute Categorys

  • Create Product Modeling Attribute Category

    Create or replace an attribute category in a ticket.

  • Get Product Modeling Attribute Category

    Retrieve an attribute category defined in a ticket.

  • Delete Product Modeling Attribute Category

    Delete an attribute category defined in a ticket.

Product Modeling Attribute Category By Names

  • Get Product Modeling Attribute Category By Name

    Retrieve an attribute category defined in a ticket, by name.

  • Delete Product Modeling Attribute Category By Name

    Delete an attribute category defined in a ticket, by name.

Product Modeling BoM Meta Data Propertys

  • Create Product Modeling BoM Meta Data Property

    Create or replace a BoM meta data property in a ticket.

  • Get Product Modeling BoM Meta Data Property

    Retrieve a BoM meta data property defined in a ticket.

  • Delete Product Modeling BoM Meta Data Property

    Delete a BoM meta data property defined in a ticket.

Product Modeling BoM Meta Data Property By Names

  • Get Product Modeling BoM Meta Data Property By Name

    Retrieve a BoM meta data property defined in a ticket, by name.

  • Delete Product Modeling BoM Meta Data Property By Name

    Delete a BoM meta data property defined in a ticket, by name.

Product Modeling Domains

  • Create Product Modeling Domain

    Create or replace a domain in a ticket.

  • List Product Modeling Domains

    List all domains defined in a ticket.

  • Get Product Modeling Domain

    Retrieve a domain defined in a ticket.

  • Delete Product Modeling Domain

    Delete a domain defined in a ticket.

Product Modeling Domain By Names

  • Get Product Modeling Domain By Name

    Retrieve a domain defined in a ticket, by name.

  • Delete Product Modeling Domain By Name

    Delete a domain defined in a ticket, by name.

Product Modeling Global Features

  • Create Product Modeling Global Feature

    Create or replace a global feature in a ticket.

  • List Product Modeling Global Features

    List all global features defined in a ticket.

  • Get Product Modeling Global Feature

    Retrieve a global feature defined in a ticket.

  • Delete Product Modeling Global Feature

    Delete a global feature defined in a ticket.

Product Modeling Global Feature By Names

  • Get Product Modeling Global Feature By Name

    Retrieve a global feature defined in a ticket, by name.

  • Delete Product Modeling Global Feature By Name

    Delete a global feature defined in a ticket, by name.

Product Modeling Modules

  • Create Product Modeling Module

    Create or replace a module in a ticket.

  • List Product Modeling Modules

    List all modules defined in a ticket.

  • Get Product Modeling Module

    Retrieve a module defined in a ticket.

  • Delete Product Modeling Module

    Delete a module defined in a ticket.

Other (14)

  • List Product Modeling Assemblies

    List all assemblies defined in a ticket.

  • List Product Modeling Attribute Categories

    List all attribute categories defined in a ticket.

  • List Product Modeling BoM Meta Data Properties

    List all BoM meta data properties defined in a ticket.

  • Transition Ticket

    Change the state of a ticket by taking one of its available transitions.

  • Bulk Create Product Modeling Assemblies

    Create, replace or delete assemblies defined in a ticket, in bulk.

  • Bulk Delete Product Modeling Assemblies

    Delete assemblies defined in a ticket, in bulk.

  • Bulk Create Product Modeling Attribute Categories

    Create, replace or delete attribute categories defined in a ticket, in bulk.

  • Bulk Delete Product Modeling Attribute Categories

    Delete attribute categories defined in a ticket, in bulk.

  • Bulk Create Product Modeling BoM Meta Data Properties

    Create, replace or delete BoM meta data properties defined in a ticket, in bulk.

  • Bulk Delete Product Modeling BoM Meta Data Properties

    Delete BoM meta data properties defined in a ticket, in bulk.

  • Bulk Create Product Modeling Domains

    Create, replace or delete domains defined in a ticket, in bulk.

  • Bulk Delete Product Modeling Domains

    Delete domains defined in a ticket, in bulk.

  • Bulk Create Product Modeling Global Features

    Create, replace or delete global features defined in a ticket, in bulk.

  • Bulk Delete Product Modeling Global Features

    Delete global features defined in a ticket, in bulk.

Set Up Your Tacton MCP Server in Minutes

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

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>"
      ]
    }
  }
}

Tacton MCP Server FAQ

Does StackOne have a Tacton MCP server?
Yes. StackOne offers a hosted Tacton MCP server with 51 pre-built actions, and every action is tested and QA'd by StackOne. Connect it to Claude, Cursor, and any other MCP client, or to any agent framework through the AI Action SDK. It ships with managed agent authentication, prompt injection defense, and tool discovery with server-side execution that preserve your agent's context window and keep reasoning performance.
Tacton MCP server vs direct API integration: what's the difference?
A Tacton MCP server and direct API integration serve different use cases. Direct API integration is for software-to-software work, where backend code calls Tacton. A Tacton MCP server is for AI agents that discover and call Tacton at runtime, such as MCP clients like Claude and Cursor, plus framework agents built with OpenAI, LangChain, or Vercel AI. StackOne provides both.
How does Tacton authentication work for AI agents?
Tacton authentication for AI agents works through a StackOne Connect Session. Create one via the dashboard or the SDK to get an auth link and ready-to-paste config for Claude Desktop, Cursor, and other MCP clients. Your user authenticates their own Tacton account; StackOne handles token exchange, storage, and refresh. Credentials never reach the LLM, and each user is isolated via origin_owner_id.
Are Tacton MCP tools vulnerable to prompt injection?
Yes. Tacton MCP tools can be vulnerable to indirect prompt injection. Any tool that reads user-written content, such as 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. It runs regex patterns in ~1ms, then a MiniLM classifier in ~4ms. Accuracy is 88.7%, and it runs entirely on CPU.
What is the context bloat of a Tacton agent and how do I avoid it?
Context bloat happens when Tacton tool schemas and API responses eat your Tacton agent's memory, preventing it from reasoning effectively. A single Tacton query can return a massive JSON response, and connecting multiple tools compounds the problem. Tools Discovery reduces it by loading only the tools relevant to each query.
Can I limit which actions my Tacton agent can access?
Yes. You can limit which actions your Tacton 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 Tacton MCP server?
Yes. You can create custom agent actions for your Tacton MCP server using Connector Builder. It's an integration agent your coding assistant (Claude Code, Cursor, or Copilot) can invoke to research Tacton's API, generate production-ready connector YAML, test against the live API, and validate before you ship.
When should I NOT use a Tacton MCP server?
Skip a Tacton MCP server if your integration is purely software-to-software, because direct Tacton 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 Tacton actions at runtime.
What AI frameworks and AI clients does the StackOne Tacton MCP server support?
The StackOne Tacton 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.