Skip to main content
Glama
tech-inspire

Inspire MCP Server

by tech-inspire
OverviewSchemaRelated ServersScoreDiscussions
TypeScript
Remote

Inspire MCP Server

A Model Context Protocol server that uses Inspire backend images search capabilities.

Available Tools

  • get-similar-images-by-description - Get similar images by their text description

    • Required arguments:

      • description (string): Image description

      • limit (number): Pagination limit

      • offset (number): Pagination offset

Configuration

  • INSPIRE_API_BASE: base path for the backend gateway. Default: http://localhost:7080

  • IMAGES_BASE_PATH: base path for images. Example: https://<some-bucket>.s3.com/

Variables can be configured using environment variables or command-line arguments, depending on the runtime platform (Docker/Node).

Related MCP server: Pixabay MCP Server

Building

Docker:

docker build -t tech-inspire/mcp .

Node:

npm ci && npm run build

Usage with Claude Desktop

Add this to claude_desktop_config.json

Docker

{
  "mcpServers": {
    "inspire": {
      "command": "docker",
      "args": [
        "run",
        "--rm",
        "-i",
        "-e",
        "INSPIRE_API_BASE=<API_URL>",
        "-e",
        "IMAGES_BASE_PATH=<IMAGE_BASE_PATH>",
        "tech-inspire/mcp"
      ]
    }
  }
}

Node

{
  "mcpServers": {
    "inspire": {
      "command": "node",
      "args": [
        "/path/to/repo/build/index.js",
        "--INSPIRE_API_BASE=<INSPIRE_API_BASE>",
        "--IMAGES_BASE_PATH=<IMAGES_BASE_PATH>"
      ]
    }
  }
}

License

This MCP server is licensed under the GNU General Public License, as described in the LICENSE file.

Available Tools

1 tool
get-similar-images-by-descriptionD
ParametersJSON Schema
NameRequiredDescriptionDefault
descriptionYesimage description
limitNopagination: limit. set at least 5
offsetYespagination: offset

TDQS

D1/5.0
Behavior1/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Tool has no description.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness1/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Tool has no description.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness1/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Tool has no description.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters1/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Tool has no description.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose1/5

Does the description clearly state what the tool does and how it differs from similar tools?

Tool has no description.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines1/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Tool has no description.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Install Server
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

TDQS

D1.8/5.0
Disambiguation5/5

With only one tool, there is no possibility of ambiguity or overlap between tools. The single tool 'get-similar-images-by-description' stands alone with a distinct purpose.

Naming Consistency5/5

Since there is only one tool, naming consistency is inherently perfect. The tool name 'get-similar-images-by-description' follows a clear verb_noun pattern with hyphens, but with no other tools to compare, it cannot be inconsistent.

Tool Count2/5

A single tool is generally too few for a server's purpose, as it limits functionality and suggests an incomplete or narrow scope. For an 'Inspire MCP Server' that might imply image-related tasks, one tool feels insufficient for comprehensive coverage.

Completeness2/5

The server appears to focus on image retrieval, but with only one tool for getting similar images by description, there are significant gaps. Missing operations likely include uploading images, managing image collections, or other retrieval methods, making the surface severely incomplete for the domain.

Maintenance

ActivityInactive
ResponsivenessSyncing

Resources

Unclaimed servers have limited discoverability.

Looking for Admin?

If you are the server author, to access and configure the admin panel.

Related MCP Connectors

Related MCP Servers

Latest Blog Posts

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/tech-inspire/mcp-server'

If you have feedback or need assistance with the MCP directory API, please join our Discord server