Skip to content

docs: add Connect AI Tools setup with MCP #84

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
AllenAJ wants to merge 1 commit into
base: main
Choose a base branch
from
Open

docs: add Connect AI Tools setup with MCP #84

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
103 changes: 103 additions & 0 deletions api-setup/connect-ai-tools.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -0,0 +1,103 @@
---
title: "Connect AI Tools"
description: "Connect Claude Code or Cursor to Request Network docs via MCP for live, queryable documentation access."
---

## Overview

Give your AI coding tools live access to Request Network docs. Once connected via MCP, your tool can search current documentation in real time instead of relying on stale snapshots.

## What is MCP?

The Model Context Protocol (MCP) is an open standard that lets AI applications connect to external tools and data sources in a consistent way.

When you connect docs through MCP, your assistant can query:

- Latest documentation content
- Updated endpoint details
- Current integration guides and examples

## MCP server URL

Use:

```text
https://requestnetwork.mintlify.app/mcp
```

## Claude Code

<Steps>
<Step title="Add the MCP server">
Run:

```bash
claude mcp add --transport http request-network-docs https://requestnetwork.mintlify.app/mcp
```
</Step>
<Step title="Verify the connection">
List configured MCP servers:

```bash
claude mcp list
```

You should see `request-network-docs`.
</Step>
Comment on lines +38 to +46
Copy link
Copy Markdown

@greptile-apps greptile-apps bot Mar 23, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

P2 Add <Check> callout to verification step

The AGENTS.md style guide shows that verification/confirmation steps inside <Steps> should use a <Check> callout component. The current "Verify the connection" step lists the expected output inline but doesn't use <Check>, missing the documented pattern for confirming success.

Suggested change
<Step title="Verify the connection">
List configured MCP servers:
```bash
claude mcp list
```
You should see `request-network-docs`.
</Step>
<Step title="Verify the connection">
List configured MCP servers:
```bash
claude mcp list
```
<Check>
You should see `request-network-docs` in the list.
</Check>
</Step>

Context Used: AGENTS.md (source)

Note: If this suggestion doesn't match your team's coding style, reply to this and let me know. I'll remember it for next time!

<Step title="Test a docs-grounded question">
In Claude Code, ask:

```text
How do I create a secure payment link and process webhook events?
```
</Step>
</Steps>

## Cursor

<Steps>
<Step title="Open MCP settings">
In Cursor, open MCP settings and add a new server.
</Step>
<Step title="Configure server">
Use:

- **Name**: `request-network-docs`
- **Transport**: `HTTP`
- **URL**: `https://requestnetwork.mintlify.app/mcp`
</Step>
<Step title="Validate in chat">
Ask a question about Request Network APIs and confirm the answer is grounded in docs content.
</Step>
</Steps>
Comment on lines +28 to +72
Copy link
Copy Markdown

@greptile-apps greptile-apps bot Mar 23, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

P2 Use <Tabs> for platform-specific alternatives

The AGENTS.md style guide explicitly states: "Use Tabs for platform-specific content or alternative approaches." Claude Code and Cursor are two alternative platforms, so they should be presented inside a <Tabs> component rather than as separate H2 sections. This keeps the page compact and follows the documented component selection policy.

Suggested change
## Claude Code
<Steps>
<Step title="Add the MCP server">
Run:
```bash
claude mcp add --transport http request-network-docs https://requestnetwork.mintlify.app/mcp
```
</Step>
<Step title="Verify the connection">
List configured MCP servers:
```bash
claude mcp list
```
You should see `request-network-docs`.
</Step>
<Step title="Test a docs-grounded question">
In Claude Code, ask:
```text
How do I create a secure payment link and process webhook events?
```
</Step>
</Steps>
## Cursor
<Steps>
<Step title="Open MCP settings">
In Cursor, open MCP settings and add a new server.
</Step>
<Step title="Configure server">
Use:
- **Name**: `request-network-docs`
- **Transport**: `HTTP`
- **URL**: `https://requestnetwork.mintlify.app/mcp`
</Step>
<Step title="Validate in chat">
Ask a question about Request Network APIs and confirm the answer is grounded in docs content.
</Step>
</Steps>
<Tabs>
<Tab title="Claude Code">
<Steps>
<Step title="Add the MCP server">
Run:
```bash
claude mcp add --transport http request-network-docs https://requestnetwork.mintlify.app/mcp
```
</Step>
<Step title="Verify the connection">
List configured MCP servers:
```bash
claude mcp list
```
You should see `request-network-docs`.
</Step>
<Step title="Test a docs-grounded question">
In Claude Code, ask:
```text
How do I create a secure payment link and process webhook events?
```
</Step>
</Steps>
</Tab>
<Tab title="Cursor">
<Steps>
<Step title="Open MCP settings">
In Cursor, open MCP settings and add a new server.
</Step>
<Step title="Configure server">
Use:
- **Name**: `request-network-docs`
- **Transport**: `HTTP`
- **URL**: `https://requestnetwork.mintlify.app/mcp`
</Step>
<Step title="Validate in chat">
Ask a question about Request Network APIs and confirm the answer is grounded in docs content.
</Step>
</Steps>
</Tab>
</Tabs>

Context Used: AGENTS.md (source)

Note: If this suggestion doesn't match your team's coding style, reply to this and let me know. I'll remember it for next time!


## Scripts and `llms.txt`

If you are building scripts or pipelines without an MCP client, use:

| URL | Use |
| --- | --- |
| `https://requestnetwork.mintlify.app/llms.txt` | Sitemap-style index of pages and descriptions |
| `https://requestnetwork.mintlify.app/llms-full.txt` | Full documentation in one Markdown file |

Mintlify generates these files on deployment and keeps them in sync with live docs.

## Suggested verification prompts

- "How do I configure webhook signature validation in Request Network?"
- "What is the difference between secure payments and standard requests?"
- "Which headers are required when using x-client-id?"

## Related docs

<CardGroup cols={3}>
<Card title="Authentication" href="/api-reference/authentication" icon="key">
API key and Client ID usage patterns.
</Card>
<Card title="Webhooks" href="/api-reference/webhooks" icon="webhook">
Signature verification, retries, and payloads.
</Card>
<Card title="Secure Payment Integration Guide" href="/api-features/secure-payment-integration-guide" icon="link">
End-to-end wallet + client ID + webhook + payment link flow.
</Card>
</CardGroup>
Comment on lines +91 to +103
Copy link
Copy Markdown

@greptile-apps greptile-apps bot Mar 23, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

P2 Missing troubleshooting section

The AGENTS.md style guide requires: "Include troubleshooting for likely failure points." For an MCP setup page, there are predictable failure modes that users will encounter:

  • The server URL is unreachable (firewall, proxy)
  • Transport type mismatch (sse vs http depending on the Claude CLI version)
  • A duplicate server name already registered

Consider adding an <AccordionGroup> section before "Related docs" to cover these cases, for example:

## Troubleshooting

<AccordionGroup>
  <Accordion title="MCP server not appearing after `claude mcp list`">
    Ensure you ran the `claude mcp add` command without errors. Re-run it and check for any output. If the URL is behind a corporate proxy, set `HTTP_PROXY` / `HTTPS_PROXY` environment variables before running Claude Code.
  </Accordion>
  <Accordion title="Connection errors in Cursor">
    Verify the URL `https://requestnetwork.mintlify.app/mcp` is reachable from your machine. Try opening it in a browser — you should receive a valid response. If not, check your network or firewall settings.
  </Accordion>
  <Accordion title="`--transport http` flag not recognised">
    Older versions of Claude CLI may require `--transport sse` instead. Run `claude --version` and update to the latest release if needed.
  </Accordion>
</AccordionGroup>

Context Used: AGENTS.md (source)

1 change: 1 addition & 0 deletions docs.json
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -66,6 +66,7 @@
"group": "🔑 API Setup",
"pages": [
"api-setup/getting-started",
"api-setup/connect-ai-tools",
"request-network-api/api-portal-manage-api-keys-and-webhooks",
"api-setup/migrate-to-v2"
]
Expand Down