Kirha Smithery Gateway

A configurable MCP (Model Context Protocol) server for Kirha Crypto tool planning ready to use with Smithery
  • typescript

1

GitHub Stars

typescript

Language

6 months ago

First Indexed

2 months ago

Catalog Refreshed

Documentation & install

Readme and setup notes from the catalogue, plus a client-ready config you can copy for your MCP host.

Installation

Add the following to your MCP client configuration file.

Configuration

View docs

The Kirha Smithery Gateway is a configurable MCP server designed to plan and execute tools for Kirha crypto workstreams. It provides secure, session-based tool execution, easy JSON configurations, and a modular setup that lets you tailor tool planning to your crypto workflows while keeping development and debugging straightforward.

How to use

You connect to the Kirha Smithery Gateway with an MCP client to plan and run crypto-related tools. Each client session receives its own API key, which you will use to authenticate and scope tool actions to that session. Enable or disable debug logging per session to help diagnose issues during development. Tools register dynamically based on your configuration, and their behavior can leverage session-specific settings so you can tailor results per user or project.

How to install

Prerequisites you need before installing this MCP server are Node.js and npm. Ensure you have a current Node.js runtime and npm installed on your system.

Install dependencies for the project.

npm install

Run in development mode to test locally.

npm run dev

Build the project for production and start the built server.

npm run build
npm start

Additional sections

Configuration details are provided below to help you set up the MCP server for Kirha Crypto planning. You can manage environment options, tool definitions, and API endpoints to align with your security and tooling needs.

Configuration details

# smithery.yaml
runtime: "container"
startCommand:
  type: "http"
  configSchema:
    type: "object"
    properties:
      apiKey:
        type: "string"
        description: "Your API key"
      debug:
        type: "boolean"
        description: "Enable debug logging"
        default: false
      configPath:
        type: "string"
        description: "Path to custom configuration file"
    required: ["apiKey"]
# config.json
{
  "mcp": {
    "name": "kirha-crypto",
    "version": "1.0.0"
  },
  "tool": {
    "name": "execute-crypto-tool-planning",
    "title": "Crypto Tool Planning",
    "description": "Execute crypto-related tool planning",
    "enabled": true
  },
  "vertical": "crypto",
  "api": {
    "executeToolPlanningUrl": "https://api.kirha.ai/chat/v1/tool-planning/execute",
    "summarization": {
      "enable": true,
      "model": "kirha-flash"
    }
  }
}

You also configure the API call endpoint and tool mapping through these settings to ensure tools are registered and executed in the session context.

## Notes on session management and debugging

Each client connection is bound to a session-specific API key. Tools access session-scoped configuration, and API keys are securely passed to tool execution functions.

Enable debug mode for a session to surface additional diagnostics during development. You can activate it by initiating the MCP session with the debug flag.

GET /mcp?apiKey=your-key&debug=true


This will log configuration loading, tool registration, tool execution, and error details.

Available tools

execute_crypto_tool_planning

Executes crypto-related tool planning based on the configured tool and API endpoints.

Built by
VeilStrat
AI signals for GTM teams
© 2026 VeilStrat. All rights reserved.All systems operational