Enables AI assistants to import Canva share links as editable templates, read and update template layers (text, images, positions, styling), and render PNG, JPEG, WebP, or PDF variants from data — singly or in bulk up to 25 at a time. Connects via a remote OAuth endpoint, API key, or local stdio.

Standalone MCP server for SAP ABAP ADT over stdio: one destination through the auth broker (service keys, sessions, the browser login); connects to the system over HTTP, RFC or SNC (passwordless). RFC and SNC need the SAP NW RFC library at run time. Strea

md-log MCP: save/update/fetch markdown by path (stdio + remote HTTP, PAT auth).

Headless MCP server for Metabase: API-key auth (no OAuth), stdio or HTTP, 178 tools with toolsets, works on every Metabase tier

Enables Claude and ChatGPT to manage Motion tasks through one shared API core, including capturing next actions, preserving resume context, checking duplicates, and reporting scheduling health. It serves local stdio clients and OAuth-protected Streamable HTTP clients.

Enables agents to probe URLs and classify bot-wall responses with vendor and signal evidence, perform offline classification, scan for exposed key-like material, and run owner-side access audits through stdio tools.

Exposes explicitly approved local Windows stdio and loopback HTTP MCP backends through a single OAuth-protected remote HTTPS MCP endpoint, letting a mobile AI client invoke whitelisted tools with namespacing, PKCE-based authorization, and per-tool permissions.

Turns any OpenAPI 3.x spec into an MCP server that exposes one validated tool per API operation, so AI agents can discover and call a REST API over stdio or Streamable HTTP. It is read-only by default, with allow/deny lists, environment-based auth, timeouts and response truncation for safe agent access.

MCPCAN is a centralized management platform for MCP services. It deploys each MCP service using a container deployment method. The platform supports container monitoring and MCP service token verification, solving security risks and enabling rapid deployment of MCP services. It uses SSE, STDIO, and STREAMABLEHTTP access protocols to deploy MCP。