mcpField
A
API-MARKET MCP Server

API-MARKET MCP Server

Local
github.com/NoveumDeveloper Tools4Updated 82w ago

About API-MARKET MCP Server

API-MARKET MCP Server exposes API.market endpoints described by OpenAPI specifications to LLMs and agents. It supports discovering and interacting with available APIs through MCP, with API access configured using headers.

Key features

  1. 01Expose API.market endpoints as MCP resources
  2. 02Use OpenAPI specifications for API definitions
  3. 03Discover and interact with available APIs
  4. 04Configure API headers for access

Use cases

  1. 01Find APIs for routing or geocoding tasks
  2. 02Search news or web content through APIs
  3. 03Check domain availability through an API

MCP support

Exposes API.market endpoints to MCP clients as resources so LLMs and agents can discover and interact with APIs. API request headers can be configured for access.

Configuration

Local server config is the same for every client. Copy it into your client’s MCP config file.

mcp.json · Universal config
{
"mcpServers": {
"Noveum_api-market": {
"command": "npx",
"args": [
"-y",
"@noveum-ai/mcp-server"
]
}
}
}
Run commandnpx -y @noveum-ai/mcp-server

Local servers need a runtime on your machine (e.g. Node.js 18+). Config file locations differ by client; see your client’s docs.

Packages
npm@noveum-ai/mcp-server

Tools

34

Saved tool list · updated 2w ago

ParameterTypeRequiredDescription
originsstringYesList of origins described as semicolon-delimited coordinate pairs with latitudes and longitudes. Maximum 25 pairs per request.
destinationsstringNoList of destinations described as semicolon-delimited coordinate pairs with latitudes and longitudes. If not specified, an n x n matrix will be generated using the origins. Maximum 25 pairs per request.
avoid_tollsbooleanNoAvoid tolls
avoid_highwaysbooleanNoAvoid highways
avoid_ferriesbooleanNoAvoid ferries
start_timestringNoTime when travel is expected to start. You can specify the time as an integer in seconds since midnight, January 1, 1970 UTC or you can use 'now' to specify the current time.

Details

From the project README

API-MARKET MCP Server

About

A Model Context Protocol (MCP) server that exposes API-Market's endpoints as MCP resources. This server allows Large Language Models to discover and interact with APIs defined by OpenAPI specifications through the MCP protocol.
This repository provides access to the APIs available at API.market. The tool is free to use and allows agents to communicate freely with all available APIs, making it super powerful. With over 200+ APIs available at API.market, you can leverage a wide range of functionalities.

Quick Start

You do not need to clone this repository to use this MCP server. You can simply configure it in your client of choice.

For Claude Desktop
  1. Locate or create your Claude Desktop configuration file:
    • On macOS: ~/Library/Application Support/Claude/claude_desktop_config.json
  2. Add the following configuration to enable the API-Market MCP server:
    {
      "mcpServers": {
        "api-market": {
          "command": "npx",
          "args": ["-y", "@noveum-ai/mcp-server"],
          "env": {
            "API_HEADERS": "x-magicapi-key:your-api-key"
          }
        }
      }
    }
    
For Cursor
  1. Go to File -> Preferences -> Cursor Settings.
  2. Select MCP.
  3. Click on Add new global MCP Server.
  4. Paste the following into the mcp.json file.
  {
    "mcpServers": {
      "api-market": {
        "command": "npx",
        "args": [
          "-y",
          "@noveum-ai/mcp-server",
          "--headers",
          "x-magicapi-key:<your-api-key>"
        ]
      }
    }
  }

Alternatively, add this as the first entry in mcpServers.

    "api-market": {
      "command": "npx",
      "args": [
        "-y",
        "@noveum-ai/mcp-server",
        "--headers",
        "x-magicapi-key:<your-api-key>"
      ]
    },
  1. For older versions of Cursor, add the following command after clicking on Add new MCP server
npx -y @noveum-ai/mcp-server --headers x-magicapi-key:your-api-key

Getting an API Key from API.market

To obtain an API key

  1. Log in to API.market
  2. Go to your profile and select 'My API Keys'
  3. Your API keys will be displayed here

List of APIs in this MCP

Example and Usage

Example 1

We can use the agent to find a route between any two points

Example 1

Example 2

We can use the agent to find news about any topic, and then dig deeper into the articles

Example 2.1 Example 2.2

Example 3

We can use the agent to look for available domains

Example 3

Development

Adding a New API to the MCP Server

The utils folder contains helper scripts for managing API configurations, parsing OpenAPI specifications, and registering new APIs into the MCP server.

1. Locate the OpenAPI Specification

Find the OpenAPI JSON for the API you want to integrate. After that, create a folder json_files in the root directory of the project and add your OpenAPI JSON spec to the folder

2. Modify the OpenAPI Specification

After obtaining the OpenAPI spec, use modify_api.py to update the path inside the spec to include the file name.

python utils/modify_api.py
3. Update API Summaries

After modifying the paths, update the API summaries by choosing one of the following options:

  • Automatically shorten summaries using an LLM:
python utils/LLM_summary_shortener.py 
  • Manually update the summaries:
python utils/manual_summary_shortener.py 
4. Build and Test

Rebuild the project to apply the changes:

npm run build

Then, test the new API integration using:

npm run inspect
5. Submit Your Changes

If you want to contribute this new API to the repository:

  • Fork the repo.
  • Create a branch.
  • Submit a pull request (PR).
6. Publish the MCP server (Optional)

If you want to publish your changes:

  • Update the package.json accordingly (e.g., update the version, name, etc.).
  • Publish the package:
npm publish --access public

Development Tools

Building
  • npm run build - Builds the TypeScript source.
  • npm run clean - Removes build artifacts.
  • npm run typecheck - Runs TypeScript type checking.
Development Mode
  • npm run dev - Watches source files and rebuilds on changes.
  • npm run inspect-watch - Runs the inspector with auto-reload on changes.
Code Quality
  • npm run lint - Runs ESLint.
  • npm run typecheck - Verifies TypeScript types.
Command Line Arguments
npm run inspect -- \
  --api-base-url https://api.magicapi.dev/api/v1/ \
  --openapi-spec modified_files.txt \
  --headers "x-magicapi-key:your-api-key" \
  --name "my-mcp-server" \
  --version "1.0.0"
Development Workflow
  1. Start the development environment:
npm run inspect-watch
  1. Modify the TypeScript files in src/.
  2. The server will automatically rebuild and restart.
  3. Use the MCP Inspector UI to test your changes.
Debugging or Running Locally

To debug or run the MCP server locally:

  1. Clone the repository and install dependencies:
git clone https://github.com/Noveum/api-market-mcp-server.git
cd api-market-mcp-server
npm install
  1. Build the server:
npm run build
  1. For debugging, you can run:
npm run inspect 
Contributing
  1. Fork the repository.
  2. Create a feature branch.
  3. Make your changes.
  4. Run tests and linting:
npm run typecheck
npm run lint
  1. Submit a pull request.
License

MIT

Comments

Markdown supported

New to MCP?

From what the protocol is to installing your first server, these answers cover most first questions.

An open protocol that defines how AI applications connect to external tools and data in a uniform way. Clients talk to the model; MCP servers provide tools, resources and prompt templates. They exchange standard messages, so one server can be reused by many clients.