​
Overview

Projects in MCPcat are the top-level organizational unit for your MCP server analytics. Each project represents a distinct MCP server or deployment that you want to track and analyze separately.

​
What is a Project

A project is identified by a unique project ID (like proj_abc123xyz) that you use when initializing MCPcat tracking in your server. This ID links all analytics data from your MCP server to a specific project in your MCPcat dashboard. Projects allow you to:
  • Separate analytics for different MCP servers
  • Manage access control and team permissions
  • Configure project-specific settings and preferences
  • Compare usage patterns across different tools or deployments

​
Project Organization

Projects help you organize your MCP ecosystem in meaningful ways:

​
By server type

  • Create separate projects for different MCP servers (e.g., database tools, file system tools, API integrations)
  • Track each server’s unique usage patterns and requirements

​
By environment

  • Separate development, staging, and production deployments
  • Monitor real user behavior without mixing test data

​
By customer or team

  • Create projects for different customer deployments
  • Track usage by internal teams or departments

​
Project Analytics

Each project maintains its own:
  • Session history and user activity
  • Usage metrics and trends
  • Error tracking and debugging information
  • User identification and segmentation
  • Custom event tracking

​
Best Practices

When organizing your projects:
  • Use descriptive names that clearly identify the MCP server or deployment
  • Keep production and development environments in separate projects
  • Use consistent naming conventions across your organization
Projects provide the foundation for organizing and understanding your MCP server analytics, ensuring you can track, compare, and optimize each part of your MCP ecosystem effectively.