Picsha AI
ai.picshaPublished by picsha.aiOfficial publisherv1.0.3Updated Oct 25, 2026
AI-native digital asset management: semantic search, generative image edits, and CDN delivery.
Overview
Picsha AI is a digital asset management server that lets an assistant semantically search image assets, apply generative edits, and deliver them via CDN.
- What you can do
- Search and retrieve image assets in a Picsha library using semantic search, and deliver them through CDN links. Apply generative image edits to existing assets. Record an end user as the owner of uploads, or scope a session to a single end user in multi-tenant setups. The manifest lists no individual tools, so exact operations are not documented here.
- When to use it
- Useful when an assistant needs to find images in a managed asset library, make AI-generated edits to them, or serve them through a CDN, especially in multi-tenant products where uploads must be attributed to a specific end user.
- Requirements
- A Picsha account and API key, supplied as PICSHA_API_KEY for the local npm package or as an Authorization Bearer token for the remote endpoint. OAuth authentication is declared as required. The optional x-external-user-id header or PICSHA_EXTERNAL_USER_ID variable scopes or attributes a session to one end user. The local package runs on Node.js over stdio; the remote endpoint is reached over HTTP.
Installation
In SourceWeft
- Open Picsha AI in the dashboard and add it to a workspace.
- Connect the required credentials. They are stored privately and never shown on public pages.
- Enable the server for the chats that should use its tools.
Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.
Use with an agent
Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.
Read https://sourceweft.com/mcp/ai.picsha%2Fpicsha/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.Other MCP clients
Add this to your client's mcpServers config. The client completes OAuth sign-in on first connect.
{
"mcpServers": {
"picsha-ai": {
"type": "http",
"url": "https://api.picsha.ai/v1/mcp"
}
}
}Tools
0Version history
3- v1.0.3LatestOct 1, 2026
- v1.0.2Sep 30, 2026
- v1.0.1Sep 16, 2026
Score
50% of the applicable checks met
How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.
- Reached in the last 30 daysRequired25 pts
- Auth declaredRequired10 pts
- Tools listed15 pts
Answer tools/list without a credential, or ship a package that starts in a sandbox without one.
- DescriptionRequired15 pts
- Logo10 pts
Publish an icon in the registry entry.
- Documentation15 pts
Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.
- License10 pts
Declare a license in the repository or the registry entry.