Scripts and CI

For automation, or an app that can't sign in, send a secret API key instead.

A secret API key (it starts with sk_) acts with the permissions of the person who created it. Create one in Settings → Integrations → AI agents or Settings → API keys, keep it out of source code, and revoke it there when you're done.

Shell

claude mcp add --transport http cueston https://app.cueston.com/api/mcp \
  --header "Authorization: Bearer $CUESTON_API_KEY"

~/.cursor/mcp.json

{
  "mcpServers": {
    "cueston": {
      "url": "https://app.cueston.com/api/mcp",
      "headers": { "Authorization": "Bearer YOUR_SECRET_KEY" }
    }
  }
}

Shell

curl -s https://app.cueston.com/api/mcp \
  -H "Authorization: Bearer $CUESTON_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"jsonrpc":"2.0","id":1,"method":"tools/list"}'

The CLI uses the same keys and can call any MCP tool from a terminal or a CI job.

Prompts

Ready-made workflows. Each ends with a preview and waits for your go-ahead before publishing.

Reference

Transport, sign-in, scopes, tokens and limits, for MCP client and tool builders.