# marketplace [Health: Active]

**Category:** 💻 Developer Tools  
**Repository:** https://jojapi.com  
**npm Downloads (last month):** 130  
**Views:** 0  
**Installs:** 0  
**Upvotes:** 0  
**Directory Page:** https://allmcps.com/mcp/marketplace-7

## Description
Search the JoJ API marketplace, read endpoint docs, and call any API with one key via one gateway.

## Claude Desktop Quick Installation
Heuristic fallback — verify the package name and runner against the repository README before running it. Uses `npx` (confidence: low):

```json
"mcpServers": {
  "marketplace": {
    "command": "npx",
    "args": ["-y","marketplace-7"]
  }
}
```

## Documentation

## What marketplace does

The marketplace MCP server connects an AI agent to the JoJ API marketplace. It provides a way to search the marketplace, inspect documentation for API endpoints, and call APIs through a gateway. The listing describes one-key access, so the agent can use the gateway without managing a separate key for every API it calls.

This fits workflows where an agent must first discover an API, understand how its endpoints work, and then make a request. It may also be useful when API access needs to be routed through a single gateway instead of being configured independently for each service.

## Tools and capabilities

The available capabilities described for the marketplace MCP server are:

- Search the JoJ API marketplace.
- Read endpoint documentation.
- Call APIs through the JoJ gateway.
- Use one key for gateway access across API calls.

The provided material does not list individual MCP tool names, input parameters, response formats, supported HTTP methods, or a catalog of APIs available through the marketplace. Those details should be checked in the service’s own documentation before building an integration around specific operations.

## Limitations and notes

The available listing information identifies the JoJ API marketplace and its three core actions, but it does not describe installation commands, transport details, authentication variable names, client-specific setup, rate limits, billing, error handling, or API coverage. As a result, configuration cannot be specified reliably from the provided material alone.

The marketplace MCP server should be evaluated against the APIs an agent needs to use. Marketplace search and endpoint documentation can help with discovery, while actual request behavior depends on the selected API and the gateway’s documented requirements. Confirm whether the required API is listed and review its endpoint documentation before depending on it in production.

No repository README was provided for this listing, so there is no grounded basis for naming supported MCP clients, declaring a software license, or documenting a particular startup command. The source URL is the appropriate place to verify those details and obtain current setup instructions.

_Full upstream README: https://allmcps.com/mcp/marketplace-7/readme_