api-market

The API-MARKET MCP Server exposes the endpoints from API.market as MCP resources, allowing language models and automation agents to discover and interact with the wide catalog of APIs defined by OpenAPI specifications. By wiring the MCP server into your client (e.g., Claude Desktop or Cursor) and providing an API key via the API_HEADERS (x-magicapi-key) header, you enable authenticated access to API.market through the MCP protocol. This setup enables querying available APIs, inspecting endpoints, and invoking API operations through natural language or structured prompts. The server itself is designed to be drop-in ready via npx, so you can enable it without cloning the repository and without complex setup.

Prerequisites:

• Node.js and npm installed on your system
• Basic familiarity with MCP configuration files for your client (Claude Desktop, Cursor, etc.)

Installation steps:

1. Ensure Node.js and npm are installed. Verify versions:
   • node -v
   • npm -v
2. Run the MCP server via npx (no repository clone needed):

   npx -y @noveum-ai/mcp-server
   

   This will start the MCP server using the published package without needing to install globally.
3. Configure your MCP client to point to the api-market server with the API key header:
   • For Claude Desktop, add the following to your claude_desktop_config.json (or equivalent) under mcpServers:

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

   • For Cursor, add the following to mcp.json:

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

4. Replace <your-api-key> with your actual API.market API key obtained from the API.market dashboard.
5. Start your client and verify that you can discover and invoke API.market endpoints through the MCP interface.

Tips and common considerations:

• You must provide a valid API key via the API_HEADERS environment variable (or --headers in some clients) to access API.market APIs.
• The MCP server here is exposed via the npx command, so you don’t need to install the package globally; the first run will fetch the package.
• API.market offers a large catalog (200+ APIs). If you enable headers globally, ensure your key has the appropriate permissions for the APIs you intend to access.
• If you encounter issues, verify that your client’s MCP configuration points to the same command and header format shown in the examples, and ensure network access to API.market endpoints.
• You can update the API key in your client configuration without changing the server setup; rotate keys as needed and refresh your client config accordingly.