indiekit-mcp
OfficialServer Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| pg_inspect_schemaA | Inspect PostgreSQL database schema — tables, columns, types, indexes, constraints, enums, and extensions |
| pg_diff_schemas | Compare two PostgreSQL databases and return migration SQL |
| pg_diff_summary | Compare two PostgreSQL databases and return a human-readable summary of differences |
| pg_top_activity | Get current PostgreSQL activity from pg_stat_activity |
| pg_top_stats | Get database statistics (connections, cache hit ratio, TPS) |
| pg_top_locks | Get current lock information from pg_locks |
| throttled_check_rate | Check if a key is rate limited using configurable algorithms (token-bucket, leaky-bucket, fixed-window, sliding-window, gcra) |
| throttled_get_status | Get current rate limit state for a key without consuming quota |
| just_list_recipes | List all recipes defined in a justfile |
| just_run_recipe | Execute a recipe from a justfile |
| just_parse_justfile | Parse a justfile and return the AST |
| lipgloss_style_render | Render styled terminal text with colors, bold, italic, borders, padding, margin, alignment |
| lipgloss_join_horizontal | Join multiple text blocks horizontally |
| lipgloss_join_vertical | Join multiple text blocks vertically |
| env_audit_scan | Scan a project directory for environment variables used in code |
| llm_context_scan | Scan files/directories and count tokens for LLM context window estimation |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 1 tool
With only one tool, there is no risk of confusion between tools. The tool's purpose of inspecting PostgreSQL schema is clearly stated and distinct.
The single tool name 'pg_inspect_schema' follows a clear and consistent pattern (verb_noun) and is descriptive, so no inconsistency issues arise.
Only one tool is provided, which is below the typical well-scoped range of 3-15. While the tool itself is comprehensive, the server's scope feels very narrow, making it borderline appropriate.
The tool covers all major aspects of database schema inspection (tables, columns, types, indexes, constraints, enums, extensions), leaving no obvious gaps for its stated purpose.