list_pricing_plans — Vila Mariana MCP Tool Read-only
list_pricing_plans
(list pricing plans) is one of 28 tools on the
Vila Mariana
MCP server. Connect the server and your client discovers it on the handshake.
by client
How to call list_pricing_plans from your client
- Claude Code Vila Mariana list_pricing_plans run in your project directory
- Claude Desktop Vila Mariana list_pricing_plans ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor Vila Mariana list_pricing_plans ~/.cursor/mcp.json
- VS Code Vila Mariana list_pricing_plans .vscode/mcp.json
- Zed Vila Mariana list_pricing_plans ~/.config/zed/settings.json
- Windsurf Vila Mariana list_pricing_plans ~/.codeium/windsurf/mcp_config.json
- Cline Vila Mariana list_pricing_plans ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI Vila Mariana list_pricing_plans ~/.gemini/settings.json
- Grok Vila Mariana list_pricing_plans .mcp.json (in your project root)
- ChatGPT Vila Mariana list_pricing_plans Settings → Connectors → Advanced → Developer mode
- Claude.ai Vila Mariana list_pricing_plans Settings → Connectors → Add custom connector
- LangChain Vila Mariana list_pricing_plans pip install langchain-mcp-adapters
Fastest route
claude mcp add --transport http vilamariana-sampa-br https://vilamariana.sampa.br/mcpOther tools on this server
- get_site_info
- list_categories
- search_places
- get_place
- list_events
- list_guides
- list_booking_services
- get_availability
- create_booking
- reserve_event_tickets
- request_reservation
- rsvp_event
- get_event_tickets
- list_products
- create_checkout
- get_restaurant_menus
- search_dishes
- get_reviews
- list_blog_posts
- list_faqs
- list_forms
- submit_form
- get_loyalty_info
- list_offers
- list_profiles
- list_movies
- get_showtimes
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.