About mcp-tenor-api
mcp-tenor-api is an MCP server that connects clients to the Tenor GIF API. It can be run with Deno or Docker and requires a Tenor API key.
Key features
- 01Connects to the Tenor GIF API
- 02Runs from the Deno registry or a local clone
- 03Docker-based launch option
Use cases
- 01Use Tenor GIF API capabilities through an MCP client
- 02Run the server from Deno for development
- 03Launch the server in Docker
MCP support
The MCP server makes the Tenor GIF API available to MCP clients. The README does not specify the individual tools it exposes.
Configuration
Local server config is the same for every client. Copy it into your client’s MCP config file.
docker run -i --rm -e API_KEY ghcr.io/hzrd149/mcp-tenor-apiAPI_KEYSecretLocal servers need a runtime on your machine (e.g. Node.js 18+). Config file locations differ by client; see your client’s docs.
ghcr.io/hzrd149/mcp-tenor-apistdioTools
Local servers expose tools only once running on your machine, and the maintainer has not provided a tool list.
Details
From the project READMEmcp-tenor-api
A Model Context Protocol server for the Tenor GIF API.
Development
Test the MCP server using the MCP inspector:
deno task dev
Usage
Run directly from the Deno registry:
API_KEY=your-tenor-api-key deno run --allow-net --allow-env @hzrd149/mcp-tenor-api
Or run from a local clone:
API_KEY=your-tenor-api-key deno run --allow-net --allow-env mod.ts
Or use Docker:
docker run -i -it -e API_KEY=your-tenor-api-key ghcr.io/hzrd149/mcp-tenor-api
Comments
New to MCP?
From what the protocol is to installing your first server, these answers cover most first questions.
An open protocol that defines how AI applications connect to external tools and data in a uniform way. Clients talk to the model; MCP servers provide tools, resources and prompt templates. They exchange standard messages, so one server can be reused by many clients.