> ## Documentation Index
> Fetch the complete documentation index at: https://docs.bedrock.cv/llms.txt
> Use this file to discover all available pages before exploring further.

# MCP Server

> Give AI agents direct access to the Drawing Index.

## What is MCP?

The [Model Context Protocol](https://modelcontextprotocol.io) (MCP) is an open standard for connecting AI agents to external data sources and tools. Instead of pasting data into prompts, MCP lets agents call structured tools to query, retrieve, and act on data in real time. Claude, ChatGPT, Microsoft Copilot, and any MCP-compatible client can connect to an MCP server and use its tools as part of their reasoning.

## Why MCP for drawings?

LLMs can reason about construction drawings -- cross-referencing schedules, checking code compliance, coordinating across disciplines -- but they need structured access to the parsed data. Raw PDFs are too large and too dense for a single prompt. A 200-page drawing set contains thousands of cross-references that span sheets and disciplines.

The Drawing Index MCP gives agents composable query tools to traverse the knowledge graph interactively. The agent decides what to look up, when to drill deeper, and how to combine results. Bedrock provides the data; the agent provides the reasoning.

## Design Principles

<CardGroup cols={2}>
  <Card title="Composable Primitives" icon="puzzle-piece">
    Each tool does one thing. The agent chains them to accomplish complex workflows like code compliance checks or RFI drafting. The MCP never imposes a workflow the agent can't deviate from.
  </Card>

  <Card title="Context-Rich Responses" icon="layer-group">
    Every entity includes parent context. A feature comes with its block type and sheet number. A block comes with its sheet and drawing. No extra calls just to get human-readable context.
  </Card>

  <Card title="Progressive Disclosure" icon="eye">
    List operations return lightweight summaries by default. Heavy data (OCR text, schedule metadata, overlay changes) is gated behind `include` parameters. The agent pays the token cost only when it needs detail.
  </Card>

  <Card title="Explicit Async Boundary" icon="clock">
    Vision processing is async. The `Compare` tool returns a `job_id`. A separate `PollJob` tool polls status. Tools never block -- the agent decides when and how often to poll.
  </Card>

  <Card title="Pass-Through Filters" icon="filter">
    Filters reference parent entities directly. The `Query` tool accepts pass-through filters like `sheet_number`, `block_type`, and `block_identifier` that join through parent entities. This avoids the "resolve then query" round-trip pattern.
  </Card>

  <Card title="Flat Tool Surface" icon="grid-2">
    Seven tools total. No nested namespaces, no tool discovery step. Every MCP-compatible agent sees all tools immediately on connection.
  </Card>
</CardGroup>

## Tools

Seven tools organized in four categories:

| Tool                                | Category | Description                        |
| ----------------------------------- | -------- | ---------------------------------- |
| [`Query`](/mcp/tools/query)         | Data     | Get, list, or filter any entity    |
| [`Search`](/mcp/tools/search)       | Data     | Hybrid semantic + keyword search   |
| [`Ask`](/mcp/tools/ask)             | Data     | Natural language Q\&A with sources |
| [`Compare`](/mcp/tools/compare)     | Vision   | Async drawing comparison           |
| [`Parse`](/mcp/tools/parse)         | Vision   | Async feature extraction           |
| [`PollJob`](/mcp/tools/get-job)     | Async    | Poll job status and results        |
| [`ViewImage`](/mcp/tools/get-image) | Content  | Storage URI to signed URL          |

<Info>
  Across 9 reference workflows, agents average **2.2 tool calls** per task. The pass-through filters and context-rich responses keep round-trips low.
</Info>

## Next Steps

<CardGroup cols={2}>
  <Card title="Setup" icon="plug" href="/mcp/setup">
    Connect the Bedrock MCP server to Claude, ChatGPT, Microsoft Copilot, or your custom agent.
  </Card>

  <Card title="Tools Reference" icon="wrench" href="/mcp/tools/query">
    Full parameter and response documentation for all seven tools.
  </Card>

  <Card title="Workflow Examples" icon="route" href="/mcp/workflows/symbol-counting">
    Step-by-step tool call sequences for real construction queries.
  </Card>

  <Card title="Best Practices" icon="lightbulb" href="/mcp/best-practices">
    Prompt tips, context management, and error handling.
  </Card>
</CardGroup>