# nitur [Health: Active]

**Category:** 💻 Developer Tools  
**Repository:** https://nitur.dev  
**Views:** 1  
**Installs:** 0  
**Upvotes:** 0  
**Directory Page:** https://allmcps.com/mcp/nitur

## Description
Create projects and read their web analytics: views, referrers, countries, custom events.

## Claude Desktop Quick Installation
No confirmed install details yet, so no config is published. Follow the setup steps in the repository above.

## Documentation

## What the nitur MCP server does

The nitur MCP server provides two documented areas of functionality: project creation and web analytics access. It is intended for an AI agent that needs to work with projects in nitur.dev and retrieve website measurement data through the Model Context Protocol.

The available description identifies four analytics areas: views, referrers, countries, and custom events. These cover basic traffic volume, the sources sending visitors, geographic distribution, and application-defined events. The material does not describe filtering, date ranges, aggregation options, event creation, or export behavior, so those capabilities should not be assumed.

## Tools and capabilities

The nitur MCP server is documented as supporting the following operations:

- Create projects.
- Read view data.
- Read referrer data.
- Read country data.
- Read custom-event data.

The listing does not provide the individual MCP tool names, argument schemas, return formats, or required identifiers. Developers should inspect the server's current documentation before building prompts or tool calls around specific parameters.

For an agent workflow, the stated fit is straightforward: create or select a project, then retrieve the available web analytics for that project. The source material does not establish whether project creation and analytics access require separate permissions or whether analytics are available immediately after creation.

## Limitations and notes

The README is unavailable, and the supplied listing contains no installation instructions. It does not state whether the nitur MCP server uses stdio, streamable HTTP, or another transport, and it does not document authentication, environment variables, configuration files, endpoint details, or client-specific setup.

Client compatibility is also unspecified. No supported client names are provided, so compatibility with Claude Desktop, Cursor, Cline, Windsurf, or other MCP clients cannot be confirmed from the available material. The same applies to licensing: no license information is included.

The nitur MCP server should therefore be evaluated first against the concrete requirement to create projects and read the four named analytics categories. Confirm the connection method, credentials, tool schemas, and supported clients from nitur.dev before implementation. Avoid relying on undocumented features such as writing events, modifying existing projects, applying advanced reports, or exporting data.

_Full upstream README: https://allmcps.com/mcp/nitur/readme_