MCP for agents
Use MCP when an agent host should discover SorryAssets tools and generate digital assets without operating the GUI.
What the MCP path is for
- List catalog capabilities and public model ids.
- Estimate cost before spending.
- Submit generation tasks.
- Poll task status.
- Read the public Skills catalog.
The desktop app has its own local MCP bridge for app-connected workflows. Use the source MCP server when you want direct backend access.
Host config
Build the source MCP server, then point your host at the compiled entry.
{
"mcpServers": {
"sorryassets": {
"command": "node",
"args": ["/absolute/path/to/apps/mcp-server/build/index.js"],
"env": {
"SORRYASSETS_API_KEY": "sa_your_key",
"SORRYASSETS_API_URL": "https://sorryassets.com"
}
}
}
}
Boundary
The agent holds only an account-scoped sa_ key. It never receives provider credentials, upstream channel ids, wholesale prices, or upstream URLs.
Reasoning remains in the calling agent. SorryAssets is the generation and asset-workflow tool layer, not a server-side LLM.