We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/littlebearapps/wp-navigator-mcp'
If you have feedback or need assistance with the MCP directory API, please join our Discord server
publish.yml•1.65 kB
name: Publish to npm
# This workflow can be triggered:
# 1. Automatically via release-please.yml after a release is created (primary method)
# 2. Manually via workflow_dispatch for re-runs or recovery
# 3. On release published event (backup, may require manual draft toggle due to GITHUB_TOKEN limitations)
#
# NOTE: This workflow only runs in the PUBLIC repo (littlebearapps/wp-navigator-mcp).
# The master repo (private) should not publish - provenance requires public repos.
on:
release:
types: [published]
workflow_dispatch:
inputs:
version:
description: 'Version to publish (for logging only, publishes package.json version)'
required: false
type: string
jobs:
publish:
runs-on: ubuntu-latest
# Skip if running in master (private) repo - provenance requires public repo
if: github.repository == 'littlebearapps/wp-navigator-mcp'
permissions:
contents: read
id-token: write # Required for npm provenance
steps:
- name: Checkout
uses: actions/checkout@v4
- name: Setup Node.js
uses: actions/setup-node@v4
with:
node-version: '20'
registry-url: 'https://registry.npmjs.org'
- name: Install dependencies
# Use --ignore-scripts to skip native builds (sharp from @xenova/transformers)
# We only need TypeScript compilation, not ML inference
run: npm ci --ignore-scripts
- name: Build TypeScript
run: npm run build
- name: Publish to npm
run: npm publish --access public --provenance
env:
NODE_AUTH_TOKEN: ${{ secrets.NPM_TOKEN }}