JSON Storage MCP API

AI agent memory and state management via Model Context Protocol

Overview

The JSON Storage MCP API provides AI assistants with simple key-value storage for unstructured JSON data. Optimized for AI integrations using the MCP protocol over HTTP transport with JSON-RPC 2.0.

Two Endpoint Types Available:

• General Endpoint: /mcp/v1/storage/json - Manage multiple categories with storage_json_* tools
• Category-Specific: /mcp/v1/storage/json/{category} - Single category with dynamic {category}_json_* tools

MCP Endpoint

https://mcp.ainoflow.io/mcp/v1/storage/json

Transport:

HTTP (SSE)

Configuration

OpenAI Agent Builder

Add MCP server in the UI dialog:

URL:

Label:

Authentication (Access token / API Key):

Claude Desktop

Add to your Claude Desktop configuration:

Cursor IDE

Add to your Cursor MCP configuration:

Available Tools

storage_json_list_categories

List all distinct categories with item counts for navigation

No parameters required

Example Response:

Useful for discovering what categories exist and navigating the data structure

storage_json_create

Create JSON data with auto-generated key (UUID without dashes)

category

required

- Namespace (e.g., "events", "logs")

data

required

- JSON string to store (must be object or array)

expiresAt

optional

- Expiration date (ISO 8601)

expiresMs

optional

- TTL in milliseconds from now

Example Usage:

Returns auto-generated key like: a1b2c3d4e5f6g7h8i9j0k1l2m3n4o5p6

storage_json_upsert

Create or update (replace) JSON data with explicit key

category

required

- Namespace (e.g., "config", "memory")

key

required

- Unique identifier

data

required

- JSON string to store

expiresAt

optional

- Expiration date (ISO 8601)

expiresMs

optional

- TTL in milliseconds from now

Example Usage:

storage_json_patch

Partially update specific fields using JSON Merge Patch (RFC 7386)

category

required

- Namespace

key

required

- Unique identifier

patch

required

- JSON patch object to merge

Behavior:

• Null values remove fields
• Objects are recursively merged
• Arrays and primitives replace existing values
• Item must exist (404 if not found)

Example:

storage_json_get

Retrieve JSON data

category

required

- Namespace

key

required

- Document key

Example:

Returns JSON document content or error if not found

storage_json_delete

Delete JSON data

category

required

- Namespace

key

required

- Document key

storage_json_list_keys

List keys in category with pagination

category

required

- Namespace

page

optional

- Page number (default: 1)

limit

optional

- Items per page (default: 50, max: 1000)

Returns:

Array of key objects with category, key, size, createdAt, updatedAt, expiresAt, and pagination metadata

storage_json_get_metadata

Get metadata without retrieving data

category

required

- Namespace

key

required

- Document key

Returns:

category, key, createdAt, updatedAt, expiresAt, version, etag, size, createdBy, updatedBy

Available Resources

storage://json/{category}/{key}

Access stored JSON data as a resource

MIME Type: application/json

storage://json/{category}/{key}/meta

Access metadata for stored JSON item

MIME Type: application/json

Category-Specific Endpoint

Optional: Single Category Mode

For focused use cases where you work with a single category

Category-Specific Endpoint

https://mcp.ainoflow.io/mcp/v1/storage/json/{category}

Benefits:

• Simpler tool interface (no category parameter)
• Dynamic tool names: {category}_json_* instead of storage_json_*
• Better isolation (separate MCP servers for different purposes)
• Reduced token usage (shorter requests and responses)
• No tool name conflicts between multiple MCP servers

General Endpoint:

Category-Specific:

Use Cases for AI Assistants

Configuration Management

Store AI agent settings and preferences

Data Caching with TTL

Cache API responses with automatic expiration

Auto-Generated Keys

Log events without managing unique keys

Partial Updates

Update single field without fetching full document

Agent Memory

Persistent memory for conversation context

Browse Categories

Discover what data is stored

Limits

Constraints for JSON storage operations

Maximum document size10MB

Key length200 characters

Category length100 characters

JSON structureObject or array (no primitives)

Total documentsPlan-based limit

REST API Compatibility

Both MCP and REST APIs can be used simultaneously

REST API	MCP Tool
`POST /{category}`	`storage_json_create`
`PUT /{category}/{key}`	`storage_json_upsert`
`PATCH /{category}/{key}`	`storage_json_patch`
`GET /{category}/{key}`	`storage_json_get`
`DELETE /{category}/{key}`	`storage_json_delete`
`GET /{category}`	`storage_json_list_keys`
`GET /{category}/{key}/meta`	`storage_json_get_metadata`

View full REST API Documentation →

Ready to integrate Storage MCP?

Get Started Free Back to MCP Hub