AbleSign MCP
The AbleSign MCP server provides 44 MCP tools that expose the AbleSign digital signage API, enabling AI agents to manage screens, screen groups, media, web apps, workspaces, and users without manual REST calls.
Screens: List, register (using a six-character pairing code), get, update, delete. Filter by orientation, online status, or tags. Manage per‑screen playlists: get, replace, add 1–50 media/web‑app items (at start or end), and partially update individual items.
Screen Groups: Create, list, get, update, delete. Manage group playlists: get, replace, add items, update items. View and set group members (up to 100 screens).
Media Folders: List, create, get, rename, delete. Support nested hierarchies via parent folder IDs.
Media Files: List (filter by format, orientation, tags, date, folder), get (including signed download URLs), update metadata, delete. Upload and replace files through a three‑step flow: initiate (obtains a signed PUT URL), client uploads the raw bytes, then complete.
Web Apps: List, create (from a URL or raw HTML), get, update (metadata, URL, schedule, zoom level, tags), delete.
Workspaces: List, create, get, update (set color as #RRGGBB), delete (only non‑default, empty workspaces). List workspace users.
All tools accept structured arguments and return JSON; errors include HTTP status, error code, and message.
Click on "Install Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@AbleSign MCPlist all screens in my workspace"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
AbleSign MCP
A Python Model Context Protocol server for the AbleSign digital signage API.
The purpose of this project is simple: let AI agents operate AbleSign digital signage without making them speak REST by hand. It was fully vibe coded. There is no claim that this is sacred architecture or precious artisanal software. The agents do not care; they just have to do their jobs with it.
It exposes all 44 documented API operations as MCP tools:
screens and screen playlists
screen groups, membership, and group playlists
media folders and media files
AbleSign's initiate/finish upload and replacement flows
web apps
workspaces and workspace users
Requirements
Nix, or Python 3.11+ when installing with
uvan AbleSign API key, created in AbleSign CMS → Account → API Keys
Related MCP server: agentforge
Install and run
Install the ablesign-mcp binary from the flake:
nix profile install github:MartinLoeper/ablesign-mcp
ABLESIGN_API_KEY=ak_your_key ablesign-mcpYou can also run it directly without installing it:
ABLESIGN_API_KEY=ak_your_key \
nix run github:MartinLoeper/ablesign-mcpTo install or run the current checkout instead, replace
github:MartinLoeper/ablesign-mcp with ..
Using uv for a source checkout:
cp .env.example .env
# Set ABLESIGN_API_KEY in .env, then export it or use your preferred env loader.
uv sync
ABLESIGN_API_KEY=ak_your_key uv run ablesign-mcpThe default transport is stdio. To run a Streamable HTTP server:
ABLESIGN_API_KEY=ak_your_key \
ablesign-mcp --transport streamable-httpClients then connect to http://127.0.0.1:8000/mcp.
MCP client configuration
For a stdio MCP client, use:
{
"mcpServers": {
"ablesign": {
"command": "ablesign-mcp",
"env": {
"ABLESIGN_API_KEY": "ak_your_key",
"ABLESIGN_WORKSPACE_ID": "123"
}
}
}
}ABLESIGN_WORKSPACE_ID is optional. Without it, AbleSign uses the account's
default workspace.
Environment
Variable | Required | Default | Purpose |
| yes | — | Bearer token used for every API request |
| no | account default | Sent as |
| no |
| API base URL |
| no |
| request timeout in seconds |
| no |
|
|
| no |
| HTTP bind host |
| no |
| HTTP bind port |
Media uploads
AbleSign uses a three-step upload flow:
Call
initiate_media_upload(orinitiate_media_replacement).Upload the raw file bytes with HTTP
PUTto the returned signed URL.Call
complete_media_upload(orcomplete_media_replacement) with the returned upload ID.
The MCP server exposes the authenticated AbleSign steps. Uploading bytes to the temporary signed storage URL is intentionally left to the caller so the server does not receive arbitrary local filesystem access.
Development
nix build
nix run . -- --help
uv sync --extra dev
uv run pytest
uv run ruff check .
uv run ruff format --check .The API is currently marked beta by AbleSign. The server returns AbleSign errors with their HTTP status, error code, and message so callers can react to validation and rate-limit failures.
Philosophy and license
This project is released under the MIT License. Do whatever you would like with it. Use it, fork it, break it, fix it, sell it, or rewrite it 1,000 times. I really do not care. My agents do not care either. They just have to do their job with it and make gastronomy great again. lol
Maintenance
Resources
Unclaimed servers have limited discoverability.
Looking for Admin?
If you are the server author, to access and configure the admin panel.
Related MCP Servers
- Flicense-qualityDmaintenanceAn MCP (Multi-Agent Conversation Protocol) Server that enables interaction with the At-Work API (api.at-work.biz), allowing agents to communicate with this service through various transport modes like stdio, SSE, and HTTP.Last updated
- FlicenseAqualityFmaintenanceMCP server that exposes 300+ AI agents as tools via a single API key. Supports listing agents, invoking any agent with chat-completion style messages, checking agent health, and retrieving platform statistics.Last updated53
- Alicense-qualityDmaintenanceA full-featured MCP server providing seamless access to CustomGPT.ai APIs, enabling agent and conversation management through MCP-compatible clients.Last updated5MIT
- Alicense-qualityDmaintenanceMCP server for interacting with QUADS infrastructure systems via API, enabling resource management and automation through LLM applications.Last updatedMIT
Related MCP Connectors
MCP server for AI agents to plan, verify, and deploy Cloudflare-native apps.
MCP server for AI dialogue using various LLM models via AceDataCloud
MCP server exposing the Backtest360 engine API as tools for AI agents.
Latest Blog Posts
- Who's Calling? MCP Hosts Are an Identity Blind Spot (And the Spec Knows It)By Om-Shree-0709 on .mcpAgent IdentityOAuth 2.1
- Your AI Chatbot Just Exposed Your CEO's Salary to an InternBy Om-Shree-0709 on .Agent IdentityMCP SecurityOAuth Delegation
- Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)By Om-Shree-0709 on .Agentic AiPrompt InjectionWebAssembly
MCP directory API
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/MartinLoeper/ablesign-mcp'
If you have feedback or need assistance with the MCP directory API, please join our Discord server