Quickstart for agents

​

Give your agent this prompt

Follow https://print.app/docs/mcp/quickstart-agents and connect the Print.App MCP server to this agent.
Keep my secret key out of any file I commit, and tell me what you changed.

​

Steps for the agent

1. Get a secret key. Ask the user for a Print.App secret key (sk_…). If they have none, they create one in the admin under Secret keys, labelled for you. Never repeat the key back in chat.
2. Add the server for the tool you run in, at user level, never in a project file that gets committed:

   Tool	What to do
   Claude Code	claude mcp add --transport http --scope user printapp https://api.print.app/mcp --header "Authorization: Bearer <key>"
   Codex	Add [mcp_servers.printapp] with url = "https://api.print.app/mcp" and bearer_token_env_var = "PRINTAPP_SECRET_KEY" to ~/.codex/config.toml, and export PRINTAPP_SECRET_KEY=<key> in the user’s shell profile.
   Cursor	Add "printapp": { "url": "https://api.print.app/mcp", "headers": { "Authorization": "Bearer <key>" } } under mcpServers in ~/.cursor/mcp.json.
   VS Code	Add the server with a promptString input (password: true) to .vscode/mcp.json, as in MCP server → VS Code; VS Code asks the user for the key.
   ChatGPT, Claude	You can’t add these yourself. Tell the user to add a custom connector with the URL https://api.print.app/mcp (OAuth), then paste their key on the Print.App page that opens. Steps: MCP server.
   Anything else	A remote MCP server over Streamable HTTP at https://api.print.app/mcp, with the header Authorization: Bearer <key>.

3. Load it. Reload or restart the MCP servers if your tool needs it (Claude Code: start a new session; Cursor: refresh in MCP settings; VS Code: MCP: List Servers, then start printapp).
4. Check it. Call the get_account tool and show the user the store hostname it returns.
5. Report. Tell the user which file or setting you changed, and that revoking the key in the admin disconnects you.

​

Rules for the agent

• Keep the key out of project files, scripts and commits. User-level settings or environment variables only.
• A secret key can change anything in the store the API can. Use one key per agent.
• Upload images and SVGs with upload_file, then place them with asset. Never send SVG markup inline: the API’s firewall refuses it.
• Look at your work with preview_design after editing a design, and fix what looks wrong.

​

What you can do next

• Build a print-ready template from a brief: create_design, then edit_design, then preview_design.
• Upload a logo and add it to the editor’s graphics.
• Import a Google font and set up a brand palette.
• Put a design on a store product with set_product_designs, or share it with create_editor_link.
• Find customers’ submitted projects and their PDF links.

​

Go deeper