Connect Cursor, VS Code and other MCP clients
The endpoint, the transport and the two ways to authenticate for any MCP-compatible client.
Polytender speaks standard MCP over streamable HTTP, so any compliant client works.
| Endpoint | https://api.polytender.com/mcp |
| Transport | Streamable HTTP |
| Auth | OAuth 2.1 (discovery and dynamic registration supported), or a personal API key as a bearer token |
Configuration
Most clients accept a JSON block like this:
{
"mcpServers": {
"polytender": {
"type": "http",
"url": "https://api.polytender.com/mcp",
"headers": { "Authorization": "Bearer pt_your_key" }
}
}
}Create the key under API keys in the app, see API keys and connected apps.
Clients that implement the OAuth flow (Claude Code, Cursor and others) can omit the header: the first call returns a 401 with a discovery pointer, the client runs the flow and you authorize in the browser.
Cursor
Add the block above to your MCP configuration (Settings → MCP → Add server, or
the mcp.json file Cursor points you at), then reload. Polytender appears in
the tool list and can be used in chat.
VS Code
Use an MCP-capable extension and register the same endpoint. With an API key the header form above is the simplest setup.
Verifying the connection
Ask for something that needs no organization data:
List the Polytender sources and when they were last synced.If that answers, the transport and authentication work. If it fails, see Troubleshooting.