Set up a feature with your agent

First-time setup pages include a feature preview, up to three setup steps and Set up with your coding agent. Creation pages offer the same assistance above the form. The preview is illustrative, not telemetry from your app.

Copy a scoped prompt#

1. Open the feature in the correct application and environment.
2. Choose View prompt to inspect the complete instructions and optionally name your framework, or Copy setup prompt to let the agent detect it.
3. Paste into your coding agent with the application's repository open.

The prompt includes organization and application identifiers, the selected environment, API origin, feature-specific instructions and documentation. It asks the agent to inspect existing code, preserve consent and permission checks, prepare changes and verify actual receipts. Copying is local; SaaS Pro does not send the prompt to an agent automatically.

No stored credentials are added. A public ingest key created on the Install page is available once, in that page's memory. View prompt lets you explicitly include it before copying. Leaving or reloading loses that value. Public keys can collect events and evaluate flags; they cannot manage the application. Secret ingest keys, provider credentials and management tokens are never added to the generated prompt. Existing key prefixes cannot be reconstructed into a full key.

Connect local MCP#

Choose Connect agent for Claude Code, Codex or Cursor configuration. The existing @saaspro/mcp package uses stdio and calls the Management API with SPM_TOKEN and SPM_HOST.

Set the token in your agent's protected environment or local MCP configuration. Keep credential-bearing config files out of Git. Use read scope for inspection, write for reviewed module changes, and admin only when ingest-key operations are required. Scopes do not grant permissions your membership lacks.

MCP has dedicated tools for the core workflows. Features without a dedicated tool can use a documented Management API endpoint. The prompt tells the agent to inspect the deployment's /api/v1/openapi.json before making requests and to leave console-only actions as explicit operator steps.

Cloud agents and ChatGPT#

An agent with an HTTPS API client can use the Management API from its protected server environment. Store SPM_TOKEN in that agent's secret store. A cloud agent cannot reach a localhost deployment; use the origin of the deployed instance you intend to access.

This deployment does not expose a hosted MCP transport or an OAuth connector for ChatGPT. Local MCP configuration is not a cloud connector URL. The connection dialog explains this boundary and offers the existing API workflow.

Data sources and exports#

Some setup tasks are completed in the console rather than a public API:

• PostgreSQL sources: create a read-only reporting source in Data integrations → Sources. Review the reporting table, tenant column and value, identity binding and allowed columns. The password, CA and join key belong in the vault. Read a bounded preview before approving scheduled snapshots.
• Storage exports: create an S3-compatible export in Data integrations → Exports. Review bucket, dedicated prefix, credential scope, selected events, bucket lifecycle and schedule. Approve data transfer before enabling delivery, then inspect its receipt and object.

The agent can prepare integration code and a configuration checklist without receiving these secrets in its prompt. It must not invent API routes for actions that the deployment only exposes in the console.

Finish with evidence#

A prompt being copied, a successful SDK install or a passing build is not a collection receipt. Review the changed files, complete any required console steps and verify the first real event, recording, trace, import or delivery in the selected environment. Production writes, external messages, paid runs and deployment remain deliberate operator decisions.