"Spine" matching MCP tools:

• list_docs

  Pine Script

  List all available Pine Script v6 documentation files with descriptions. Returns files organised by category with descriptions. For small files use get_doc(path). For large files (ta.md, strategy.md, collections.md, drawing.md, general.md) use list_sections(path) then get_section(path, header).

  Connector

• get_doc

  Pine Script

  Read a specific Pine Script v6 documentation file. For large files (ta.md, strategy.md, collections.md, drawing.md, general.md) prefer list_sections() + get_section() to avoid loading 1000-2800 line files into context.

  Connector

• deals

  connect

  Deals — the transactional spine tracking a work changing hands. action "list": deals you can see (owner/seller/buyer/intermediary), filter by state/work_id/direction — read-only. action "get": deal detail incl. linked records (RAI requests, consignment requests, shared views, sales, provenance, custody) — read-only; needs deal_id. action "create": manual deal creation (most deals auto-create from purchase requests / consignment approvals) — write; present a summary + confirm first. action "update_state": advance (proposed→negotiating→agreed→closed_won|closed_lost) or close — write; close_reason required for closed_lost; present the transition + confirm first.

  Connector

• resolve_topic

  Pine Script

  Fast lookup for exact Pine Script API terms and known concepts. Use for exact function names and Pine Script vocabulary (e.g., "ta.rsi", "strategy.entry", "repainting", "request.security"). For natural language questions, read the docs://manifest resource for routing guidance, then use get_doc() or list_sections() + get_section().

  Connector

• get_prompt

  Pine Script

  Get a prompt by name with optional arguments. Returns the rendered prompt as JSON with a messages array. Arguments should be provided as a dict mapping argument names to values.

  Connector

• get_functions

  Pine Script

  Get valid Pine Script v6 functions, optionally filtered by namespace. Use before writing Pine Script to see which functions exist. For checking a single function name, use validate_function() instead.

  Connector

• get_section

  Pine Script

  Get a specific section from a documentation file by its header. Use after list_sections() shows available headers, or after resolve_topic() / search_docs() identifies the relevant file.

  Connector

• list_corridors

  Zoning Signal

  List every published corridor page. A corridor is the cross-municipal economic-topology view — the cross-jurisdiction read on a shared infrastructure spine, aquifer, or commercial gravity field. Returns name, slug, constituent cities, primary axis, and URL.

  Connector

• search_docs

  Pine Script

  Search Pine Script v6 documentation and return matching sections. Finds sections containing the query and returns previews with get_section() call hints so you can read the full content. Multi-word queries use AND logic: all terms must appear in the section (not necessarily on the same line).

  Connector

• list_sections

  Pine Script

  List all section headers in a doc file. Use before get_section() to find the right header. Especially useful for large files like ta.md, strategy.md, collections.md, drawing.md, general.md which have 50-115 sections each.

  Connector

• doxa_encourage

  Doxa MCP

  Generate Doxa-voice encouragement for a user's situation. Returns a short screenshot-shareable response with scripture references, anchored in The Doxa Way — a 9-movement spine pointing toward the next mile, not the next step.

  Connector

• validate_function

  Pine Script

  Check if a Pine Script v6 function name is valid.

  Connector

• list_prompts

  Pine Script

  List all available prompts. Returns JSON with prompt metadata including name, description, and optional arguments.

  Connector