docs: add Connect AI Tools setup with MCP#84
Open
AllenAJ wants to merge 1 commit intoRequestNetwork:mainfrom
Open
docs: add Connect AI Tools setup with MCP#84AllenAJ wants to merge 1 commit intoRequestNetwork:mainfrom
AllenAJ wants to merge 1 commit intoRequestNetwork:mainfrom
Conversation
Add a dedicated API setup page for connecting Claude Code and Cursor via MCP, including Request Network Mintlify MCP and llms endpoints, then wire it into nav. Made-with: Cursor
Greptile SummaryThis PR adds a new Key points:
Confidence Score: 4/5
Important Files Changed
Sequence DiagramsequenceDiagram
participant Dev as Developer / AI Tool
participant CLI as Claude Code CLI
participant Cursor as Cursor IDE
participant MCP as requestnetwork.mintlify.app/mcp
participant Docs as Request Network Docs
Note over Dev,Docs: Claude Code setup
Dev->>CLI: claude mcp add --transport http request-network-docs <url>
CLI-->>Dev: Server registered
Dev->>CLI: claude mcp list
CLI-->>Dev: request-network-docs ✓
Note over Dev,Docs: Cursor setup
Dev->>Cursor: Add MCP server (name, transport HTTP, URL)
Cursor-->>Dev: Server saved
Note over Dev,Docs: Runtime doc query
Dev->>CLI: Ask docs-grounded question
CLI->>MCP: Query docs via MCP protocol
MCP->>Docs: Fetch latest content
Docs-->>MCP: Documentation response
MCP-->>CLI: Structured answer
CLI-->>Dev: Response grounded in live docs
Note over Dev,Docs: Script / pipeline (no MCP client)
Dev->>Docs: GET /llms.txt or /llms-full.txt
Docs-->>Dev: Sitemap index or full Markdown
Reviews (1): Last reviewed commit: "docs: add Connect AI Tools setup page" | Re-trigger Greptile |
![greptile-apps[bot]](https://avatars.githubusercontent.com/in/867647?s=60&v=4){kind=small}
Comment on lines
+28
to
+72
| ## 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> |
There was a problem hiding this comment.
<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!
Comment on lines
+38
to
+46
| <Step title="Verify the connection"> | ||
| List configured MCP servers: | ||
|
|
||
| ```bash | ||
| claude mcp list | ||
| ``` | ||
|
|
||
| You should see `request-network-docs`. | ||
| </Step> |
There was a problem hiding this comment.
<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!
Comment on lines
+91
to
+103
| ## 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> |
There was a problem hiding this comment.
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 (
ssevshttpdepending 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)
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
api-setup/connect-ai-toolsllms.txt/llms-full.txtlinksdocs.jsonWhy
Developers increasingly use AI coding tools. This page makes docs grounding setup explicit and copy-paste ready.
Test plan
Made with Cursor