Provides analytics tracking for MCP server operations and tool usage monitoring
Click on "Install Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@System Initiativeshow me the current state of our production Kubernetes cluster"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
System Initiative MCP Server
A Model Context Protocol (MCP) server that provides Claude Code with direct access to System Initiative's API for managing infrastructure components, change sets, schemas, and actions.
Development Setup
Environment Variables
Required:
export SI_API_TOKEN="your-token-here"
export SI_BASE_URL="http://localhost:5380" # Defaults to production if not overriddenOptional analytics configuration:
export POSTHOG_API_KEY="dev-posthog-key" # Override if you want to use the Dev Project to test tracking changesTesting with MCP Inspector
The MCP Inspector provides a web interface for testing tools and debugging:
# Start the inspector
deno task inspectorThis opens a browser interface where you can:
Test individual tools with parameters
Inspect tool schemas and validate responses
Debug authentication and connection issues
View real-time tool execution
Testing with Claude Code
Configure Claude Code to use your local server (without running in a container):
# From the repository root
claude mcp add si-mcp-server-dev -- deno run --allow-env --allow-net bin/si-mcp-server/main.ts stdio
# Or from within si-mcp-server directory
claude mcp add si-mcp-server-dev -- deno run --allow-env --allow-net main.ts stdio
# Verify it's working
claude mcp listRelated MCP server: SlopWatch MCP Server
Available Tasks
Task | Command | Description |
|
| Run with auto-reload for development |
|
| Start MCP Inspector for testing |
|
| Compile to standalone binary |
|
| Build Docker image |
|
| Run Docker container |
Adding New Tools
Create tool file in
src/tools/Import required dependencies and
withAnalyticsfromcommonBehavior.tsDefine Zod schemas for input/output validation
Wrap handler with
withAnalytics(toolName, async () => { ... })Export tool registration function
Register in
src/server.ts