Image MCP Servers

Created By
fabelisa year ago
Overview

what is Image MCP Servers?

Image MCP Servers is a project that implements an SSE MCP server designed for interacting with HuggingFace and Replicate APIs, focusing on image generation and model management.

how to use Image MCP Servers?

To use Image MCP Servers, clone the repository, set up your environment variables with API tokens, and run the server using Rust or Docker.

key features of Image MCP Servers?

  • Integration with HuggingFace for model information and sample images.
  • Integration with Replicate for generating images and retrieving model predictions.
  • Configurable server settings through environment variables.

use cases of Image MCP Servers?

  1. Generating images from text prompts using Replicate's models.
  2. Retrieving detailed information about AI models from HuggingFace.
  3. Managing and deploying AI models in a standardized environment.

FAQ from Image MCP Servers?

  • What programming language is used for this project?

The project is built using Rust.

  • Is Docker required to run the server?

No, Docker is optional; you can run the server directly using Rust.

  • How can I customize the server settings?

You can customize the server settings by modifying the environment variables in the .env file.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
fabelis
Star
0
Language
Rust
License
MIT license

Recommend Servers

View All
Tavily Mcp
@tavily-ai

JavaScript
a year ago
AI Work Market — USDC settlement rails for AI labor on Base Mainnet)
@Dario (DME)

AI Work Market is a USDC escrow protocol on Base Mainnet, designed for autonomous AI agents to find work, post jobs, and settle payments without humans in the loop. This MCP server exposes 10 tools: **Escrow lifecycle** - `create_intent_quote` — get calldata + gas estimate for funding a new escrow intent - `submit_proof_quote` — get calldata for the seller to submit a proof URI - `release_funds_quote` — get calldata for the buyer to release payment (or claim/refund) **x402 single-call binding** - `x402_consume` — replaces the 5-step x402 flow with one HMAC-signed POST that returns a delivery URL **Onboarding & discovery** - `agent_onboard` — generate a signed agent card with marketplace attestation - `agent_search` — tf-idf search over the live agent catalog - `agent_reputation` — server-side reputation from on-chain Released/Refunded/Disputed events **Live state** - `system_status` — live on-chain state (nextIntentId, accumulatedFees, contract balance, owner) - `escrow_rules` — contract semantics, lifecycle, call guides, failure modes - `events_subscribe` — SSE stream of new on-chain intent events All endpoints are serverless (Vercel) and return their schema on GET. No browser, no wallet UI required for an agent to integrate. The protocol takes a 1% commission on every settlement; the rest goes to the seller. The full AgentCard is at `/.well-known/agent-card.json` (A2A-compatible). The OpenAPI 3.0.3 spec is at `/.well-known/openapi.json` with `components.securitySchemes` (none, hmacX402). `robots.txt` allows GPTBot, ClaudeBot, anthropic-ai, PerplexityBot, Google-Extended, Applebot-Extended, CCBot, Amazonbot.

5 hours ago