Skip to main content
Glama
Davoooda

Woopicx MCP Server

by Davoooda
OverviewSchemaRelated ServersScoreDiscussions
JavaScript
Remote

Woopicx MCP (Model Context Protocol) Server

Expose Woopicx /v1/search API as a tool for Claude, Cursor, and other LLM clients via MCP.

What is MCP?

MCP is a protocol that lets LLMs call external tools over stdio. When you enable a tool in Claude or Cursor, you can type "search Woopicx for business icons" and the LLM will automatically call our API and return results.

Related MCP server: Freepik MCP

Quick Setup (Cursor / Claude Desktop)

1. Install Node.js (if not already)

node --version  # should be 18+

2. Get your Woopicx API Key

Public test key: wpx_live_2cc034849a7fa88889044181170ee259

Or generate your own at: https://woopicx.com/admin/api-keys

3. Add to Cursor settings.json

Open Cursor → Settings → Features → "Code Editor" → scroll to "MCP Servers" → click "Edit JSON"

Add:

{
  "mcpServers": {
    "woopicx": {
      "command": "node",
      "args": ["/absolute/path/to/woopicx-mcp/index.js"],
      "env": {
        "WOOPICX_API_KEY": "wpx_live_2cc034849a7fa88889044181170ee259"
      }
    }
  }
}

Once published to npm you can instead use "command": "npx", "args": ["-y", "woopicx-mcp"].

4. Restart Cursor

Now you can ask: "Find me some free 3D business icons from Woopicx"

Cursor will automatically call search_woopicx tool with your query.

Claude Desktop (macOS)

  1. Edit ~/.claude/claude.json:

{
  "mcpServers": {
    "woopicx": {
      "command": "node",
      "args": ["/path/to/woopicx-mcp.js"],
      "env": {
        "WOOPICX_API_KEY": "wpx_live_2cc034849a7fa88889044181170ee259"
      }
    }
  }
}

  1. Restart Claude Desktop

API & Tool Details

Tool: search_woopicx

Description: Search free graphics on Woopicx (3D icons, mockups, stock photos, illustrations, certificates, tattoo designs).

Parameters:

  • query (string, required): Search term, e.g. "business icons", "mockups", "tattoo designs"

  • collection (string, optional): Specific collection

    • basic3d - 3D icons (8k+ free)

    • base - stock photos & illustrations

    • mobile-phone-mockup - phone mockups

    • saas-mockups - SaaS/startup mockups

    • certificates - certificate templates

    • tattoo - tattoo designs

  • limit (integer, optional): Results count, 1-50 (default 15)

Response:

{
  "results": [
    {
      "uid": "550bf722-...",
      "title": "Business Person Icon",
      "collection": "basic3d",
      "type": "png",
      "url": "https://woopicx.com/asset/550bf722-...",
      "thumb": "https://cdn.woopicx.com/..."
    }
  ],
  "total": 127,
  "duration_ms": 34
}

How It Works

  1. LLM sees your prompt ("find business icons")

  2. LLM decides to use search_woopicx tool

  3. LLM sends request to MCP server via stdio

  4. Server calls /v1/search API on Woopicx

  5. Server returns results to LLM

  6. LLM formats results for you

Troubleshooting

"Tool not found"

  • Restart your IDE

  • Check the file path is absolute (not relative)

"API Error 401"

  • Check your API key is set correctly

  • Verify key has /v1/search permission

"No results found"

  • Try a simpler query ("icons" instead of "custom business svg logos")

  • Specify a collection to narrow search

Publishing to MCP Hub

Once tested, publish to mcp.so:

  1. Create GitHub repo: woopicx-mcp

  2. Push this server + README

  3. Submit to https://mcp.so/registry

Future Ideas

  • Image similarity search (upload PNG, find similar)

  • Collection browser (list all available collections)

  • Download tool (get asset ZIP with Claude's permission)

  • Batch search (search multiple collections in one call)

Woopicx: 40+ free collections of graphics. No signup to browse.
API Docs: https://api.woopicx.com/docs

Made for Claude, Cursor, and beyond.

Available Tools

1 tool
search_woopicxA

Search free graphics on Woopicx: 3D icons, mockups, stock photos, illustrations, certificates, tattoo designs. Returns asset titles and woopicx.com URLs.

ParametersJSON Schema
NameRequiredDescriptionDefault
limitNoNumber of results, 1-50 (default 15).
queryYesSearch query, e.g. "business icons", "phone mockup", "tattoo designs".
collectionNoOptional collection to narrow the search.

TDQS

A3.8/5.0
Behavior3/5

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

With no annotations provided, the description carries the transparency burden. It does disclose that the tool searches free graphics and returns asset titles and URLs, which is helpful. However, it does not mention authentication requirements, rate limits, pagination behavior, or any side effects, leaving some behavioral aspects unclear.

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

Conciseness5/5

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

The description is two sentences long, directly states the purpose and return value, and includes a compact list of asset categories. Every element earns its place without redundancy or unnecessary detail.

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

Completeness4/5

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

For a simple search tool with a fully described input schema and no output schema, the description is largely complete: it identifies what is searched, the categories, and the return format. Minor gaps remain around result ordering, pagination limits beyond the limit parameter, and error behavior, but these are not critical for basic usage.

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

Parameters3/5

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

The input schema provides complete descriptions for all three parameters (query, limit, collection), including defaults and enum values for collection. The description adds only example search categories via the prose listing, but does not meaningfully extend the parameter semantics beyond what the schema already offers.

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

Purpose5/5

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

The description clearly states the tool's function with a specific verb ('Search') and resource ('free graphics on Woopicx'), and lists concrete categories (3D icons, mockups, stock photos, etc.). It also notes what is returned (asset titles and woopicx.com URLs), making the purpose unambiguous.

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

Usage Guidelines3/5

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

The description implies usage for searching free graphics on Woopicx and provides category examples, but there is no explicit guidance on when to choose this tool over alternatives or any exclusions. Since no sibling tools are listed, the guidance is only implicit.

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

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. 1 tool updatev1.0.0
    • First observedsearch_woopicx
Install Server
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

TDQS

A3.9/5.0
Disambiguation5/5

With only one tool, there is no possibility of confusing it with others. The tool's purpose is clearly defined for searching Woopicx assets.

Naming Consistency5/5

The tool name 'search_woopicx' follows a consistent verb_noun pattern, which is clear and standard even as a lone tool.

Tool Count3/5

A single tool feels thin for an MCP server, especially with a broad server name, but it is adequate for a focused search use case. The count is borderline rather than extreme.

Completeness4/5

The search tool returns asset titles and URLs, covering the search workflow end-to-end. Minor omissions like dedicated asset detail retrieval or category browsing exist but are not essential.

Maintenance

ActivitySlowing
ResponsivenessNo issues

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/Davoooda/woopicx-mcp'

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