Integrations & MCP
VS Code & Cursor
Use Poly files directly in VS Code, Cursor, and other MCP-compatible IDEs.
Connect Poly to VS Code, Cursor, or any other MCP-compatible editor to give your coding assistant access to the specs, design assets, and reference material you keep in Poly.
VS Code
Add Poly to your MCP configuration — per-project in .vscode/mcp.json, or globally via MCP: Add Server in the command palette:
{
"servers": {
"poly": {
"type": "http",
"url": "https://mcp.poly.app/mcp"
}
}
}
Cursor
Add Poly to .cursor/mcp.json in your project (or ~/.cursor/mcp.json globally):
{
"mcpServers": {
"poly": {
"url": "https://mcp.poly.app/mcp"
}
}
}
Signing in
On first use your editor opens a browser window to sign you into Poly — the server authenticates with OAuth, so there are no API keys to generate or store in config files.
What your assistant can do
> pull the acceptance criteria from //Home/specs/checkout.md and scaffold the tests
> search my Poly for the brand color palette and apply it to this stylesheet
> read the API error codes doc in Poly and generate the enum
The tools behind these — search, fetch, and the cli command surface — are documented in Using MCP.
Using Claude Code inside your editor? Install the Claude Code plugin instead — it adds the agent skill on top of the MCP connection.