Holaspirit

You run a MCP server that provides a standardized interface to Holaspirit data, letting AI assistants perform tasks, read data, and interact with your organization’s circles, meetings, and members through simple commands.

How to use

You connect your MCP client to the holaspirit MCP server to perform actions like listing tasks, circles, roles, meetings, and more. Choose the transport mode that fits your workflow. Use stdio when your client communicates over stdin/stdout, or use HTTP when you want to interact through a web-friendly API surface. The server translates your requests into Holaspirit API calls and returns structured results that your assistant can reason about.

Common usage patterns include listing core data (tasks, circles, roles, domains), retrieving details for a specific circle or meeting, and searching for members by email. You can combine multiple actions into a session with an MCP client to build workflows, automations, or conversational assistants that navigate your Holaspirit data.

How to install

Prerequisites: you need Node.js and npm installed on your system. Make sure you have a valid Holaspirit API token and your organization ID ready, as you will configure the server with these values.

Install the server package using npm or run it directly with npx. You can also run it in a development mode during testing.

Configuration and usage notes

Two transport modes are supported. The stdio transport runs the MCP server locally and communicates via stdin/stdout. The HTTP transport exposes an HTTP endpoint that accepts POST requests on any path and uses the Streamable HTTP protocol.

Environment variables you need to configure are the Holaspirit API token and your organization ID. These values authenticate requests to Holaspirit and scope data to your organization.

Security considerations

Treat your API token like a password. Store it securely in an environment file or secret manager, and ensure it is not committed to code repositories. When using HTTP transport, restrict access to trusted clients and consider routing through a gateway that enforces proper authentication.

Troubleshooting

If you encounter connection issues, verify that the API token and organization ID are correct, and ensure the Holaspirit service is reachable from your environment. Check that the MCP server is running on the expected port for HTTP transport, and review logs for any authentication errors or rate limiting from the Holaspirit API.

Examples of common actions

List all tasks in your organization, retrieve details for a specific circle, or fetch the member feed. The server exposes a clear set of endpoints that map directly to these activities.

Tools and endpoints (capabilities)

The MCP server provides a set of endpoints to list and get details for tasks, metrics, circles, roles, domains, policies, meetings, and member-related data. You can search for a member by email and retrieve tensions for a meeting or meetings.

Starting the server in stdio mode

npx holaspirit-mcp-server

Starting the server in HTTP mode

npx holaspirit-mcp-server --port 3000

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