Hosted API · secret-managed
Hosted configuration
Run the MCP process through your secret manager so it can resolve the API key at process start.
Model Context Protocol · stdio server
Connect your MCP client to ShotCurator.
Run the repository's MCP server on your machine and connect it to the hosted ShotCurator API. Your API key stays in the server process; it never passes through this page.
- Hosted API origin
- Authentication
Authorization: Bearer <api key>- HTTP contracts
- Request schemas, bounds, routes, and response notes live in the generated HTTP API reference.
Client configuration
Connect the MCP process to the hosted API.
Install the repository with Node 22 and pnpm, then add one configuration to your MCP client. The examples use 1Password references so no credential value is written to the configuration file.
Process environment
Configuration contract
Set the API origin to https://api.shotcurator.com and provide the bearer
API key through your secret manager.
Generated catalog
Choose the narrowest tool for the job.
Names, titles, and server descriptions are generated from the same metadata used by MCP registration. Usage and lifecycle notes make the still, legacy, and asynchronous paths explicit.