Holaspirit Mcp Server

What is Holaspirit Mcp Server about?

A server that bridges the Holaspirit organization management platform with the Model Context Protocol (MCP), exposing Holaspirit's REST endpoints as MCP tools. AI assistants can call these tools to list tasks, retrieve circles, roles, meetings, policies, and more, all through a unified MCP interface.

How to use Holaspirit Mcp Server?

1. Installation

   npm install holaspirit-mcp-server
   

   Or install on‑the‑fly with npx (preferred):

   npx holaspirit-mcp-server
   

2. Configuration – set the required environment variables either directly or in a .env file:

   HOLASPIRIT_API_TOKEN=your_api_token
   HOLASPIRIT_ORGANIZATION_ID=your_org_id
   

3. Running
   • STDIO (default) for MCP clients that communicate via stdin/stdout:

     npx holaspirit-mcp-server
     

   • HTTP for web or HTTP‑based clients (e.g., Streamable HTTP protocol):

     npx holaspirit-mcp-server --port 3000
     

   The HTTP server accepts POST requests on any path.
4. Client configuration – add a server entry to the MCP client JSON:

   {
     "holaspirit": {
       "command": "npx",
       "args": ["holaspirit-mcp-server"],
       "env": {
         "HOLASPIRIT_API_TOKEN": "<your token>",
         "HOLASPIRIT_ORGANIZATION_ID": "<your org id>"
       }
     }
   }
   

Key features of Holaspirit Mcp Server

• Task Management – holaspirit_list_tasks
• Metrics Access – holaspirit_list_metrics
• Organizational Structure – list and retrieve circles, roles, domains, policies
• Meeting Tools – list meetings, get meeting details, fetch tensions, member feed
• Member Search – lookup members by email
• Two transport modes – STDIO and HTTP (Streamable HTTP)
• Hot‑reloading development mode via npm run dev
• Linting, building, and example scripts for easy contribution

Use cases of Holaspirit Mcp Server

• AI‑driven project assistants that can query upcoming tasks, assign work, or report metrics without writing custom API calls.
• Automated meeting summarizers that pull meeting details, tensions, and member feeds to generate concise briefings.
• Organizational audits where an AI agent extracts role hierarchies, circles, and policies for compliance checks.
• Custom dashboards built on top of MCP that visualize Holaspirit data in real‑time.
• Chatbot integrations enabling conversational queries like “What are the pending tasks for this week?”

FAQ from the Holaspirit Mcp Server

Q: Do I need a Holaspirit account to use this server? A: Yes, you need a valid Holaspirit API token and the organization ID for the target workspace.

Q: Can I run the server behind a firewall? A: Absolutely. When using the HTTP mode, you can bind to any host/port and configure your network rules accordingly.

Q: Which transport should I choose? A: Use STDIO for local MCP clients (e.g., Claude Desktop). Choose HTTP when integrating with web services or remote agents.

Q: How do I update the server? A: Run npm update holaspirit-mcp-server or simply reinstall with npx holaspirit-mcp-server to fetch the latest version.

Q: Is there support for custom Holaspirit endpoints? A: Currently the server exposes a fixed set of tools. You can fork the repository and add new tool definitions following the existing pattern.

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

Quick Start

Installation

Installing via Smithery

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

npx -y @smithery/cli install holaspirit-mcp-server --client claude

Manual Installation

npm install holaspirit-mcp-server

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:

# Copy the example file
cp .env.example .env

Then edit .env with your actual values:

HOLASPIRIT_API_TOKEN=your_api_token_here
HOLASPIRIT_ORGANIZATION_ID=your_organization_id_here

Usage

The server supports two transport modes:

Stdio Transport (Default)

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

npx holaspirit-mcp-server

HTTP Transport

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

npx holaspirit-mcp-server --port 3000

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:

...
    "holaspirit": {
      "command": "npx",
      "args": [
        "-y",
        "holaspirit-mcp-server"
      ],
      "env": {
        "HOLASPIRIT_API_TOKEN": "<your token>",
        "HOLASPIRIT_ORGANIZATION_ID": "<your org id>"
      }
    },
...

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