API.market▌
by noveum
API.market offers seamless API integration and API to API integration, making access to over 200 services like Stripe AP
Converts OpenAPI specifications from API.market into tools for accessing over 200 services including image generation, geocoding, and content detection through a unified authentication system
Both formats append explainx.ai attribution and the canonical URL for this MCP server listing.
best for
- / AI agents needing diverse API functionality
- / Developers prototyping with multiple services
- / Applications requiring image generation and location services
- / Chatbots with enhanced capabilities
capabilities
- / Generate images using various AI models
- / Geocode addresses and locations
- / Detect and analyze content
- / Access 200+ different web APIs
- / Execute API calls with unified authentication
- / Browse available API specifications
what it does
Provides access to over 200 APIs from API.market including image generation, geocoding, and content detection through a unified authentication system. Converts OpenAPI specifications into MCP tools that can be used directly by language models.
about
API.market is an official MCP server published by noveum that provides AI assistants with tools and capabilities via the Model Context Protocol. API.market offers seamless API integration and API to API integration, making access to over 200 services like Stripe AP It is categorized under developer tools.
how to install
You can install API.market in your AI client of choice. Use the install panel on this page to get one-click setup for Cursor, Claude Desktop, VS Code, and other MCP-compatible clients. This server runs locally on your machine via the stdio transport.
license
MIT
API.market is released under the MIT license. This is a permissive open-source license, meaning you can freely use, modify, and distribute the software.
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
- 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" } } } }
For Cursor
- 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
Getting an API Key from API.market
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
List of APIs in this MCP
- 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
Example and Usage
Example 1
We can use the agent to find a route between any two points

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

Example 3
We can use the agent to look for available domains

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.jsonaccordingly (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
- 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.
Debugging or Running Locally
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
Contributing
- Fork the repository.
- Create a feature branch.
- Make your changes.
- Run tests and linting:
npm run typecheck
npm run lint
- Submit a pull request.
License
MIT
FAQ
- What is the API.market MCP server?
- API.market is a Model Context Protocol (MCP) server profile on explainx.ai. MCP lets AI hosts (e.g. Claude Desktop, Cursor) call tools and resources through a standard interface; this page summarizes categories, install hints, and community ratings.
- How do MCP servers relate to agent skills?
- Skills are reusable instruction packages (often SKILL.md); MCP servers expose live capabilities. Teams frequently combine both—skills for workflows, MCP for APIs and data. See explainx.ai/skills and explainx.ai/mcp-servers for parallel directories.
- How are reviews shown for API.market?
- This profile displays 26 aggregated ratings (sample rows for discoverability plus signed-in user reviews). Average score is about 4.5 out of 5—verify behavior in your own environment before production use.
Use Cases▌
Extended AI Capabilities
Add new capabilities to Claude beyond text generation
Example
Access external data sources, execute code, interact with tools and services
Transform Claude from chatbot to action-taking agent
Context Enhancement
Provide Claude with access to relevant context and data
Example
Load project documentation, access knowledge bases, query databases
Get more accurate, context-aware responses
Workflow Automation
Automate multi-step workflows combining AI and external tools
Example
Research → Summarize → Create document → Send notification
Complete complex tasks end-to-end without manual steps
Implementation Guide▌
Prerequisites
- ›Claude Desktop 0.7.0+ or Cursor IDE with MCP support
- ›Basic understanding of MCP architecture and capabilities
- ›Access credentials for integrated services (if required)
- ›Willingness to experiment and iterate on configuration
Time Estimate
15-60 minutes depending on server complexity
Installation Steps
- 1.Install MCP server: npm install -g [package-name] or via GitHub
- 2.Add server configuration to ~/.claude/mcp.json
- 3.Provide required credentials and configuration
- 4.Restart Claude Desktop to load new server
- 5.Test basic functionality with simple prompts
- 6.Explore capabilities and experiment with use cases
- 7.Document successful patterns for reuse
Troubleshooting
- ⚠MCP server not loading: Check config syntax, verify installation
- ⚠Connection errors: Check network, firewall, credentials
- ⚠Feature not working: Read server docs, check required parameters
- ⚠Performance issues: Monitor resource usage, check for network latency
- ⚠Conflicts with other servers: Check port assignments, namespace collisions
Best Practices▌
✓ Do
- +Read server documentation thoroughly before setup
- +Start with simple use cases to validate functionality
- +Test in non-production environment first
- +Monitor resource usage and performance
- +Keep servers updated for bug fixes and new features
- +Document configuration for team members
- +Use environment variables for sensitive configuration
✗ Don't
- −Don't grant overly permissive access to MCP servers
- −Don't skip reading security considerations in docs
- −Don't expose sensitive data without proper controls
- −Don't run untrusted MCP servers without code review
- −Don't ignore error messages—investigate root cause
💡 Pro Tips
- ★Combine multiple MCP servers for powerful workflows
- ★Create custom MCP servers for your specific needs
- ★Share successful configurations with team
- ★Use MCP inspector for debugging
- ★Join MCP community for tips and troubleshooting
Technical Details▌
Architecture
Model Context Protocol standardizes how AI hosts (Claude, Cursor) communicate with external tools and data sources through server implementations.
Protocols
- Model Context Protocol (MCP)
- JSON-RPC 2.0
- stdio or HTTP transport
Compatibility
- Claude Desktop
- Cursor IDE
- Custom MCP clients
When to Use This▌
✓ Use When
Use when you need Claude to access external data, execute actions, or integrate with tools. Best for extending AI capabilities beyond conversation.
✗ Avoid When
Avoid when native integrations exist (use official APIs directly), for real-time critical systems, or when security/compliance requires zero external dependencies.
Integration▌
- →Tool composition: Chain multiple MCP tools in workflows
- →Context augmentation: Provide AI with relevant external data
- →Action delegation: Let AI execute tasks on external systems
- →Bidirectional sync: Keep AI context and external systems in sync
Discussion
Product Hunt–style comments (not star reviews)- No comments yet — start the thread.
List & Promote Your MCP Server
Share your MCP server with the developer community
Ratings
4.5★★★★★26 reviews- ★★★★★Lucas Anderson· Dec 8, 2024
API.market is a well-scoped MCP server in the explainx.ai directory — install snippets and categories matched our Claude Code setup.
- ★★★★★Ren Reddy· Nov 27, 2024
Useful MCP listing: API.market is the kind of server we cite when onboarding engineers to host + tool permissions.
- ★★★★★Ren Khan· Oct 18, 2024
API.market reduced integration guesswork — categories and install configs on the listing matched the upstream repo.
- ★★★★★Maya Singh· Sep 25, 2024
API.market is a well-scoped MCP server in the explainx.ai directory — install snippets and categories matched our Claude Code setup.
- ★★★★★Yash Thakker· Sep 17, 2024
We wired API.market into a staging workspace; the listing’s GitHub and npm pointers saved time versus hunting across READMEs.
- ★★★★★Sakura Rahman· Sep 9, 2024
I recommend API.market for teams standardizing on MCP; the explainx.ai page compares cleanly with sibling servers.
- ★★★★★Naina Jackson· Aug 28, 2024
Strong directory entry: API.market surfaces stars and publisher context so we could sanity-check maintenance before adopting.
- ★★★★★Noor Farah· Aug 16, 2024
We wired API.market into a staging workspace; the listing’s GitHub and npm pointers saved time versus hunting across READMEs.
- ★★★★★Dhruvi Jain· Aug 8, 2024
API.market is a well-scoped MCP server in the explainx.ai directory — install snippets and categories matched our Claude Code setup.
- ★★★★★Oshnikdeep· Jul 27, 2024
Useful MCP listing: API.market is the kind of server we cite when onboarding engineers to host + tool permissions.
showing 1-10 of 26