Pinata MCP integration for AI agents.
Connect AI agents to Pinata through 12 structured actions, including get file, add file to group, delete file, and pin by cid. Review authentication, inputs…
- ACTION CONTRACTS
- 12
- AUTHENTICATION
- API key
- SOURCE STATUS
- Provider-backed
CATALOG SOURCE REVIEWED AUGUST 23, 2026 / ACTION NAMES AND SCHEMAS DERIVED FROM WORKING MACHINES PROVIDER SOURCE
CAPABILITY PROFILE
What the Pinata integration exposes
The Pinata Agent App exposes 12 provider-backed actions for developer tools and storage work. Its current contract lets an authorized agent get one pinata file by id from the public or private ipfs network, add a pinata file to a pinata group, and delete one pinata file by id from the public or private ipfs network. These operations are called through Working Machines as typed capabilities rather than through browser navigation or copied UI steps.
A connection uses API key. Before execution, the agent can inspect the selected action, its required fields, declared scopes, and expected output contract. Provider credentials remain inside the Working Machines runtime; the calling agent receives the capability and its structured result, not the underlying secret.
For reliable operation, start with the narrowest action that satisfies the task, resolve stable provider identifiers before changing state, and validate the returned object or status after execution. Availability still depends on the connected Pinata account, granted provider permissions, workspace policy, region, plan, and upstream API behavior.
VERIFIED ACTION SAMPLE
Real Pinata capabilities.
Showing 12 of 12 actions. Risk labels are conservative signals based on operation names, not substitutes for provider documentation or runtime policy.
get_fileREADGet one Pinata file by ID from the public or private IPFS network.
INPUTS: network / id
add_file_to_groupWRITEAdd a Pinata file to a Pinata group.
INPUTS: network / groupId / fileId
delete_fileHIGH IMPACTDelete one Pinata file by ID from the public or private IPFS network.
INPUTS: network / id
pin_by_cidREVIEWAsk Pinata to pin an existing public IPFS CID.
INPUTS: cid / name / groupId / keyvalues / hostNodes
create_groupWRITECreate a Pinata file group on the public or private IPFS network.
INPUTS: network / name / isPublic
get_groupREADGet one Pinata group by ID from the public or private IPFS network.
INPUTS: network / id
list_filesREADList Pinata files from the public or private IPFS network with optional filters.
INPUTS: network / name / group / mimeType / cid
list_groupsREADList Pinata file groups from the public or private IPFS network.
INPUTS: network / name / isPublic / limit / pageToken
query_pin_requestsREADQuery Pinata pin-by-CID requests with optional filters and pagination.
INPUTS: order / status / cid / limit / pageToken
remove_file_from_groupHIGH IMPACTRemove a Pinata file from a Pinata group.
INPUTS: network / groupId / fileId
update_fileWRITEUpdate a Pinata file name or key-value metadata.
INPUTS: network / id / name / keyvalues
update_groupWRITEUpdate a Pinata group name or public visibility setting.
INPUTS: network / id / name / isPublic
INPUT CONTRACTS
Know what the action needs before it runs.
get_file
networkOPTIONAL- The Pinata IPFS network to target.
idOPTIONAL- The Pinata file or group identifier.
add_file_to_group
networkOPTIONAL- The Pinata IPFS network to target.
groupIdOPTIONAL- The Pinata file or group identifier.
fileIdOPTIONAL- The Pinata file or group identifier.
delete_file
networkOPTIONAL- The Pinata IPFS network to target.
idOPTIONAL- The Pinata file or group identifier.
pin_by_cid
cidREQUIRED- The IPFS CID.
nameOPTIONAL- Optional custom name for the pinned CID.
groupIdOPTIONAL- Optional Pinata group ID to assign to the pinned CID.
keyvaluesOPTIONAL- Pinata key-value metadata. Values are sent as strings.
hostNodesOPTIONAL- Optional IPFS host node IDs.
PROVIDER-SPECIFIC WORKFLOWS
Jobs this Agent App can support
Inspect Get File
Get one Pinata file by ID from the public or private IPFS network. Use this as a bounded discovery step, retain the returned identifier, and avoid expanding the read beyond the task's stated scope.
get_fileControl Add File To Group
Add a Pinata file to a Pinata group. Resolve the target first, present material changes for confirmation, and make retries idempotent where the provider supports it.
add_file_to_groupVerify with Get Group
Get one Pinata group by ID from the public or private IPFS network. Compare the returned provider state with the intended outcome and preserve stable IDs or canonical links in the run record.
get_groupSAFETY BOUNDARY
Operate Pinata with explicit limits
- Authorize Pinata with API key and grant only the provider access required by the selected actions.
- 6 actions are change-capable by name. Confirm the target identity and material parameters before allowing a write.
- Treat `delete_file` and `remove_file_from_group` as high-impact operations and require an explicit approval boundary.
- The sampled contract declares provider scopes including `org:groups:write`, `org:files:write`, `org:files:read`, and `org:groups:read`; verify the complete action contract before execution.
- After a call, inspect the structured result and execution record before reporting that the Pinata task completed successfully.
CONNECTION MODEL
API key
Pinata JWT used with the Authorization Bearer header. Create or manage API keys from the official API keys page: https://app.pinata.cloud/developers/api-keys.
Working Machines stores provider credentials behind the execution boundary. An agent can use an authorized connection identity, but catalog discovery alone does not reveal OAuth tokens, API keys, or provider secrets.
- READ SIGNALS
- 5
- WRITE SIGNALS
- 4
- HIGH IMPACT
- 2
- REVIEW SIGNALS
- 1
EVIDENCE AND AVAILABILITY
Provider reference
Action names, input fields, authentication types, and counts on this page are generated from the Working Machines provider catalog. Provider behavior, quotas, object semantics, account eligibility, and regional availability remain governed by Pinata.