get_indicator_metadata — Development Indicators MCP MCP Tool Read-only
get_indicator_metadata
(get indicator metadata) is one of 10 tools on the
Development Indicators MCP
MCP server. Connect the server and your client discovers it on the handshake.
by client
How to call get_indicator_metadata from your client
- Claude Code Development Indicators MCP get_indicator_metadata run in your project directory
- Claude Desktop Development Indicators MCP get_indicator_metadata ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor Development Indicators MCP get_indicator_metadata ~/.cursor/mcp.json
- VS Code Development Indicators MCP get_indicator_metadata .vscode/mcp.json
- Zed Development Indicators MCP get_indicator_metadata ~/.config/zed/settings.json
- Windsurf Development Indicators MCP get_indicator_metadata ~/.codeium/windsurf/mcp_config.json
- Cline Development Indicators MCP get_indicator_metadata ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI Development Indicators MCP get_indicator_metadata ~/.gemini/settings.json
- Grok Development Indicators MCP get_indicator_metadata .mcp.json (in your project root)
- ChatGPT Development Indicators MCP get_indicator_metadata Settings → Connectors → Advanced → Developer mode
- Claude.ai Development Indicators MCP get_indicator_metadata Settings → Connectors → Add custom connector
- LangChain Development Indicators MCP get_indicator_metadata pip install langchain-mcp-adapters
Fastest route
claude mcp add --transport http development-indicators https://indicatorsmcp.impactengines.ai/mcpOther tools on this server
This list was read from the server itself, by connecting to it and calling tools/list on 1 October 2026. It is what
the server actually exposes, not what its listing claims.
Mutating and Read-only are read off each tool's name, not its schema — a hint, not a guarantee. The registry stores tool names only; connect the server for its live schemas.