API-MARKET

API Market MCP Servers

typescript

3

GitHub Stars

typescript

Language

6 months ago

First Indexed

2 months ago

Catalog Refreshed

Documentation & install

Readme and setup notes from the catalogue, plus a client-ready config you can copy for your MCP host.

Installation

Add the following to your MCP client configuration file.

Configuration

View docs

{
  "mcpServers": {
    "noveum-api-market-mcp-server": {
      "command": "npx",
      "args": [
        "-y",
        "@noveum-ai/mcp-server"
      ],
      "env": {
        "API_HEADERS": "x-magicapi-key:your-api-key"
      }
    }
  }
}

You can discover and interact with APIs defined by API.market through an MCP server. This server lets large language models locate, query, and execute API endpoints via the MCP protocol, enabling seamless integration with over 200 APIs across many use cases.

How to use

You connect your MCP client to the API-Market MCP Server using a lightweight configuration. Once connected, you can discover available APIs, route requests, and receive structured responses that map to OpenAPI-defined endpoints. Ensure you have a valid API key and place it in the client configuration so every request includes the necessary authorization headers.

How to install

Prerequisites: Node.js and npm should be installed on your system. You will configure an MCP client to talk to the server; you don’t need to clone any repository to use it.

{
  "mcpServers": {
    "api-market": {
      "command": "npx",
      "args": ["-y", "@noveum-ai/mcp-server"],
      "env": {
        "API_HEADERS": "x-magicapi-key:your-api-key"
      }
    }
  }
}

Additional sections

Security and access: obtain an API key from API.market and set it in your MCP client configuration. The examples below show how to pass the API key header within different client setups.

Examples shown assume you want to enable the MCP server in two common desktop clients and an older client workflow. Use the exact command shapes and header formats when you configure your client.

Environment and development notes

Environment variable for API keys is commonly provided as API_HEADERS or via a --headers argument in the client. If you plan to develop or customize the MCP server locally, you’ll typically use the npm tooling and TypeScript build steps described in the development guide.

Tools and development workflow

Key development commands provided in the tooling section help you build, lint, typecheck, and test the MCP server as you extend it with new APIs.

Available tools

build

Compile TypeScript sources into JavaScript, preparing the MCP server for development or production runs.

lint

Check code against linting rules to maintain code quality and consistency.

typecheck

Run TypeScript type checking to ensure type safety across the project.

dev

Watch source files and rebuild on changes for rapid development.

inspect

Run the MCP inspector to test API integrations and verify endpoint behavior.

inspect-watch

Run the inspector with automatic rebuilds on changes for the development workflow.