Skip to main content
Glama
picsha-ai

Picsha AI MCP Server

Official
by picsha-ai

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
PICSHA_API_TOKENYesYour Picsha AI API token, generated from the Picsha Admin Dashboard. Grants the AI agent access to your organization's library.
PICSHA_EXTERNAL_USER_IDNoOptional. Dynamically restricts the agent's context to a specific user by injecting their User ID. Used for sandbox mode or user isolation.

Capabilities

Features and capabilities supported by this server

CapabilityDetails
tools
{
  "listChanged": true
}
prompts
{
  "listChanged": true
}

Tools

Functions exposed to the LLM to take actions

NameDescription
search_assetsA

Search for assets in the Picsha AI platform using vector or standard keyword search. Note: If your agent instance is sandboxed to a specific user via environment variables, this search will ONLY return assets owned by that specific user. You are securely retrieving their contextual assets.

get_assetB

Retrieve detailed metadata and AI analysis results for a specific asset

reanalyze_assetB

Manually trigger AI re-analysis on an existing asset to detect faces, objects, etc.

summarize_assetB

Utilize Claude Sonnet via Amazon Bedrock to summarize documents on demand

get_rendered_asset_urlB

Generate a dynamic delivery URL for an asset with transformation parameters (e.g. width, height, format, smart crop)

upload_assetA

Upload a local file directly to the Picsha AI platform. This acts as a proxy, fetching a pre-signed S3 URL and executing the PUT request automatically. If your agent is running with user sandboxing, this file will automatically be securely bound to that user's identity. Note: Uploading immediately triggers the asynchronous 'picsha-ai-ingest' pipeline which will extract metadata, generate thumbnails, and run AI analysis (faces, tags, bedrcock summaries). Therefore, the returned asset will initially be in a 'pending' state. You should use the 'get_asset' tool a few seconds after uploading to retrieve the final AI-processed results.

list_recent_assetsB

List recently added assets in the Picsha platform. IMPORTANT: When replying to the user, ALWAYS format this as a clean Markdown table with columns for ID, Original Name, Status, and Date.

update_assetA

Update an asset's tags or custom metadata. Prefix a tag with a hyphen (e.g. '-discard') to remove it, or specify normally to add it.

delete_assetA

Permanently delete an asset from the database, search indexes, and physical storage.

moderate_assetB

Approve or reject a moderated asset pending manual review.

create_dam_groupA

Create a new Digital Asset Management (DAM) group/collection (folder) to organize assets.

link_assetsB

Link a source/parent asset to a target/child asset (e.g. variations, derived formats, social crops) with a custom relationship description.

trigger_url_ingestB

Ingest a public web asset directly into the Picsha AI platform by downloading and putting it through the ingestion pipeline.

escalate_to_supportA

Use this tool ONLY when you need to log a feature request, report a documentation gap, or escalate an issue to the engineering team. This will actually send an email to support@picsha.ai.

Prompts

Interactive templates invoked by user choice

NameDescription
analyze_asset_profileProvides a structured template to do a deep analysis of a media asset's metadata, EXIF details, and AI tags.
generate_social_campaignHelps generate platform-specific social media copy and smart crop parameters based on an asset's content.
image_magic_transformWalks the LLM and user through Picsha's generative AI fill and background removal parameters.

Resources

Contextual data attached and managed by the client

NameDescription

No resources

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/picsha-ai/mcp-server'

If you have feedback or need assistance with the MCP directory API, please join our Discord server