`clearlydefined_search`

Pack: clearlydefined · Endpoint: https://gateway.pipeworx.io/clearlydefined/mcp

No MCP client? Call it directly: GET https://gateway.pipeworx.io/v1/tools/clearlydefined_search for the schema, then POST the same URL with its arguments for the data.

Find ClearlyDefined component coordinates by name pattern across npm, Maven, PyPI, RubyGems, NuGet, crates.io, Packagist, Go and GitHub. Returns coordinate strings like “npm/npmjs/-/express/4.18.2” that clearlydefined_definition takes. Use it when you know a package name but not its exact ecosystem/namespace/version. Keyless.

Parameters

Name	Type	Required	Description
`pattern`	string	yes	Name fragment to match, e.g. “express”, “lodash”, “requests”. Broad or very common fragments can time out upstream — be specific.
`limit`	number	no	Maximum coordinates to return. Default 25, max 200.
`type`	string	no	Optional: keep only coordinates of this component type, e.g. “npm”, “maven”, “pypi”, “git”. Filtered client-side.

Example call

Arguments

{
  "pattern": "express",
  "limit": 5
}

curl

curl -X POST https://gateway.pipeworx.io/clearlydefined/mcp \
  -H 'Content-Type: application/json' \
  -d '{"jsonrpc":"2.0","id":1,"method":"tools/call","params":{"name":"clearlydefined_search","arguments":{"pattern":"express","limit":5}}}'

TypeScript (@pipeworx/sdk)

import { Pipeworx } from '@pipeworx/sdk';
const pipeworx = new Pipeworx();

const result = await pipeworx.call('clearlydefined_search', {
  "pattern": "express",
  "limit": 5
});

Connect

Add this to your MCP client config, or use one-click install buttons:

{
  "mcpServers": {
    "clearlydefined": {
      "url": "https://gateway.pipeworx.io/clearlydefined/mcp"
    }
  }
}

See Getting Started for client-specific install steps.

Regenerated from source · build September 18, 2026

Was this helpful?