Blockfrost IPFS
for AI agents.
Blockfrost IPFS integration for AI agents with secure authentication and server-side credential injection. Open Connector runs the OAuth, seals the token in an encrypted vault, and serves Blockfrost IPFS tools to your agent over MCP or a typed API — credentials injected server-side, every call audited, nothing leaving your infrastructure. Open source (AGPL-3.0) and self-hostable.
Real Blockfrost IPFS actions, managed and audited.
Your user connects Blockfrost IPFS once; your agent can then upload, retrieve, list, pin, and unpin objects through Blockfrost IPFS — scoped to the OAuth permissions you grant and the tool allowlist you configure. Every action is least-privilege and written to a tamper-evident audit trail.
- 01Connect
Your user grants Blockfrost IPFS access once (OAuth) — the token lands in the vault.
- 02Call
Your agent calls a tool over MCP or the typed API; Open Connector injects the credential server-side.
- 03Audit
Every routed call appends a hash-chained audit record — nothing leaves your infra.
Supported Blockfrost IPFS tools.
Browse 5 tools in the Blockfrost IPFS catalog. Each action uses your configured authentication and tool allowlist.
Showing 5 tools.
- Relay to an IPFS gateway
- Retrieve an object from the IPFS gateway (useful if you do not want to rely on a public gateway, such as `ipfs.blockfrost.dev`). <p> <span class="hosted">Hosted</span> Endpoint only available for hosted variant. </p>
- IPFS » Gateway
- List pinned objects
- List objects pinned to local storage <p> <span class="hosted">Hosted</span> Endpoint only available for hosted variant. </p>
- IPFS » Pins
- Get details about pinned object
- Get information about locally pinned IPFS object <p> <span class="hosted">Hosted</span> Endpoint only available for hosted variant. </p>
- IPFS » Pins
- Pin an object
- Pinning is necessary to avoid regular garbage collection (deletion) of IPFS objects. Non-pinned objects are regularly being removed without prior notice. Pinned objects are counted in your user storage quota. **Note:** If the object was pinned to Filecoin (using `filecoin=true`), it cannot be removed or unpinned due to Filecoin's immutable and persistent storage guarantees. Please ensure careful consideration when pinning objects to Filecoin, as the action is irreversible.
- IPFS » Pins
- Remove a IPFS pin
- Remove pinned objects from local storage <p> <span class="hosted">Hosted</span> Endpoint only available for hosted variant. </p> **Note:** If the object was pinned to Filecoin (using `filecoin=true`), it cannot be removed or unpinned due to Filecoin's immutable and persistent storage guarantees. Please ensure careful consideration when pinning objects to Filecoin, as the action is irreversible.
- IPFS » Pins
Blockfrost IPFS integration, answered
- How do AI agents use Blockfrost IPFS through Open Connector?
- Your user connects Blockfrost IPFS once with one of its cataloged authentication methods. Open Connector stores the credential in an encrypted vault and exposes Blockfrost IPFS tools to your agent over MCP or a typed API, with credentials injected server-side on each call.
- Is this a Blockfrost IPFS MCP server?
- Yes. Open Connector can serve Blockfrost IPFS as a named MCP server with a scoped allowlist and a per-user connection URL, so any MCP client can call Blockfrost IPFS actions with credentials injected server-side.
- Where do Blockfrost IPFS credentials live?
- In your own infrastructure. Open Connector keeps credentials in its own vault and injects them at call time, so they never leave your environment.
Give your agents Blockfrost IPFS — keep the keys.
Open source, self-hostable, with Blockfrost IPFS credentials that never leave your infrastructure. Run it from source today.