Concise MCP server exposing tools to quickly discover routes, inspect endpoint params, and view example responses.

• list_routes: Return all available route paths.
• search_routes: Robust search over routes (tokenized, fuzzy-ish substring, and synonyms like "planet details", "mahadasha").
• check_endpoint: Show URL, method, and parameter schema (types, samples, options).
• check_response: Show example response JSON for a route.

It's simple: Just save this repo locally and point to it in your MCP client config.

Clone or download this repository to any location on your machine:

git clone <repo-url>
cd documentation-MCP

Or simply download and extract it to a folder.

npm install
npm run build

This creates the build/ directory with the compiled server.

Add this to your Claude Desktop config file:

MacOS: ~/Library/Application Support/Claude/claude_desktop_config.json
Windows: %APPDATA%\Claude\claude_desktop_config.json

{
  "mcpServers": {
    "vedicastroapi-documentation": {
      "command": "node",
      "args": [
        "/absolute/path/to/documentation-MCP/build/index.js"
      ]
    }
  }
}

Important: Replace /absolute/path/to/documentation-MCP with the actual absolute path where you saved the repo.

Restart Claude Desktop (or your MCP client) to load the server.

• Look for the MCP connection indicator in your client.
• You should see tools like list_routes, search_routes, check_endpoint, check_response available.

Try these prompts:

• "List all routes"
• "Find routes for planet details"
• "Params for /prediction/daily-sun"
• "Response for /horoscope/planet-details"

• Ensure the absolute path in your config is correct.
• Confirm build/index.js exists after building.
• Reinstall and rebuild if needed:

rm -rf build node_modules
npm install
npm run build

• list routes: "List all routes"
• search routes: "Find routes for planet details", "Search mahadasha routes"
• endpoint params: "Params for /prediction/daily-sun"
• example response: "Response for /horoscope/planet-details"

# Watch mode for development
npm run watch

# Build for production
npm run build

• After npm install, run npm run build to compile TypeScript into build/.
• You should see build/index.js and tool files under build/tools/.

documentation-MCP/
├── src/
│   ├── index.ts           # Server entry
│   ├── types.ts           # Shared types
│   ├── global.d.ts        # Decls for .cjs data
│   └── tools/
│       ├── searchRoutes.ts      # search_routes (tokenized + synonyms)
│       ├── checkEndpoint.ts     # check_endpoint
│       └── checkResponse.ts     # check_response
├── routes.cjs             # List of all API routes
├── endpoints_new_copy.cjs # Endpoint details with parameters
├── url_responses_by_category.cjs  # Response examples
├── build/                 # Compiled JavaScript (generated by tsc)
├── package.json
├── tsconfig.json
└── README.md

• Route search supports synonyms (e.g., "planet details" → horoscope planet endpoints; "mahadasha" → dashas endpoints).
• If search returns nothing, try a simpler keyword; you can always run list_routes to scan the full list.
• ⚠️ Important — AI can make mistakes: Ask it to use these tools to hit the API, inspect real responses, and then make edits based on what it sees. You should still review the changes.

See docs/IDE_INTEGRATIONS.md for steps to connect this MCP server in VS Code, Cursor, PhpStorm, Zed, and Neovim.

• routes.cjs - Route list
• endpoints_new_copy.cjs - Endpoint parameters
• url_responses_by_category.cjs - Response examples

MIT

• Model Context Protocol Documentation
• MCP Weather Server Example
• Vedic Astro API