Connect
Optimize
Secure
Live 24 Actions
SPS Commerce MCP Server
for AI Agents
Connect your AI agent to StackOne's SPS Commerce MCP server and give it 24 MCP tools out of the box. Auth, tool execution, and security all managed.
SPS Commerce MCP Server
Built by 
StackOne
StackOne 
Coverage
24 Agent Actions
Create, read, update, and delete across SPS Commerce — and extend your agent's capabilities with custom actions.
Authentication
Agent Tool Authentication
Per-user OAuth in one call. Your SPS Commerce MCP server gets session-scoped tokens with zero credentials stored on your infra.
Agent Auth →
Security
Agent Protection
Every SPS Commerce 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 SPS Commerce call.
Tools Discovery →What is the SPS Commerce MCP Server?
A SPS Commerce MCP server lets AI agents read and write SPS Commerce data through the Model Context Protocol — Anthropic's open standard for connecting LLMs to external tools. StackOne's SPS Commerce MCP server ships with 24 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 SPS Commerce MCP Tools
Every action from SPS Commerce's API, ready for your agent. Create, read, update, and delete — scoped to exactly what you need.
Submission Forms
- List Submission Forms
List all available trading-partner submission forms (campaigns) on the SPS Commerce network.
- Get Submission Form
Retrieve a specific trading-partner submission form by ID.
Transactions
- List Transactions
List EDI transaction files in a directory on the SPS Commerce file space.
- Get Transaction
Download a specific EDI transaction file by its full path.
- Delete Transaction
Delete an EDI transaction file from the SPS Commerce file space.
Shipping Label Templates
- List Shipping Label Templates
List all GS1-128 / UCC-128 shipping-label templates available to the authenticated user.
- Get Shipping Label Template
Retrieve the details of a single shipping-label template by ID.
Packing Slip Templates
- List Packing Slip Templates
List all packing-slip templates available to the authenticated user.
- Get Packing Slip Template
Retrieve the details of a single packing-slip template by ID.
Other (15)
- Create Trading Partner Submission
Submit a new trading partner (supplier or retailer) for SPS Commerce onboarding.
- Create Transaction (Upload EDI File)
Upload a new EDI transaction file to the SPS Commerce file space.
- Get Shipping Label JSON Schema
Retrieve the JSON Schema (draft-07) for a shipping-label template.
- Get Shipping Label Sample JSON
Retrieve a sample JSON payload for a shipping-label template.
- Get Shipping Label Batch Status
Poll the status of a previously-submitted PDF or ZPL batch job.
- Get Packing Slip JSON Schema
Retrieve the JSON Schema (draft-07) for a packing-slip template.
- Get Packing Slip Sample JSON
Retrieve a sample JSON payload for a packing-slip template.
- View Interaction History
List file processing reports for transactions transmitted to/from SPS Commerce.
- Render Shipping Label Sample PDF
Render a sample PDF preview of a shipping label (no real data required).
- Render Shipping Label PDF
Render a retailer-compliant shipping label as PDF, populated with the supplied data.
- Render Shipping Label PDF Batch
Submit an async batch job to render a large set of shipping-label PDFs.
- Render Shipping Label ZPL
Render a retailer-compliant shipping label as ZPL (Zebra Printer Language).
- Render Shipping Label ZPL Batch
Submit an async batch job to render a large set of shipping labels as ZPL.
- Render Packing Slip Sample PDF
Render a sample PDF preview of a packing slip (no real data required).
- Render Packing Slip PDF
Render a retailer-compliant packing slip as PDF, populated with the supplied data.
SPS Commerce AI Agent Use Cases
Connect your AI agent to SPS Commerce and help your team scale the sales operations they run by hand today.
Post-Demo Follow-Up
Use StackOne to connect your AI agent to your CRM, email, and calendar tools to automate post-demo follow-up.
View Deal Risk Scoring
Use StackOne to connect your AI agent to your CRM, email, and calendar tools to automate deal risk scoring and pipeline alerts.
View Outbound Prospecting
Use StackOne to connect your AI agent to your CRM, sales engagement, and messaging tools to automate outbound prospecting.
ViewSet Up Your SPS Commerce MCP Server in Minutes
One endpoint. Any framework. Your agent is talking to SPS Commerce in under 10 lines of code.
Agent Frameworks
JSON{
"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>"
]
}
}
}Check More crm-sales MCP Servers
Capsule CRM
127+ actions
Bloomerang
104+ actions
Pipeliner CRM
59+ actions
Filevine
53+ actions
LeadDocket
26+ actions
Platform Resources
MCP Code Mode: Keeping Tool Responses Out of Agent Context
Anthropic's code_execution processes data already in context. Custom MCP code mode keeps raw tool responses in a sandbox. 14K tokens vs 500.
11 min
Comparing BM25, TF-IDF, and Hybrid Search for MCP Tool Discovery
Benchmarking BM25, TF-IDF, and hybrid search for MCP tool discovery across 916 tools. The 80/20 TF-IDF/BM25 hybrid hits 21% Top-1 accuracy in under 1ms.
10 min
Indirect Prompt Injection Defense for MCP Tools: A Technical Guide
MCP tools that read emails, CRM records, and tickets are indirect prompt injection vectors. Here's how we built a two-tier defense that scans tool results in ~11ms.
12 min
MCP vs A2A: Architecture, Security, and When to Use Each
MCP vs A2A: what each protocol standardizes, how they differ, their shared security risks including indirect prompt injection, and when to use one, both, or a hybrid architecture.
12 min
MCP vs API: What 200+ Connector Builds Taught Us
MCP wraps APIs, it doesn't replace them. After building 200+ connectors that serve both, here's when each approach wins.
14 min read
SPS Commerce MCP Server FAQ
Does StackOne have a SPS Commerce MCP server?
Yes. StackOne offers a hosted SPS Commerce MCP server with 24 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.
SPS Commerce MCP server vs direct API integration — what's the difference?
A SPS Commerce MCP server and direct API integration serve different use cases. Direct API integration is for software-to-software — backend code calling SPS Commerce. A SPS Commerce 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 SPS Commerce at runtime. StackOne provides both.
How does SPS Commerce authentication work for AI agents?
SPS Commerce 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 SPS Commerce account; StackOne handles token exchange, storage, and refresh. Credentials never reach the LLM, and each user is isolated via
origin_owner_id.Are SPS Commerce MCP tools vulnerable to prompt injection?
Yes — SPS Commerce 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 SPS Commerce agent and how do I avoid it?
Context bloat happens when SPS Commerce tool schemas and API responses eat your SPS Commerce agent's memory, preventing it from reasoning effectively. A single SPS Commerce 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 SPS Commerce agent can access?
Yes — you can limit which actions your SPS Commerce 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 SPS Commerce MCP server?
Yes — you can create custom agent actions for your SPS Commerce MCP server using Connector Builder. It's an integration agent your coding assistant (Claude Code, Cursor, or Copilot) can invoke to research SPS Commerce's API, generate production-ready connector YAML, test against the live API, and validate before you ship.
When should I NOT use a SPS Commerce MCP server?
Skip a SPS Commerce MCP server if your integration is purely software-to-software — direct SPS Commerce 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 SPS Commerce actions at runtime.
What AI frameworks and AI clients does the StackOne SPS Commerce MCP server support?
The StackOne SPS Commerce 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.