Apexapi Mcp

io.github.apexapiPublished by GitHub account apexapiv0.1.1Updated Oct 24, 2026

Call 120+ AI models and live web context (scrape/crawl/extract) from any MCP client with one key

VerifiedSTDIODesktop onlyWeb Search & ScrapingAI & ML

Overview

AI-generated overview

ApexApi MCP lets an assistant call 120+ AI models and scrape, crawl or extract live web content through one prepaid API key.

What you can do
  • Chat with 120+ hosted models and list the available models
  • Check the remaining prepaid balance on the account
  • Scrape a single page, crawl a whole site, and extract structured data from pages
  • Track long-running jobs with a job status check
  • Generate images and text-to-speech audio
When to use it
Useful when you want one MCP client to reach many model providers plus live web scraping and structured extraction without wiring up each vendor separately, and you are fine with a single prepaid balance covering all calls.
Requirements
Runs locally over stdio via the npm package apexapi-mcp (Node.js/npx), or as a remote Streamable HTTP endpoint with an Authorization bearer header. Requires an ApexApi API key (starts with ak-) supplied as the APEXAPI_API_KEY environment variable, and network access.
Before you install
The API key is a billable credential: all model, scraping, image and speech calls draw on a prepaid balance, so usage costs money. Scraped page content and prompts are sent to ApexApi's servers and onward to the model providers. The README also mentions agent self-registration for obtaining keys, so review how a key is created and scoped before use.

Installation

In SourceWeft

  1. Open Apexapi Mcp in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.

Other MCP clients

Follow the launch instructions in the repository.

README

apexapi-mcp

MCP server for ApexApi — call 120+ AI models (OpenAI, Anthropic, Google, DeepSeek, Qwen…) and read the live web (scrape / crawl / structured extract) from any MCP client, with one ak- API key and one prepaid balance.

Tools

chat, list_models, get_balance, scrape_page, crawl_site, extract_structured, check_job, generate_image, generate_speech

Local (stdio)

Get a key at https://apexapi.dev/keys, then add to your MCP client config:

json
{  "mcpServers": {    "apexapi": {      "command": "npx",      "args": ["-y", "apexapi-mcp"],      "env": { "APEXAPI_API_KEY": "ak-..." }    }  }}

Claude Code: claude mcp add apexapi -e APEXAPI_API_KEY=ak-... -- npx -y apexapi-mcp

Remote (Streamable HTTP)

Endpoint: https://api.apexapi.dev/mcp with header Authorization: Bearer ak-...

Responses use MCP Streamable HTTP framing (SSE) — clients like Claude Code handle this natively; it is not a plain-JSON REST endpoint.

Claude Code: claude mcp add --transport http apexapi https://api.apexapi.dev/mcp --header "Authorization: Bearer ak-..."

Docs

https://apexapi.dev/docs/mcp

Source: README.md at commit 1ef0f61

Tools

0
SourceWeft has not started this package in its sandbox yet, so its tools are not known.

Version history

1
  1. v0.1.1LatestSep 16, 2026

Score

50% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 days25 pts

    Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.

  • Auth declared10 pts

    Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.

  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts
  • License10 pts