blob-storage
A lightweight MCP data broker that stores large binary payloads under a UUID, enabling MCP clients and agents to exchange massive results without flooding the LLM context window.
README
Blob Storage Service
A lightweight MCP data broker that stores large binary payloads under a UUID, enabling MCP clients and agents to exchange massive results without flooding the LLM context window.
Architecture
MCP Client / LLM Agent
│
│ tool call (large result)
▼
MCP Server ──store_blob──▶ Blob Storage Service ──▶ SQLite + local files
│ │
│ returns UUID │ retrieve_blob(uuid)
◀──────────────────────────────┘
The agent only ever sees a UUID token — not the raw bytes.
Project Structure
src/blob_storage/
├── __init__.py # package metadata
├── config.py # pydantic-settings (env / .env)
├── models.py # SQLAlchemy ORM + Pydantic schemas
├── database.py # async engine, session factory, init_db()
├── storage.py # StorageBackend ABC + LocalFileBackend
├── service.py # BlobService (orchestration)
├── api.py # FastAPI REST API
└── mcp_server.py # MCP server (HTTP Streamable, /mcp)
tests/
├── conftest.py # shared fixtures
├── test_api.py # API integration tests
└── test_service.py # service unit tests
Quickstart
Install dependencies
uv sync
Start the REST API
uv run blob-api # defaults from config / .env
uv run blob-api --host 0.0.0.0 --port 9000 # override at runtime
Interactive docs available at http://<host>:<port>/docs.
Start the MCP server
uv run blob-mcp # defaults: 0.0.0.0:8001
uv run blob-mcp --host 0.0.0.0 --port 9001
The MCP endpoint is served at http://<host>:<port>/mcp.
Configuration
Settings are read from environment variables or a .env file in the project root.
| Variable | Default | Description |
|---|---|---|
STORAGE_DIR |
./data/blobs |
Directory for blob files |
DATABASE_URL |
sqlite+aiosqlite:///./data/metadata.db |
SQLAlchemy async DB URL |
DEFAULT_TTL_SECONDS |
7776000 |
Default TTL — 90 days. Use 0 for no expiry. |
MAX_BLOB_SIZE_BYTES |
524288000 |
Max upload size (500 MB) |
API_HOST |
0.0.0.0 |
REST API bind address |
API_PORT |
8000 |
REST API port |
MCP_HOST |
0.0.0.0 |
MCP server bind address |
MCP_PORT |
8001 |
MCP server port |
MCP_API_BASE_URL |
http://127.0.0.1:8000 |
REST API URL used internally by the MCP server |
SWEEP_INTERVAL_SECONDS |
3600 |
How often the TTL cleanup job runs |
CLI flags (
--host,--port) take precedence over config/env for the respective server.
REST API Reference
| Method | Path | Description |
|---|---|---|
GET |
/health |
Liveness check |
POST |
/blobs |
Store a blob |
GET |
/blobs/{uuid} |
Download a blob |
GET |
/blobs/{uuid}/meta |
Metadata only (no payload) |
DELETE |
/blobs/{uuid} |
Delete a blob |
Store a blob
Pass metadata as custom request headers:
| Header | Default | Description |
|---|---|---|
X-Mime-Type |
application/octet-stream |
MIME type of the payload |
X-Ttl-Seconds |
config default | Override TTL; 0 = never expires |
X-Origin |
— | Free-form source identifier |
X-Tags |
— | JSON object for arbitrary labels |
curl -X POST http://localhost:8000/blobs \
-H "Content-Type: application/octet-stream" \
-H "X-Mime-Type: application/json" \
-H "X-Origin: my-mcp-server" \
--data-binary '{"key": "value"}'
Response:
{
"uuid": "3fa85f64-5717-4562-b3fc-2c963f66afa6",
"expires_at": "2026-05-30T16:42:07Z",
"size_bytes": 16
}
MCP Integration
The MCP server uses the Streamable HTTP transport. Configure your MCP host to connect over HTTP rather than spawning a subprocess:
{
"mcpServers": {
"blob-storage": {
"type": "http",
"url": "http://127.0.0.1:8001/mcp"
}
}
}
Available tools
| Tool | Input | Output |
|---|---|---|
store_blob |
data_b64, mime_type, ttl_seconds?, origin?, tags? |
{ uuid, expires_at, size_bytes } |
retrieve_blob |
uuid |
{ uuid, mime_type, data_b64 } |
get_blob_meta |
uuid |
metadata JSON |
delete_blob |
uuid |
{ deleted: uuid } |
All binary data is base64-encoded in MCP tool calls (MCP messages are JSON/text).
Running Tests
uv run pytest tests/ -v
Extending the Storage Backend
To use S3 or MinIO in production, implement the StorageBackend abstract class in storage.py:
from blob_storage.storage import StorageBackend
class S3Backend(StorageBackend):
async def store(self, blob_uuid: str, data: bytes) -> None: ...
async def retrieve(self, blob_uuid: str) -> bytes: ...
async def delete(self, blob_uuid: str) -> None: ...
Then inject it into BlobService and the _backend singleton in api.py.
推荐服务器
Baidu Map
百度地图核心API现已全面兼容MCP协议,是国内首家兼容MCP协议的地图服务商。
Playwright MCP Server
一个模型上下文协议服务器,它使大型语言模型能够通过结构化的可访问性快照与网页进行交互,而无需视觉模型或屏幕截图。
Magic Component Platform (MCP)
一个由人工智能驱动的工具,可以从自然语言描述生成现代化的用户界面组件,并与流行的集成开发环境(IDE)集成,从而简化用户界面开发流程。
Audiense Insights MCP Server
通过模型上下文协议启用与 Audiense Insights 账户的交互,从而促进营销洞察和受众数据的提取和分析,包括人口统计信息、行为和影响者互动。
VeyraX
一个单一的 MCP 工具,连接你所有喜爱的工具:Gmail、日历以及其他 40 多个工具。
graphlit-mcp-server
模型上下文协议 (MCP) 服务器实现了 MCP 客户端与 Graphlit 服务之间的集成。 除了网络爬取之外,还可以将任何内容(从 Slack 到 Gmail 再到播客订阅源)导入到 Graphlit 项目中,然后从 MCP 客户端检索相关内容。
Kagi MCP Server
一个 MCP 服务器,集成了 Kagi 搜索功能和 Claude AI,使 Claude 能够在回答需要最新信息的问题时执行实时网络搜索。
e2b-mcp-server
使用 MCP 通过 e2b 运行代码。
Neon MCP Server
用于与 Neon 管理 API 和数据库交互的 MCP 服务器
Exa MCP Server
模型上下文协议(MCP)服务器允许像 Claude 这样的 AI 助手使用 Exa AI 搜索 API 进行网络搜索。这种设置允许 AI 模型以安全和受控的方式获取实时的网络信息。