Pinata MCP
OfficialServer Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| PINATA_JWT | Yes | Your Pinata JWT API key | |
| GATEWAY_URL | No | Your Pinata gateway URL (e.g., example.mypinata.cloud) |
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
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
| resources | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| testAuthenticationB | Verify that your Pinata JWT is valid and working |
| searchFilesB | Search for files in your Pinata account by name, CID, or MIME type. Returns a list of files matching the given criteria. |
| getFileByIdC | Retrieve detailed information about a specific file stored on Pinata by its ID |
| updateFileC | Update metadata for an existing file on Pinata including name and key-value pairs |
| deleteFileC | Delete a file from your Pinata account by its ID |
| uploadFileC | Upload a file to Pinata IPFS. Provide either a file:// URI or base64-encoded content. |
| createPrivateDownloadLinkB | Generate a temporary download link for accessing a private IPFS file from Pinata |
| createLinkA | Create a direct access link for a file stored on Pinata IPFS. For public files returns a gateway URL, for private files generates a temporary download link. |
| fetchFromGatewayC | Fetch content from Public or Private IPFS via Pinata gateway and return it |
| listGroupsC | List groups in your Pinata account with optional filtering by name |
| createGroupC | Create a new group in your Pinata account to organize files |
| getGroupC | Retrieve detailed information about a specific group by its ID |
| updateGroupC | Update metadata for an existing group on Pinata |
| deleteGroupC | Delete a group from your Pinata account by its ID |
| addFileToGroupC | Add an existing file to a group in your Pinata account |
| removeFileFromGroupC | Remove a file from a group in your Pinata account |
| createPaymentInstructionA | Create a new x402 payment instruction for content monetization. Currently supports USDC (6 decimals) on Base/Base Sepolia only. |
| listPaymentInstructionsC | List and filter x402 payment instructions for content monetization |
| getPaymentInstructionC | Retrieve a specific x402 payment instruction by ID |
| updatePaymentInstructionC | Update an existing x402 payment instruction. Currently supports USDC (6 decimals) on Base/Base Sepolia only. |
| deletePaymentInstructionB | Delete an x402 payment instruction |
| listPaymentInstructionCidsC | List CIDs associated with a payment instruction |
| addCidToPaymentInstructionC | Associate a CID with a payment instruction for x402 monetization |
| removeCidFromPaymentInstructionC | Remove a CID association from a payment instruction |
| addSignatureC | Add an EIP-712 cryptographic signature to a CID for content verification |
| getSignatureC | Get signature details for a specific CID |
| deleteSignatureC | Remove a signature from a CID |
| createSignedUploadUrlC | Create a signed URL for client-side file uploads without exposing your API key |
| pinByCidA | Pin an existing CID from the IPFS network to your Pinata account |
| queryPinRequestsC | Query the status of pin by CID requests |
| cancelPinRequestC | Cancel a pending pin by CID request |
| vectorizeFileC | Vectorize a file for AI/semantic search capabilities |
| deleteFileVectorsC | Delete vectors for a file |
| queryVectorsC | Query vectorized files in a group using semantic search |
| listAllowedDirectoriesB | List all directories that this MCP server is allowed to access for file operations |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 35 tools
Most tools have distinct purposes targeting specific resources like files, groups, payment instructions, or signatures, with clear action verbs. However, some overlap exists: createLink and createPrivateDownloadLink both generate access links, and addFileToGroup/removeFileFromGroup could be confused with file operations like updateFile or deleteFile, though descriptions help differentiate.
Naming is mixed with camelCase (e.g., addCidToPaymentInstruction) and snake_case (e.g., query_pin_requests) patterns, causing inconsistency. Verb styles vary (e.g., 'add', 'create', 'delete', 'fetch'), but the structure is generally readable as verb-noun combinations, albeit without a uniform convention.
With 35 tools, the count is borderline high for a file storage and monetization server, suggesting potential over-scoping. While it covers many operations, it may feel heavy compared to typical well-scoped servers (3-15 tools), risking complexity for agents.
The tool set provides comprehensive CRUD/lifecycle coverage for the domain: full file management (upload, update, delete, search), group organization, payment instructions with CID associations, signature handling, and vectorization for AI. No obvious gaps exist; agents can perform end-to-end workflows without dead ends.