> For the complete documentation index, see [llms.txt](https://docs.apryse.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.apryse.com/explore-docs-with-ai/connect-to-mcp/set-up-cursor.md).
# Connect Cursor to Apryse docs
Bring Apryse SDK documentation into your Cursor workflows.
This guide explains how to connect Cursor to a Model Context Protocol (MCP) server that exposes published [Apryse docs](https://docs.apryse.com/). After you configure the connection, Cursor can access your documentation directly and use it to answer questions, retrieve information, and help with documentation-related tasks.
### Prerequisites
Before you start, make sure to:
* Obtain a Cursor account. See Cursor's [licensing details](https://cursor.com/pricing) for more.
* Install the [Cursor desktop app](https://cursor.com/download). See this [Cursor quickstart](https://cursor.com/docs/get-started/quickstart) for more.
* Sign in to Cursor desktop using your Cursor account.
{% hint style="info" %}
**Info:** This guide covers steps using the Cursor desktop app. Learn about [other ways](https://cursor.com/en-US/download) to use Cursor.
{% endhint %}
### 1. Add the MCP server
In this section, you'll add the MCP server to the Cursor UI and verify the connection. For more, see this [Cursor MCP quickstart](https://cursor.com/docs/mcp).
{% stepper %}
{% step %}
Open the Cursor desktop application.
{% endstep %}
{% step %}
From the sidebar navigation, select **Customize**, then click **MCPs**.
{% endstep %}
{% step %}
Click **+ New** to configure a new MCP connection.
{% endstep %}
{% step %}
Add the following to the `.cursor/mcp.json` file.
{% tabs %}
{% tab title="JSON" %}
{% code title=".cursor/mcp.json" overflow="wrap" %}
```json
{
"mcpServers": {
"apryse-docs": {
"url": "https://docs.apryse.com/~gitbook/mcp"
}
}
}
```
{% endcode %}
{% endtab %}
{% endtabs %}
* This configuration registers an MCP server named `apryse-docs` in Cursor.
* The `url` value specifies the MCP endpoint Cursor uses to access the server's documentation and tools.
* Use the server's HTTP endpoint when configuring the connection. The `stdio` and `sse` transport types aren't supported.
{% endstep %}
{% step %}
Save the file. The MCP server appears as connected, with an indicator of how many tools are enabled.
Click the connection to open a configuration modal that displays connection details and options to view, enable, or disable individual tools.
{% endstep %}
{% step %}
To verify the MCP server is available, open a **New Chat** and execute the following prompt:
{% prompt description="Check MCP server availability" defaultExpanded="full" %}
```markdown
What MCP servers and tools are available for me to work with?
```
{% endprompt %}
Successful output:
{% code overflow="wrap" expandable="true" %}
```
3. user-apryse-docs
Apryse documentation search and Q&A.
Tools:
askQuestion — natural-language questions with synthesized answers
searchDocumentation — search docs, APIs, and guides
getPage — fetch full markdown for a specific doc page
sendFeedback — report doc issues
mcp_auth — authenticate if needed
```
{% endcode %}
{% endstep %}
{% endstepper %}
### 2. Try a sample prompt
Ask Cursor questions about the documentation content the MCP server exposes.
{% prompt description="Build an implementation" icon="cursor" defaultExpanded="partial" %}
```markdown
How do I add PDF editing capabilities to a web application using Apryse WebViewer?
```
{% endprompt %}
{% prompt description="Build an implementation" icon="cursor" defaultExpanded="partial" %}
```markdown
How do I reorganize and reorder PDF pages using Java and the Apryse Server SDK?
```
{% endprompt %}
{% prompt description="Build an implementation" icon="cursor" defaultExpanded="partial" %}
```markdown
How do I redact text, images, and other sensitive information in PDFs using Apryse WebViewer?
```
{% endprompt %}
### 3. Remove the MCP server
These steps are optional and remove the Apryse documentation MCP server.
{% stepper %}
{% step %}
To remove the MCP server configuration from Cursor, delete that entry from the `.cursor/mcp.json` configuration file.
{% hint style="info" %}
**Info:** Cursor stores MCP server configurations in an `mcp.json` file located within a `.cursor` directory. Common locations include:
* macOS/Linux (user level): `~/.cursor/mcp.json`
* Windows (user level): `%USERPROFILE%\.cursor\mcp.json`
* Project level: `.cursor/mcp.json`
{% endhint %}
If you can't find the file, use Cursor's **Open File** command (**Cmd+P** on macOS or **Ctrl+P** on Windows/Linux) and search for `mcp.json`.
{% endstep %}
{% step %}
After making changes, restart Cursor to reload the MCP configuration.
{% endstep %}
{% step %}
Ask what MCP servers are available to make sure the `apryse-docs` MCP server was removed.
{% endstep %}
{% endstepper %}
### Troubleshooting
Cursor cannot find or connect to the MCP server.
* Verify that the MCP server URL is correct.
* Confirm that the `mcp.json` file contains valid JSON and is located in the correct `.cursor` directory.
* Restart Cursor after adding or updating the MCP configuration.
* Verify that the MCP server is running and reachable from your network.
* Check for firewall, VPN, or proxy restrictions.
Cursor doesn't detect MCP tools.
* Ask Cursor to list the tools available from the MCP server.
* Verify that the MCP server exposes tools and resources.
* Restart Cursor and reload the MCP configuration.
* Verify that the MCP server is connected and available.
Cursor cannot access documentation content.
* Confirm that the documentation has been published.
* Complete any required authentication when prompted.
* Verify that the MCP server has access to the documentation content.
* Verify that your account has permission to access the MCP server.
Cursor doesn't return the expected results.
* Verify that the content exists in the documentation.
* Try a more specific prompt.
* Confirm that the MCP server indexes the content you are searching.
* Verify that the expected MCP tools are available.
### Next steps
Explore setup guides for other supported AI coding assistants:
* [Set up Claude Code](/explore-docs-with-ai/connect-to-mcp/set-up-claude-code.md)
* [Set up Codex](/explore-docs-with-ai/connect-to-mcp/set-up-codex.md)
* [Set up GitHub Copilot](/explore-docs-with-ai/connect-to-mcp/set-up-github-copilot.md)
---
# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.
## 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, and the optional `goal` query parameter:
```
GET https://docs.apryse.com/explore-docs-with-ai/connect-to-mcp/set-up-cursor.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.
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.
