-
Notifications
You must be signed in to change notification settings - Fork 2
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.
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
RequestNetwork:main
Choose a base branch
from
AllenAJ:docs/connect-ai-tools
base: main
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Open
Changes from all commits
Commits
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
| 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> | ||
| <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> | ||
|
rodrigopavezi marked this conversation as resolved.
|
||
|
|
||
| ## 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> | ||
|
rodrigopavezi marked this conversation as resolved.
|
||
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
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.
Uh oh!
There was an error while loading. Please reload this page.