mcp-tenor-api

@hzrd149

About mcp-tenor-api

An mcp server for using the tenor api

Config

Add this server to your MCP-compatible client using the configuration below.

{
  "mcpServers": {
    "mcp-tenor-api": {
      "command": "docker",
      "args": [
        "run",
        "-i",
        "-it",
        "-e",
        "API_KEY=your-tenor-api-key",
        "ghcr.io/hzrd149/mcp-tenor-api"
      ]
    }
  }
}

Tools

No tools detected

We auto-extract tools from the README. The maintainer can list them under a ## Tools heading to populate this section.

Overview

What is mcp-tenor-api?

mcp-tenor-api is a Model Context Protocol server that provides access to the Tenor GIF API. It is intended for use with MCP-compatible clients.

How to use mcp-tenor-api?

Run the server from the Deno registry, a local clone, or Docker. Set the API_KEY environment variable to your Tenor API key.

Key features of mcp-tenor-api

Integrates the Tenor GIF API via MCP
Runs on Deno
Supports execution with Docker

Use cases of mcp-tenor-api

—

FAQ from mcp-tenor-api

How is mcp-tenor-api installed and run?

It can be run directly from the Deno registry, from a local clone, or via Docker. In all cases the API_KEY environment variable must be set.

What dependencies does mcp-tenor-api require?

It requires the Deno runtime and a valid Tenor API key.

What authentication does mcp-tenor-api use?

Authentication is handled through the API_KEY environment variable, which must contain a Tenor API key.

—

Frequently asked questions

How is mcp-tenor-api installed and run?

It can be run directly from the Deno registry, from a local clone, or via Docker. In all cases the `API_KEY` environment variable must be set.

What dependencies does mcp-tenor-api require?

It requires the Deno runtime and a valid Tenor API key.

What authentication does mcp-tenor-api use?

Authentication is handled through the `API_KEY` environment variable, which must contain a Tenor API key. —

Comments

Basic information

More Developer Tools MCP servers

Mobbin

Mobbin MCP connects your AI agents to 600,000+ real product screens, so what they build starts with what already works.

Routebase

Routebase keeps your API's design, docs, contract tests, mocks and monitoring in one living OpenAPI spec so they can't drift apart. Agents work on that same source of truth, under your team's permissions.

Moxie Docs

Jackalope-Dev

Automated codebase documentation for GitHub: searchable docs, MCP context for AI agents, doc drift detection, and Friday Cleanup PRs.

directree

coburn2716

directree MCP server — query the honest software directory from any AI assistant

TaskerArmy Agent

TaskerArmy

Ask Claude or ChatGPT what Shopify theme optimization tasks are pending on your store, a remote MCP server for TaskerArmy Agent accounts.