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.
You do not need to clone this repository to use this MCP server. You can simply configure it in your client of choice.
- Locate or create your Claude Desktop configuration file:
- On macOS:
~/Library/Application Support/Claude/claude_desktop_config.json
- On macOS:
- 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" } } } }
- Go to File -> Preferences -> Cursor Settings.
- Select MCP.
- Click on Add new global MCP Server.
- 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>"
]
},
- 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
To obtain an API key
- Log in to API.market
- Go to your profile and select 'My API Keys'
- Your API keys will be displayed here
- GET-trueway-matrix-MatrixService-CalculateDrivingMatrix
- GET-magicapi-whisper-predictions--request_id
- POST-magicapi-whisper-whisper
- POST-capix-faceswap-upload
- POST-capix-faceswap-faceswap-v1-image
- POST-capix-faceswap-faceswap-v1-video
- POST-capix-faceswap-result
- GET-trueway-geocoding-GeocodingService-Geocode
- GET-trueway-geocoding-GeocodingService-ReverseGeocode
- POST-magicapi-dnschecker-dnschecker
- GET-magicapi-coder-predictions--request_id
- POST-magicapi-coder-coder
- POST-bridgeml-nsfw-detection-nsfw_detection
- GET-magicapi-whois-whois--domain-
- GET-magicapi-deblurer-predictions--request_id
- POST-magicapi-deblurer-deblurer
- POST-bridgeml-text-to-image-text_to_image
- GET-magicapi-period-predictions--request_id
- POST-magicapi-period-period
- GET-trueway-places-PlacesService-FindPlaceByText
- GET-trueway-places-PlacesService-FindPlacesNearby
- GET-magicapi-hair-predictions--request_id
- POST-magicapi-hair-hair
- POST-bridgeml-codellama-bridgeml-codellama
- GET-brave-brave-videos-search
- GET-brave-brave-web-search
- GET-brave-brave-images-search
- GET-brave-brave-news-search
- GET-brave-brave-suggest-search
- GET-brave-brave-spellcheck-search
- POST-magicapi-domainchecker-check_domains
- GET-trueway-routing-DirectionsService-FindDrivingRoute
- GET-trueway-routing-DirectionsService-FindDrivingPath
- POST-pipfeed-parse-extract
We can use the agent to find a route between any two points
We can use the agent to find news about any topic, and then dig deeper into the articles
We can use the agent to look for available domains
The utils
folder contains helper scripts for managing API configurations, parsing OpenAPI specifications, and registering new APIs into the MCP server.
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
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
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
Rebuild the project to apply the changes:
npm run build
Then, test the new API integration using:
npm run inspect
If you want to contribute this new API to the repository:
- Fork the repo.
- Create a branch.
- Submit a pull request (PR).
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
npm run build
- Builds the TypeScript source.npm run clean
- Removes build artifacts.npm run typecheck
- Runs TypeScript type checking.
npm run dev
- Watches source files and rebuilds on changes.npm run inspect-watch
- Runs the inspector with auto-reload on changes.
npm run lint
- Runs ESLint.npm run typecheck
- Verifies TypeScript types.
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"
- Start the development environment:
npm run inspect-watch
- Modify the TypeScript files in
src/
. - The server will automatically rebuild and restart.
- Use the MCP Inspector UI to test your changes.
To debug or run the MCP server locally:
- Clone the repository and install dependencies:
git clone https://github.com/Noveum/api-market-mcp-server.git
cd api-market-mcp-server
npm install
- Build the server:
npm run build
- For debugging, you can run:
npm run inspect
- Fork the repository.
- Create a feature branch.
- Make your changes.
- Run tests and linting:
npm run typecheck
npm run lint
- Submit a pull request.
MIT