Connect
Optimize
Secure
Live 27 Actions
Polymer MCP Server
for AI Agents
Connect your AI agent to StackOne's Polymer MCP server and give it 27 MCP tools out of the box. Auth, tool execution, and security all managed.
Polymer MCP Server
Built by 
StackOne
StackOne 
Coverage
27 Agent Actions
Create, read, update, and delete across Polymer — and extend your agent's capabilities with custom actions.
Authentication
Agent Tool Authentication
Per-user OAuth in one call. Your Polymer MCP server gets session-scoped tokens with zero credentials stored on your infra.
Agent Auth →
Security
Agent Protection
Every Polymer 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 Polymer call.
Tools Discovery →What is the Polymer MCP Server?
A Polymer MCP server lets AI agents read and write Polymer data through the Model Context Protocol — Anthropic's open standard for connecting LLMs to external tools. StackOne's Polymer MCP server ships with 27 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 Polymer MCP Tools
Every action from Polymer's API, ready for your agent. Create, read, update, and delete — scoped to exactly what you need.
Candidates
- List Candidates
List the candidates in your Polymer Hire organization.
- Get Candidate
Retrieve a single candidate by ID.
Comments
- Create Comment
Add an internal comment to a job application.
- List Comments
List the comments on a Polymer Hire job application.
- Update Comment
Update an existing comment on a job application.
- Delete Comment
Delete a comment from a job application.
Job Applications
- Import Job Application
Import a candidate as a job application without triggering the apply flow.
- List Job Applications
List the job applications in your Polymer Hire organization.
- Get Job Application
Retrieve a single job application by ID.
Jobs
- List Jobs
List the jobs in your Polymer Hire organization.
- Get Job
Retrieve a single job by ID.
Reviews
- Create Review
Add a review with an optional rating to a job application.
- List Reviews
List the reviews on a Polymer Hire job application.
- Update Review
Update an existing review on a job application.
- Delete Review
Delete a review from a job application.
Other (12)
- List Hiring Stage Events
List the hiring stage history of a job application.
- List Job Hiring Stages
List the hiring pipeline stages for a job.
- Get Resume Export Status
Check the status of a resume export job.
- List Messages
List the messages exchanged on a Polymer Hire job application.
- Get Organization
Retrieve details of the current Polymer Hire organization.
- List Active Users
List the active users in your Polymer Hire organization.
- List Deactivated Users
List the deactivated users in your Polymer Hire organization.
- Get Organization User
Retrieve a single organization user by ID.
- Move Application Stage
Move a job application to a different hiring stage.
- Apply (Create Job Application)
Submit a new application to a job on behalf of a candidate.
- Archive Application
Archive a job application.
- Start Resume Export
Start an asynchronous resume export job for a job posting.
Set Up Your Polymer MCP Server in Minutes
One endpoint. Any framework. Your agent is talking to Polymer 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 Documents & Knowledge MCP Servers
Confluence
145+ actions
Lokalise
101+ actions
NinjaOne
96+ actions
ClickUp
95+ actions
Liferay
92+ actions
Google Shopping
80+ actions
Discourse
67+ 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
Polymer MCP Server FAQ
Does StackOne have a Polymer MCP server?
Yes. StackOne offers a hosted Polymer MCP server with 27 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.
Polymer MCP server vs direct API integration — what's the difference?
A Polymer MCP server and direct API integration serve different use cases. Direct API integration is for software-to-software — backend code calling Polymer. A Polymer 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 Polymer at runtime. StackOne provides both.
How does Polymer authentication work for AI agents?
Polymer 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 Polymer account; StackOne handles token exchange, storage, and refresh. Credentials never reach the LLM, and each user is isolated via
origin_owner_id.Are Polymer MCP tools vulnerable to prompt injection?
Yes — Polymer 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 Polymer agent and how do I avoid it?
Context bloat happens when Polymer tool schemas and API responses eat your Polymer agent's memory, preventing it from reasoning effectively. A single Polymer 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 Polymer agent can access?
Yes — you can limit which actions your Polymer 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 Polymer MCP server?
Yes — you can create custom agent actions for your Polymer MCP server using Connector Builder. It's an integration agent your coding assistant (Claude Code, Cursor, or Copilot) can invoke to research Polymer's API, generate production-ready connector YAML, test against the live API, and validate before you ship.
When should I NOT use a Polymer MCP server?
Skip a Polymer MCP server if your integration is purely software-to-software — direct Polymer 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 Polymer actions at runtime.
What AI frameworks and AI clients does the StackOne Polymer MCP server support?
The StackOne Polymer 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.