@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 installConfiguration
The server accepts the following environment variables:
API_BASE_URL(optional) — Base URL for the Centia API. Default:https://api.centia.ioAPI_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 devThis 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-serverBuild and run (production)
npm run build
npm startThis 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 devUsing with MCP Inspector (recommended for local testing)
MCP Inspector lets you connect to the server and try tools interactively.
- Start the Inspector UI:
npx @modelcontextprotocol/inspector -- npx @centia/mcp-server - 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
cwdpoints to this project directory.
NPM scripts
npm run dev— Run TypeScript directly withtsx(hot‑reload style dev loop).npm run build— Compile TypeScript to CommonJS/ESM indist/viatsc.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:
- Copy the
AGENT.mdfile from this repository to the root orsrc/folder of your own application's repository. - 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.jsonexists and is valid. The server generates tools from this file at startup. - 401/403 errors: set a valid
API_TOKENin 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
