npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details

    pkg:[package-name]

  • User packages

    @[username]

Sponsor

Optimize Toolset

I’ve always been into building performant and accessible sites, but lately I’ve been taking it extremely seriously. So much so that I’ve been building a tool to help me optimize and monitor the sites that I build to make sure that I’m making an attempt to offer the best experience to those who visit them. If you’re into performant, accessible and SEO friendly sites, you might like it too! You can check it out at Optimize Toolset.

About

Hi, 👋, I’m Ryan Hefner  and I built this site for me, and you! The goal of this site was to provide an easy way for me to check the stats on my npm packages, both for prioritizing issues and updates, and to give me a little kick in the pants to keep up on stuff.

As I was building it, I realized that I was actually using the tool to build the tool, and figured I might as well put this out there and hopefully others will find it to be a fast and useful way to search and browse npm packages as I have.

If you’re interested in other things I’m working on, follow me on Twitter or check out the open source projects I’ve been publishing on GitHub.

I am also working on a Twitter bot for this site to tweet the most popular, newest, random packages from npm. Please follow that account now and it will start sending out packages soon–ish.

Open Software & Tools

This site wouldn’t be possible without the immense generosity and tireless efforts from the people who make contributions to the world and share their work via open source initiatives. Thank you 🙏

© 2026 – Pkg Stats / Ryan Hefner

@wootsup/apimapper-mcp

v0.6.0

Published

API Mapper MCP Server — multi-platform (WordPress/Joomla), multi-AI-client, Stripe-style auth, bundled skills

Vulnerabilities

Powered byPowered by Snyk
  • 0High
  • 0Medium
  • 0Low

Links

Git

Maintainers

getimo-productionsgetimo-productions

Keywords

mcpmodel-context-protocolapi-mapperwordpressjoomlaclaudechatgptcursor

Readme

@wootsup/apimapper-mcp

Build YOOtheme dynamic content via natural conversation. The official MCP server for API Mapper — connect your AI assistant to API Mapper running on WordPress or Joomla, then create flows, manage OAuth credentials, and publish sources without leaving the chat.

npm version license

Install

Two paths, pick one.

Option A — npx (Claude Code, Cursor, VS Code, Cline, Codex CLI)

npx -y @wootsup/apimapper-mcp setup

The interactive wizard:

  1. Asks which AI client(s) you use (auto-detected when possible).
  2. Prompts for your API Mapper site URL and MCP key.
  3. Runs an identity-probe handshake against your site.
  4. Patches the client's MCP config (~/.claude.json, ~/.cursor/mcp.json, VS Code settings.json, etc.) idempotently.
  5. Installs the bundled skill to ~/.claude/skills/apimapper/.

Re-run any time — writers are idempotent. Use --help to see all subcommands.

Option B — Claude Desktop (DXT bundle)

  1. Download apimapper-mcp.mcpb — see the installation guide.
  2. Drag it onto the Claude Desktop window (or Settings → Developer → Install from file).
  3. Enter your site URL, MCP key, and platform when prompted.

Setup (3 steps)

  1. Install the API Mapper plugin on your site:
  2. Generate an MCP key in the admin:
    • WordPress: click API Mapper in the WP admin menu — the flow editor opens. In the editor header (top-right), click the ⋮ (three-dot) menu → Settings. In the modal's left sidebar, click MCP Access → New API key.
    • Joomla: Components → API Mapper loads the same editor — use the same ⋮ → Settings → MCP Access path.
    • Token shape: amk_live_… (production) or amk_test_… (sandbox).
  3. Run npx -y @wootsup/apimapper-mcp setup (or install the DXT) and paste the key. The wizard verifies it with an HMAC-SHA256 identity probe before writing config.

Verify in your AI client:

You:  apimapper_health
LLM:  ✅ status: ok, platform: wordpress, version: 2.0.13

Common tools

A small set of high-leverage tools. The full surface is 79 tools: 19 are first-class in tools/list, and the other 60 route through the apimapper_advanced gateway (so the listed surface stays under each client's tool cap). Everything is documented in detail in the tools reference.

| Tool | What it does | |------|--------------| | apimapper_health | Connectivity + auth probe. Run this first. | | apimapper_onboarding | Lists platform, existing flows, next-step suggestions. | | apimapper_flow_setup_with_sources | Composite: create flow + add sources + compile + publish. | | apimapper_connection_list | List connections (paginated, table-formatted). | | apimapper_credential_create | Add OAuth or Bearer credentials. | | apimapper_oauth_authorize_begin | Start an OAuth 2.0 PKCE flow. | | apimapper_graph_preview | Preview a flow's output without saving. | | apimapper_library_catalog | Browse pre-built connection templates. | | apimapper_get_skill | Fetch the bundled skill text on demand. | | apimapper_advanced | Gateway to the 60 advanced tools. Call { tool } for a target's schema, or { tool, arguments } to run it. |

The 60 advanced tools (the full connection / credential / flow / library / license / schema surface) are not listed individually in tools/list — they route through apimapper_advanced so the first-class surface stays under each client's tool cap.

See the tools reference for the canonical workflow guide, and the API Mapper MCP docs for OAuth, Joomla, YOOtheme, and troubleshooting deep-dives.

Multi-platform: WordPress and Joomla

Every tool routes through a platform abstraction that detects WordPress (/wp-json/api-mapper/v1/*) vs. Joomla (/index.php?option=com_apimapper) from the site URL and platform setting. You write the same prompt; the server speaks the right dialect — including the Joomla com_ajax envelope unwrap.

Multi-client

Supported AI clients (auto-detected by the setup wizard):

  • Claude Desktop — DXT bundle or ~/Library/Application Support/Claude/
  • Claude Code — ~/.claude.json
  • Cursor — ~/.cursor/mcp.json (or project-local .cursor/mcp.json)
  • VS Code — workspace .vscode/settings.json mcp.servers
  • Cline — VS Code extension settings
  • Codex — ~/.codex/config.toml
  • ChatGPT Desktop — when MCP support ships

The server ships stdio-only (local install via npx or the Claude Desktop DXT bundle).

Troubleshooting

See the troubleshooting guide. Common cases:

  • 403 invalid_token → token expired or wrong site URL. Re-run setup.
  • 404 on every tool → plugin not installed or REST routes disabled.
  • Joomla 0 envelope → SEF/htaccess intercepting com_ajax; check the reference doc.

Feedback and support

Found a bug or have a feature request? Reach us at wootsup.com/contact.

For the security disclosure process, see SECURITY.md.

License

MIT © 2026 WootsUp / getimo productions.

Links