holaspirit-mcp-server

A MCP(Model Context Protocol) server that accesses to Holaspirit API.

This server provides MCP-compatible access to Holaspirit's API, allowing AI assistants to interact with your Holaspirit data through a standardized interface.

Features

Available tools:

• holaspirit_list_tasks - List all tasks in the organization

• holaspirit_list_metrics - List all metrics in the organization

• holaspirit_list_circles - List all circles in the organization

• holaspirit_get_circle - Get details of a specific circle

• holaspirit_list_roles - List all roles in the organization

• holaspirit_get_role - Get details of a specific role

• holaspirit_list_domains - List all domains in the organization

• holaspirit_list_policies - List all policies in the organization

• holaspirit_list_meetings - List all meetings in the organization

• holaspirit_get_meeting - Get details of a specific meeting

• holaspirit_get_member_feed - Get member feed

• holaspirit_get_tensions - Get tensions for a meeting or meetings

• holaspirit_search_member - Search for a member by email

Related MCP server: Mail MCP Tool

Quick Start

Installation

Installing via Smithery

To install holaspirit-mcp-server for Claude Desktop automatically via Smithery:

Manual Installation

Configuration

You can configure the server using environment variables. Two methods are supported:

Environment Variables

• HOLASPIRIT_API_TOKEN: Your Holaspirit API token

• HOLASPIRIT_ORGANIZATION_ID: Your Holaspirit organization ID

Using .env File

Create a .env file in the project root:

Then edit .env with your actual values:

Usage

The server supports two transport modes:

Stdio Transport (Default)

For use with MCP clients that communicate via stdin/stdout:

HTTP Transport

For use with web clients or HTTP-based integrations using the latest Streamable HTTP protocol:

The HTTP server accepts POST requests only on any path (e.g., /, /mcp, /sse) and uses the Streamable HTTP transport protocol.

Edit MCP configuration json for your client:

For stdio transport:

For HTTP transport, configure your client to connect to:

• http://localhost:3000/ (or any path)

Development

Available Scripts

• npm run dev - Start the server in development mode with hot reloading

• npm run build - Build the project for production

• npm run start - Start the production server

• npm run lint - Run linting checks (ESLint and Prettier)

• npm run fix - Automatically fix linting issues

• npm run examples - Run the example scripts

Contributing

1. Fork the repository

2. Create your feature branch

3. Run tests and linting: npm run lint

4. Commit your changes

5. Push to the branch

6. Create a Pull Request