Holaspirit MCP Server

A MCP(Model Context Protocol) server that accesses to Holaspirit API. The holaspirit mcp server wraps that behind the Model Context Protocol, so an assistant can use it through 4 defined tools rather than through you.

What it actually does

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

• 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

Its toolset

Everything the assistant can do here goes through one of these:

• Installation — The Installation tool exposed by this server
• Configuration — You can configure the server using environment variables. Two methods are supported:
• Usage — The Usage tool exposed by this server
• 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

Configuration

You will need 2 environment variables: HOLASPIRIT_API_TOKEN, HOLASPIRIT_ORGANIZATION_ID. The server will not start without them, which is usually why the tools fail to appear on a first run. Keep credentials in your client's env block or a secrets manager rather than in a file you might commit.

Adding it to your client

The server ships on npm as @smithery/cli, so your MCP client can launch it on demand — there is no separate build step. Add the server block to your client's configuration, restart it, and the tools register themselves.

When to reach for it

Among the developer tooling options, the useful question is rarely "what can it do" but "what does it cost you to run" — permissions, credentials, and how much of your context its toolset consumes. Holaspirit's toolset — Installation, Configuration, Usage and 1 more — is a fair guide to whether it matches your workflow. It is maintained by syucream; worth a glance at recent repository activity before you build anything load-bearing on it.

This entry was verified against Holaspirit's own documentation before publication; SyncDev keeps the directory reviewed rather than auto-generated.

Caveats

• It runs with your machine's permissions. That is convenient and also the reason to think about what you point it at before you approve a tool call.
• Missing credentials fail quietly in some clients — if no tools show up, check the environment block first.
• MCP clients confirm each tool call by default. Leave that on until you have watched what the holaspirit mcp server does with a few real requests.