github-repo-shape — Think Steps MCP Tool
github-repo-shape
(github repo shape) is one of 30 tools on the
Think Steps
MCP server. Connect the server and your client discovers it on the handshake.
by client
How to call github-repo-shape from your client
- Claude Code Think Steps github-repo-shape run in your project directory
- Claude Desktop Think Steps github-repo-shape ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor Think Steps github-repo-shape ~/.cursor/mcp.json
- VS Code Think Steps github-repo-shape .vscode/mcp.json
- Zed Think Steps github-repo-shape ~/.config/zed/settings.json
- Windsurf Think Steps github-repo-shape ~/.codeium/windsurf/mcp_config.json
- Cline Think Steps github-repo-shape ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI Think Steps github-repo-shape ~/.gemini/settings.json
- Grok Think Steps github-repo-shape .mcp.json (in your project root)
- ChatGPT Think Steps github-repo-shape Settings → Connectors → Advanced → Developer mode
- Claude.ai Think Steps github-repo-shape Settings → Connectors → Add custom connector
- LangChain Think Steps github-repo-shape pip install langchain-mcp-adapters
Fastest route
claude mcp add --transport http think-steps https://agent-observatory-sensor.nolimit-observatory.workers.dev/s/think-steps/mcp
Other tools on this server
- think-steps
- utc-time
- timezone
- validate-json
- normalize-url
- inspect-robots
- domain-shape
- citation
- compatibility
- status-catalog
- iana-zones
- web-fetch
- fetch-status
- weather-hint
- memory-key-count
- file-path-ok
- browser-url-ok
- search-query-len
- hn-front-count
- lib-docs-hint
- playwright-url-ok
- figma-url-shape
- jira-key-shape
- geo-hint
- calc-eval
- wiki-title-ok
- agent-tool-index
- people-search-index
- agent-ads-index
This list was read from the server itself, by connecting to it and calling tools/list on 24 September 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.