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

@centia/mcp-server

v1.0.1

Published

Centia MCP Server

Readme

Centia MCP Server

A Model Context Protocol (MCP) server that exposes the Centia API as MCP tools generated from the OpenAPI spec. It communicates over STDIO and can be used with any MCP-compatible client (Claude Desktop, MCP Inspector, etc.).

Prerequisites

  • Node.js 18+ (20+ recommended)
  • npm 9+

Install

# From the project root
npm install

Configuration

The server accepts the following environment variables:

  • API_BASE_URL (optional) — Base URL for the Centia API. Default: https://api.centia.io
  • API_TOKEN (recommended) — Personal access token for Centia. Most endpoints/tools require authentication; set this to enable them.

The API surface is defined in centia-api.json (already included in the repo). The server reads it at runtime to generate tools.

Run locally (development)

Hot‑reload development run with tsx:

npm run dev

This starts the MCP server on STDIO. It is meant to be launched by an MCP client (see below), but you can also smoke‑test it with the MCP Inspector.

Run with npx

You can run the server directly using npx.

If running from the source locally:

npm run build
npx .

If the package is installed or you want to use the published version:

npx @centia/mcp-server

Build and run (production)

npm run build
npm start

This compiles TypeScript to dist/ and starts node dist/index.js.

If you need environment variables:

API_TOKEN=your_token_here npm start
# or
API_BASE_URL=https://api.centia.io API_TOKEN=your_token_here npm run dev

Using with MCP Inspector (recommended for local testing)

MCP Inspector lets you connect to the server and try tools interactively.

  1. Start the Inspector UI:
    npx @modelcontextprotocol/inspector -- npx @centia/mcp-server
  2. If needed, add environment variables in the Inspector connection dialog (e.g., API_TOKEN).

Using with Claude Desktop

Add the server to your Claude Desktop MCP config (e.g., claude_desktop_config.json).

Using npx (easiest)

{
  "mcpServers": {
    "centia": {
      "command": "npx",
      "args": ["-y", "@centia/mcp-server"],
      "env": {
        "API_TOKEN": "YOUR_CENTIA_TOKEN",
        "API_BASE_URL": "https://api.centia.io"
      }
    }
  }
}

Using local source

{
  "mcpServers": {
    "centia": {
      "command": "npm",
      "args": ["run", "start"],
      "env": {
        "API_TOKEN": "YOUR_CENTIA_TOKEN",
        "API_BASE_URL": "https://api.centia.io"
      },
      "cwd": "/absolute/path/to/your/mcp-server"
    }
  }
}
  • For development, replace "args": ["run", "start"] with "args": ["run", "dev"].
  • Ensure cwd points to this project directory.

NPM scripts

  • npm run dev — Run TypeScript directly with tsx (hot‑reload style dev loop).
  • npm run build — Compile TypeScript to CommonJS/ESM in dist/ via tsc.
  • npm start — Run the built server (node dist/index.js).

Using AGENT.md with AI Coding Agents

This repository includes an AGENT.md file that provides specific instructions and best practices for AI coding agents (like Claude Code, Junie, etc.) when working with Centia BaaS.

To ensure your AI agent follows these rules while developing your application:

  1. Copy the AGENT.md file from this repository to the root or src/ folder of your own application's repository.
  2. When starting a session with your AI agent, it will automatically find and follow the guidelines defined in AGENT.md.

The guide covers:

  • Prime Directive: Preferring MCP tools and official SDKs.
  • Tool Priority: Order of interaction (MCP tools > SDK > HTTP).
  • Project Structure: Recommended layout for Centia-based apps.
  • Security & Auth: How to handle tokens and OAuth flows correctly.

Troubleshooting

  • Tools missing or inputs look odd: ensure centia-api.json exists and is valid. The server generates tools from this file at startup.
  • 401/403 errors: set a valid API_TOKEN in the environment.
  • JSON Schema validation errors: schemas are auto‑normalized/sanitized for MCP, but if you updated centia-api.json, re-run and check logs for details.
  • ESM/CommonJS issues: this project uses ESM ("type": "module"). Use Node.js 18+ and run scripts via npm as shown above.

License

ISC