PicX MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| REDIS_URL | Yes | Valkey/Redis URL. Backs tasks, response cache, OAuth storage. | |
| PICX_API_KEY | Yes | Your PicX API key from https://ai.picxstudio.com/api | |
| PICX_API_BASE | No | PicX API root. Must end in /v1. | https://api.picxstudio.com/v1 |
| JWT_SIGNING_KEY | No | Explicit JWT key. Without it, tokens die when the OAuth client secret rotates. | |
| GOOGLE_CLIENT_ID | No | Google OAuth client ID. | |
| PICX_MCP_BASE_URL | No | Public URL for OAuth callbacks. | https://mcp.picxstudio.com |
| REQUEST_STATE_KEY | Yes | ≥32 bytes, byte-identical across all replicas. Protects interactive round state. | |
| GOOGLE_CLIENT_SECRET | No | Google OAuth client secret. | |
| SESSION_CREDIT_CEILING | No | Max credits one MCP session may spend, independent of the account's daily cap. | 2000 |
| STORAGE_ENCRYPTION_KEY | No | Fernet key. Without it, upstream OAuth tokens are stored in plaintext. | |
| CONFIRM_CREDIT_THRESHOLD | No | Above this, the tool returns input_required to confirm before spending. | 200 |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
No tools | |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
This server cannot be deployed
Maintenance
ActivityMaintained
ResponsivenessNo issues