adpanel-core
Related Servers
Alternatives to adpanel-core
No user-submitted related servers found.
Related Servers
- FlicenseNot gradedqualityDmaintenanceLocal MCP server that exposes fixed tools for GPT, Claude, and Gemini while routing to any OpenAI-compatible chat completions backend with independent configuration per target.1-

deAPI MCP Serverofficial
AlicenseBqualityBmaintenanceOfficial MCP server for deAPI. 39 tools for image and video generation, image editing, background removal and upscaling, text-to-speech, music generation, transcription of audio, video files and video links, OCR, video description and embeddings. Requires a deAPI API key.391MIT- AlicenseNot gradedqualityDmaintenanceA production-grade MCP server designed for multi-tenant, authenticated, and observable AI agent systems, enabling secure tool execution across heterogeneous data sources.68MIT

AISIX AI Gatewayofficial
AlicenseAqualityBmaintenanceSelf-hosted MCP gateway that registers upstream MCP servers and fronts them behind one governed Streamable HTTP endpoint: per-tool access control by caller API key, guardrails over tool arguments and results, rate limits, and usage logs. The same Rust gateway also proxies LLM and A2A agent traffic.1227Apache 2.0- AlicenseAqualityFmaintenanceProduction-grade MCP server for image and video understanding and generation across Gemini, OpenAI, and Grok.5114 PyPI4Apache 2.0
- FlicenseNot gradedqualityDmaintenanceA universal MCP server for registering internal, external, and OpenAPI-based APIs as MCP tools. It exposes them to MCP clients via Streamable HTTP and provides admin portal, RBAC/session auth, credential injection, and audit logging.-
TDQS
Scored across 3 tools
Each tool maps to a distinct stage in a linear pipeline: ingest a brand matrix, orchestrate a timeline, and synthesize a broadcast asset. The descriptions explicitly reference the prerequisite artifact for each later stage, so there is little risk of misselection.
All tools use the same adpanel_ prefix followed by a clear verb_noun pattern in snake_case. The convention is predictable and consistent across the entire surface.
Three tools correspond cleanly to the three core pipeline operations, with each tool earning its place. The count is well-scoped for a focused processing service rather than being artificially thin.
The forward processing chain is covered, but there are no read/list/status operations for brand matrices, timelines, assets, or routing references. Agents can execute the pipeline but may struggle to inspect, verify, retry, or manage previously created artifacts.