@wootsup/anysource-mcp

@wootsup/anysource-mcp

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

---

Install

Two paths, pick one.

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

npx -y @wootsup/anysource-mcp setup

The interactive wizard:

1. Asks for your MCP key and shows its id, issuer and scope.
2. Asks for the site URL (pre-filled from the key) and which AI client(s) to configure.
3. Checks that your site answers, then patches the client's MCP config idempotently (paths under Multi-client below).
4. Tests your key with one call to the site, and rolls back if that fails.

To install the bundled skill into ~/.claude/skills/apimapper/, run npx -y @wootsup/anysource-mcp install-skill. Use --help to see all subcommands.

Option B: Claude Desktop (MCPB bundle)

1. Download anysource-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 and MCP key when prompted.

Setup (3 steps)

1. Install the AnySource for YOOtheme Pro plugin on your site:
   • WordPress: plugin from wootsup.com
   • Joomla: extension from wootsup.com
2. Generate an MCP key in the admin:
   • WordPress: click AnySource 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 MCP key.
   • Joomla: Components → AnySource loads the same editor. Use the same ⋮ → Settings → MCP access path.
   • Token shape: ask_live_… (production) or ask_test_… (sandbox). Keys created before the rename start with amk_ and keep working.
3. Run npx -y @wootsup/anysource-mcp setup (or install the MCPB) and paste the key. The wizard tests it against your site and rolls back if the site refuses it.

Verify in your AI client: ask it to run anysource_health. It reports connectivity, authentication and platform.

Common tools

The full surface is 82 tools: 23 are first-class in tools/list (20 from the plugin, 3 site tools this package answers), and the other 59 route through the anysource_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
anysource_health	Connectivity + auth probe. Run this first.
anysource_onboarding	Lists platform, existing flows, next-step suggestions.
anysource_flow_setup_with_sources	Composite: create flow + add sources + compile + publish.
anysource_connection_list	List connections (paginated, table-formatted).
anysource_credential_create	Add OAuth or Bearer credentials.
anysource_oauth_authorize_begin	Start an OAuth 2.0 PKCE flow.
anysource_graph_preview	Preview a flow's output without saving.
anysource_library_catalog	Browse pre-built connection templates.
anysource_get_skill	Fetch a skill topic on demand.
anysource_advanced	Gateway to the 59 advanced tools. Call { tool } for a target's schema, or { tool, arguments } to run it.

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

Multi-platform: WordPress and Joomla

Every call goes to the plugin's MCP endpoint: /wp-json/anysource/mcp on WordPress, /api/index.php/v1/anysource/mcp on Joomla. Without ANYSOURCE_PLATFORM, the bridge tries both and settles on the one that answers. You write the same prompt on both.

Several sites

Point ANYSOURCE_SITES_FILE at a sites.json with one entry per site and one default. Your AI lists, tests and switches sites with anysource_sites_list, anysource_sites_test and anysource_use_site.

Multi-client

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

• Claude Desktop: MCPB bundle or ~/Library/Application Support/Claude/
• Claude Code: ~/.claude.json
• Cursor: ~/.cursor/mcp.json (or project-local .cursor/mcp.json)
• VS Code: the user-profile mcp.json (~/Library/Application Support/Code/User/mcp.json on macOS), under servers
• Cline: ~/.cline/config.json
• Codex: ~/.codex/config.toml

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

Troubleshooting

See the troubleshooting guide. Common cases:

• 401 with apimapper_token_invalid (Joomla: invalid_bearer_token) → key revoked, expired or issued by another site. Issue a new key and re-run setup.
• 404 on every tool → plugin not active, or its MCP endpoint is not reachable.

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

• Homepage: https://wootsup.com
• Plugin (WordPress + Joomla): download from https://wootsup.com/downloads
• Docs: https://wootsup.com/docs/mcp/anysource/
• Installation: https://wootsup.com/docs/mcp/anysource/installation
• Tools reference: https://wootsup.com/docs/mcp/anysource/tools
• Troubleshooting: https://wootsup.com/docs/mcp/anysource/troubleshooting
• Support: https://wootsup.com/contact/
• Changelog: CHANGELOG.md