ashra

Ashra MCP is a Model Context Protocol server for Ashra that integrates with Claude and other MCP clients. To use it, configure Claude (or your MCP client) to connect to the Ashra MCP server by adding an entry named ashra in your claude_desktop_config.json (or equivalent MCP config) and point the server to the built index.js file. The server expects an API key for Ashra via the ASHRA_API_KEY environment variable. Once configured, Claude can send model-context requests through the MCP interface to the Ashra backend, enabling context-aware interactions and capabilities defined by Ashra.

To run locally, ensure you build the project and start the server with the proper environment variable. The configuration shown expects the Node.js runtime to execute the built entry at build/index.js. If you use a version manager like nvm and the default node is not the desired version, you can override the command path in the config by supplying the full path to the node binary. The Ashra MCP server will then listen for MCP requests from clients like Claude and respond with Ashra-specific context you’ve configured.

Prerequisites:

• Node.js (and optionally a Node version manager like nvm)
• Yarn (for dependency installation and build)
• Access to the Ashra MCP repository/files to build

Installation steps:

1. Install dependencies:

   • Using Yarn: yarn

2. Build the project:

   • Using Yarn: yarn build

3. Prepare configuration for Claude or your MCP client:

   • Create or update claude_desktop_config.json with the Ashra MCP server entry as shown in the README, including your ASHRA_API_KEY.

4. Run the server locally (example):

   • Ensure you are in the project root and execute the Node entry point with the required environment variable: ASHRA_API_KEY=your-key-here node <path/to/ashra-mcp>/build/index.js

Notes:

• If you are using nvm and the default node is not the desired version, specify the full path to the node binary in your config: "command": "/Users/<user>/.nvm/versions/node/<version>/bin/node", "args": ["<path/to/ashra-mcp>/build/index.js"]
• The ASHRA_API_KEY must be kept secret and provided wherever the server runs.

Tips and common issues:

• Ensure the path in args points to the built index.js of the Ashra MCP project.
• The ASHRA_API_KEY must be valid for Ashra; an invalid key will cause request failures.
• If Claude cannot reach the MCP server, verify network access and that the server process is running and listening on the expected port.
• Keep dependencies up to date by periodically running yarn install and yarn build.
• If using a containerized environment, translate the mcp_config into the corresponding container startup command and pass ASHRA_API_KEY as an environment variable.