mcp
MCP server for Centia.io
claude mcp add --transport stdio centia-io-mcp-server npx -y @centia/mcp-server \ --env API_TOKEN="YOUR_CENTIA_TOKEN" \ --env API_BASE_URL="https://api.centia.io"
How to use
This MCP server exposes the Centia API as a suite of MCP tools generated from the OpenAPI specification found in centia-api.json. Running the server provides STDIO-based MCP endpoints that can be accessed by any MCP-compatible client (such as Claude Desktop or MCP Inspector). Tools are created dynamically based on the API surface, and require authentication via API_TOKEN to access protected endpoints. Start the server using a compatible launcher (for example via npx as shown in the installation instructions), then connect your MCP client and browse the generated tools to perform operations against Centia resources.
Once connected, you can invoke individual tools (for example users, projects, or other Centia resources defined in the API) directly from your MCP client. Tools are surfaced according to the OpenAPI definition and can include actions like create, read, update, delete, and specialized operations documented in centia-api.json. If you need to test locally, you can also use MCP Inspector to interactively explore the available tools and their input schemas before integrating into your application.
How to install
Prerequisites:
- Node.js 18+ (20+ recommended)
- npm 9+ (comes with Node.js installations)
Install from the project root:
npm install
Configure environment variables (example):
- API_BASE_URL: https://api.centia.io (default)
- API_TOKEN: your personal Centia token (required for authenticated tools)
Run the server locally in development:
npm run dev
This starts the MCP server on STDIO for testing with MCP clients. For production-like runs, build and start:
npm run build
npm start
This compiles TypeScript to dist/ and runs the built server via node dist/index.js.
If you need to run with environment variables inline:
API_TOKEN=your_token_here npm start
# or
API_BASE_URL=https://api.centia.io API_TOKEN=your_token_here npm run dev
Additional notes
Tips and caveats:
- The server reads centia-api.json at startup to generate the available MCP tools. Ensure centia-api.json is present and valid.
- If you encounter 401/403 errors, verify that API_TOKEN is set and valid.
- This server uses ESM modules; ensure Node.js 18+ compatibility when running scripts.
- When testing with Claude Desktop or MCP Inspector, pass API_TOKEN and API_BASE_URL as environment variables in your connection configuration.
- The default API_BASE_URL is https://api.centia.io if you donβt provide one.
- For development workflows, use npm run dev for hot-reload iteration and npm run build for a production-like bundle before starting with npm start.
Related MCP Servers
context7
Context7 MCP Server -- Up-to-date code documentation for LLMs and AI code editors
editor
MCP Server for AI automation of the PlayCanvas Editor
time
β° Time MCP Server: Giving LLMs Time Awareness Capabilities
shadcn-ui
MCP server for shadcn/ui component references
job-searchoor
A simple MCP server that delivers you jobs based on your needs
advanced-homeassistant
An advanced MCP server for Home Assistant. π Batteries included.