Get the FREE Ultimate OpenClaw Setup Guide →

muapi

Mcp server code to setup muapi to work with clients like Claude, Cursor etc.

Installation
Run this command in your terminal to add the MCP server to Claude Code.
Run in terminal:
Command
claude mcp add --transport stdio samuraigpt-muapi-mcp-server node server.js \
  --env MUAPI_API_KEY="your-api-key-here" \
  --env MUAPI_BASE_URL="https://api.muapi.example"

How to use

The MUAPI MCP Server bridges clients like Claude or Cursor to the MUAPI service. It exposes an MCP-compatible interface that translates client requests into MUAPI calls and returns responses back to the client. Once running, you can connect your MCP-enabled clients to the muapi server name, and use the available commands and prompts to interact with MUAPI features such as natural language processing, content generation, or tool-specific actions provided by MUAPI.

To use it, start the server with the configured command and environment variables. Then configure your MCP client to point at the muapi server and send requests using the MCP protocol. The server handles request routing, authentication via the API key, and response formatting, making it straightforward to integrate Claude, Cursor, or other MCP-enabled clients.

How to install

Prerequisites:

  • Node.js (version >= 14) installed on your system
  • Access to the muapi service and an API key

Step-by-step installation:

  1. Clone the MCP server repository: git clone https://github.com/your-org/samuraigpt-muapi-mcp-server.git cd samuraigpt-muapi-mcp-server

  2. Install dependencies: npm install

  3. Configure environment variables:

    • MUAPI_BASE_URL: Base URL for the MUAPI service
    • MUAPI_API_KEY: Your MUAPI API key
  4. Run the server: npm run start

    or if a direct node entry is provided

    node server.js

  5. Verify the server is listening (defaults to port 3000): curl http://localhost:3000/health

  6. Point your MCP client to the muapi server endpoint as described in your client docs.

Additional notes

Notes:

  • Ensure your MUAPI API key is kept secret and not committed to version control.
  • If you change the listening port, update both the server environment and your MCP client configuration.
  • Check logs for any authentication or connectivity issues with MUAPI.
  • If your MUAPI instance requires TLS, ensure your environment provides the proper certificates and update MUAPI_BASE_URL accordingly.
  • This MCP server acts as a translator between MCP clients and MUAPI; it does not store user data beyond request/response lifecycles.

Related MCP Servers

Sponsor this space

Reach thousands of developers