42matters MCP
by pipeworx-io
README.md
# mcp-42matters
42matters MCP — wraps the 42matters App Market Data API (42matters.com)
Part of [Pipeworx](https://pipeworx.io) — an MCP gateway connecting AI agents to 1558+ live data sources.
## Tools
| Tool | Description |
|------|-------------|
| `fortytwo_app_lookup` | Look up full details for a single mobile app — title, developer, ratings, downloads/installs, category, price, and more. For Android pass the package name via `app_id` (e.g. "com.facebook.katana"); for iOS pass the numeric App Store id (e.g. "284882215"). Example: fortytwo_app_lookup({ platform: "android", app_id: "com.facebook.katana", _apiKey: "your-token" }) |
| `fortytwo_app_search` | Search the app store by keyword and return matching apps with pagination. Example: fortytwo_app_search({ platform: "ios", query: "racing games", limit: 20, page: 1, _apiKey: "your-token" }) |
| `fortytwo_top_charts` | Get a ranked top-chart list (top free, top paid, top grossing, etc.) for a country and category. Android uses `cat_key` (e.g. "OVERALL"); iOS uses `genre_id` (e.g. "36" for the overall/all-apps genre) plus optional `device_type`. Example: fortytwo_top_charts({ platform: "android", list_name: "topselling_free", cat_key: "OVERALL", country: "US", limit: 10, _apiKey: "your-token" }) |
| `fortytwo_apps_by_sdk` | Find apps that integrate a given SDK. Pass one or more SDK ids via `sdk` (e.g. "google-ads-admob"). Useful for competitive/market-share analysis of ad networks, analytics, and other SDKs. Example: fortytwo_apps_by_sdk({ platform: "android", sdk: "google-ads-admob", limit: 20, _apiKey: "your-token" }) |
## Quick Start
Add to your MCP client (Claude Desktop, Cursor, Windsurf, etc.):
```json
{
"mcpServers": {
"42matters": {
"url": "https://gateway.pipeworx.io/42matters/mcp"
}
}
}
```
### What this endpoint actually serves
`tools/list` at `https://gateway.pipeworx.io/42matters/mcp` returns the tools in the table
above **plus the shared Pipeworx meta-tools** — `ask_pipeworx`,
`discover_tools`, `search_within`, `remember`/`recall` and the rest of the
gateway-wide set. So the tool count you see is larger than this table: a
single-pack endpoint currently lists roughly 30 shared tools alongside the
pack's own. The connection's `initialize` response states its exact scope, and
is the authoritative answer for a given day.
This is deliberate, not multiplexing by accident. The meta-tools are what let a
scoped connection answer a question this pack does not cover — via
`ask_pipeworx`, which routes across the whole catalog — without you adding a
second MCP server. There is currently no way to mount a pack endpoint without
them; if the extra schemas cost you more context than the routing is worth,
connect to the full gateway once rather than to several pack endpoints.
Or connect to the full Pipeworx gateway to get every pack's tools listed
directly, instead of just this one's:
```json
{
"mcpServers": {
"pipeworx": {
"url": "https://gateway.pipeworx.io/mcp"
}
}
}
```
Both URLs reach the same gateway and the same 1558+ data sources. The
only difference is which pack's tools are listed **directly**; `ask_pipeworx`
reaches all of them from either one.
## Standalone (no gateway account)
This package also runs as a local stdio MCP server — no Pipeworx account, no
gateway round-trip:
```json
{
"mcpServers": {
"42matters": {
"command": "npx",
"args": ["-y", "@pipeworx/mcp-42matters"]
}
}
}
```
Or run it directly to confirm it starts:
```bash
npx -y @pipeworx/mcp-42matters
```
It speaks MCP over stdin/stdout and answers `initialize`/`tools/list`/`tools/call`
for **only** this pack's tools — none of the shared meta-tools the gateway
connection above adds. Same source, same tools, no ask_pipeworx routing.
## Using with ask_pipeworx
Instead of calling tools directly, you can ask questions in plain English —
this works on the pack endpoint above as well as on the full gateway:
```
ask_pipeworx({ question: "your question about 42matters data" })
```
The gateway picks the right tool and fills the arguments automatically.
## More
- [Docs and guides](https://pipeworx.io/docs)
- [pipeworx.io](https://pipeworx.io)
## License
MIT
This server cannot be deployed
Maintenance
ActivityMaintained
ResponsivenessNo issues