# MCP-Assisted Development

{% hint style="info" %}
💬 **Need help?** If you're stuck, ask Eva on ATRIP for instant diagnostics.

<a href="https://www.atriptech.com/" class="button primary" data-icon="comments">Ask Eva</a>
{% endhint %}

Use GitBook MCP to speed up Atlas API development.

It helps you find the right pages, understand the flow, and narrow down the next step faster.

### When to use MCP

Use MCP when you need to:

* find the correct API flow for a task
* understand which identifier is needed next
* compare similar APIs such as `search.do` and `getOffer.do`
* locate the right troubleshooting page for an error
* move faster in sandbox without guessing

### What MCP is best at

MCP works best as a docs assistant during development.

Use it to:

* map the booking flow from `Search` to `Pay`
* identify which page explains a field or status
* find related guides for webhooks, refunds, or utility APIs
* narrow down which page to open before coding

### Recommended Atlas use cases

#### Start a sandbox build

Ask MCP to outline the minimum sandbox flow.

Then validate against these pages:

* [Sandbox Development](/api-document/readme/quick-start/sandbox-development.md)
* [Booking Overview](/api-document/readme/booking-overview.md)
* [API Reference](/api-document/api-reference.md)

#### Move through the booking flow

Use MCP to confirm the next step after each successful call.

Typical sequence:

* `Search` → keep `routingIdentifier`
* `Verify` → keep `sessionId`
* `Create Order` → keep `orderNo`
* `Payment & Ticketing` → poll and confirm final status

#### Troubleshoot faster

Use MCP to route errors to the right troubleshooting section.

Good starting points:

* [Error Codes](/api-document/troubleshooting-and-support/errors-handing.md)
* [FAQs](/api-document/troubleshooting-and-support/faqs.md)
* [Webhook Overview](/api-document/readme/webhook-overview.md)

### Prompt patterns that work well

Use short, task-based prompts.

Examples:

* Show the minimum Atlas sandbox booking flow.
* I have `routingIdentifier`. What should I call next?
* Compare `Verify` and `Get Offer` for new integrations.
* Which pages should I read before implementing ticketing polling?
* Where should I look for payment decline troubleshooting?
* Which webhook pages matter after ticketing completes?

### Ground rules

Use MCP as a navigation and implementation aid.

Keep these rules:

* treat [API Reference](/api-document/api-reference.md) as the source of truth for fields and schemas
* keep production secrets out of prompts
* validate request details against your actual environment
* complete [UAT Validation](/api-document/readme/quick-start/uat-submission-guide.md) before go-live

{% hint style="info" %}
GitBook MCP is available at [the MCP endpoint](https://resources.atriptech.com/~gitbook/mcp).
{% endhint %}

### Suggested workflow

1. Use MCP to find the right flow.
2. Open the matching overview or guide page.
3. Confirm fields and schemas in [API Reference](/api-document/api-reference.md).
4. Build and validate in [Sandbox Development](/api-document/readme/quick-start/sandbox-development.md).
5. Use troubleshooting pages when a call or state transition fails.
6. Move to [UAT Validation](/api-document/readme/quick-start/uat-submission-guide.md) when the flow is stable.

### Related pages

* [Quick Start](/api-document/readme/quick-start.md)
* [Sandbox Validation Test Kit](/api-document/readme/quick-start/sandbox-development/sandbox-validation-test-kit.md)
* [Booking Overview](/api-document/readme/booking-overview.md)
* [Troubleshooting & Support](/api-document/troubleshooting-and-support.md)


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://resources.atriptech.com/api-document/readme/quick-start/mcp-assisted-development.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.