Plugin de Estatísticas de Uso de IA
@tarcisiojr
About Plugin de Estatísticas de Uso de IA
Servidor MPC para capturar estatísticas de uso de AI Code Assist
Config
No standard config provided
This server doesn't expose a parseable MCP config block in its README. See the repository for install instructions.
RepositoryTools
No tools detected
We auto-extract tools from the README. The maintainer can list them under a ## Tools heading to populate this section.
Overview
What is Plugin de Estatísticas de Uso de IA?
Plugin de Estatísticas de Uso de IA collects and submits statistics about AI assistant usage, such as data volume, code changes, developer name, Git repository, lines changed, and programming language. It integrates with a server for analysis and is intended for developers tracking AI-assisted work.
How to use Plugin de Estatísticas de Uso de IA?
Configure the plugin in cline_mcp_settings.json. Build it by running npm install then npm run build in the plugin directory. The compiled JavaScript is output to ai-usage-stats/build/index.js.
Key features of Plugin de Estatísticas de Uso de IA
- Monitors AI assistant interactions
- Records data volume and code changes
- Tracks developer name and Git repository
- Logs lines generated, altered, or removed
- Detects programming language used
- Submits statistics to a server for analysis
Use cases of Plugin de Estatísticas de Uso de IA
- Monitor how much code AI assistants generate per developer
- Track changes in specific Git repositories from AI usage
- Analyze programming language trends in AI-assisted development
- Measure productivity impact of AI tools over time
FAQ from Plugin de Estatísticas de Uso de IA
What data does the plugin collect?
It collects data volume, code generated/changed/removed, developer name, associated Git repository, number of lines, and programming language.
What are the dependencies for building the plugin?
Node.js and npm are required. Run npm install to install dependencies, then npm run build to compile TypeScript to JavaScript.
How is the plugin configured?
Configuration is done through the cline_mcp_settings.json file, with options for command, args, env, disabled, and autoApprove.
Can I extend the plugin?
Yes, you can modify the source code in ai-usage-stats/src/index.ts to add support for new languages, collect additional metrics, or integrate with different analysis servers.
Where does the collected
Frequently asked questions
What data does the plugin collect?
It collects data volume, code generated/changed/removed, developer name, associated Git repository, number of lines, and programming language.
What are the dependencies for building the plugin?
Node.js and npm are required. Run `npm install` to install dependencies, then `npm run build` to compile TypeScript to JavaScript.
How is the plugin configured?
Configuration is done through the `cline_mcp_settings.json` file, with options for command, args, env, disabled, and autoApprove.
Can I extend the plugin?
Yes, you can modify the source code in `ai-usage-stats/src/index.ts` to add support for new languages, collect additional metrics, or integrate with different analysis servers.
Basic information
More Developer Tools MCP servers
Serena
oraiosA powerful MCP toolkit for coding, providing semantic retrieval and editing capabilities - the IDE for your agent

Moxie Docs
Jackalope-DevAutomated codebase documentation for GitHub: searchable docs, MCP context for AI agents, doc drift detection, and Friday Cleanup PRs.

TaskerArmy Agent
TaskerArmyAsk Claude or ChatGPT what Shopify theme optimization tasks are pending on your store, a remote MCP server for TaskerArmy Agent accounts.
Vibgrate MCP
VibgrateQuery your team's drift, vulnerability, and migration data from any AI assistant. Vibgrate MCP connects Cursor, Claude, ChatGPT, Windsurf, or VS Code to Vibgrate Cloud: 51 tools for DriftScores, CVEs and EOL runtimes, up
OpenSumi
opensumiA framework helps you quickly build AI Native IDE products. MCP Client, supports Model Context Protocol (MCP) tools via MCP server.
Comments