flin-imgbb-mcp
MCP server for uploading images to ImgBB from Claude-compatible clients.
Quick Start
The recommended setup uses uvx — no repository clone or virtual environment required.
Add this to your Claude MCP configuration:
{
"mcpServers": {
"imgbb": {
"command": "uvx",
"args": ["flin-imgbb-mcp@latest"],
"env": {
"IMGBB_API_KEY": "your-imgbb-api-key"
}
}
}
}
Get your API key at api.imgbb.com.
Tools
upload_image
Upload a single image file to ImgBB and get its public URL.
| Parameter | Type | Required | Description |
|---|---|---|---|
file_path |
string | yes | Absolute or relative path to the image file |
name |
string | no | Optional name for the image on ImgBB |
expiration |
number | no | Expiration in seconds (60–15552000) |
Returns: url, display_url, delete_url, title
list_images
List all image files in a local folder (png, jpg, jpeg, gif, webp, bmp).
| Parameter | Type | Required | Description |
|---|---|---|---|
folder_path |
string | yes | Absolute path to the folder |
upload_all_images
Upload all images from a local folder to ImgBB.
| Parameter | Type | Required | Description |
|---|---|---|---|
folder_path |
string | yes | Absolute path to the folder |
expiration |
number | no | Expiration in seconds (60–15552000) for all images |
Configuration
| Environment Variable | Required | Description |
|---|---|---|
IMGBB_API_KEY |
yes | Your ImgBB API key |
Troubleshooting
Server does not start / "IMGBB_API_KEY is not set"
Make sure IMGBB_API_KEY is set in the env block of your MCP configuration. The server checks for it at startup and will exit with a clear error if it is missing.
Upload fails with HTTP 400 The file path must point to a valid image file. Supported formats: png, jpg, jpeg, gif, webp, bmp.
uvx command not found
Install uv from docs.astral.sh/uv.
Development
# Install uv
curl -LsSf https://astral.sh/uv/install.sh | sh
# Install dependencies
uv sync --group dev
# Run tests
uv run pytest tests/ -v
# Lint
uv run ruff check src/ tests/
# Build distribution artifacts
uv build
Release
Releases are published to PyPI automatically when a version tag is pushed:
git tag v1.0.2
git push origin v1.0.2
The GitHub Actions release workflow builds the package and publishes it via PyPI Trusted Publishing.
License
MIT
Metadata
Release files for flin-imgbb-mcp 1.0.2
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | |
|---|---|---|---|
| flin_imgbb_mcp-1.0.2.tar.gz | 8.8 kB | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| flin_imgbb_mcp-1.0.2-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 14.2 kB
Release files / flin_imgbb_mcp-1.0.2.tar.gz
| Download URL | flin_imgbb_mcp-1.0.2.tar.gz |
|---|---|
| Size | 8.8 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
2a37e0db49889a48c6c336ab1a9f660d282397c60eff43d669534f84ad9e5d3a
|
|
BLAKE2b-256 checksum How to use checksums |
e69a4fa0a3304fdf087f5da5b2065d5fc082ae59d9675a683f893d2e7db3cfe2
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.7
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Mar 28, 2026.
Transparency logRelease files / flin_imgbb_mcp-1.0.2-py3-none-any.whl
| Download URL | flin_imgbb_mcp-1.0.2-py3-none-any.whl |
|---|---|
| Size | 5.3 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
ee7e9e1ccc66b3f985d9210e636f427adee2e4d1ea3a5f2d3f90ccc51078c079
|
|
BLAKE2b-256 checksum How to use checksums |
6052d09fa4209db1b2b585f04630863e025c05e4ebfb4f7750b8680abf9a75d5
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.7
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Mar 28, 2026.
Transparency log