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. 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 for more.
• Install the Cursor desktop app. See this Cursor quickstart for more.
• Sign in to Cursor desktop using your Cursor account.

Info: This guide covers steps using the Cursor desktop app. Learn about other ways to use Cursor.

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.

1

Open the Cursor desktop application.

2

From the sidebar navigation, select Customize, then click MCPs.

3

Click + New to configure a new MCP connection.

4

Add the following to the .cursor/mcp.json file.

JSON

.cursor/mcp.json

{
  "mcpServers": {
    "apryse-docs": {
      "url": "https://docs.apryse.com/~gitbook/mcp"
    }
  }
}

• 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.

5

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.

6

To verify the MCP server is available, open a New Chat and execute the following prompt:

Check MCP server availability

What MCP servers and tools are available for me to work with?

Successful output:

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

2. Try a sample prompt

Ask Cursor questions about the documentation content the MCP server exposes.

Build an implementation

How do I add PDF editing capabilities to a web application using Apryse WebViewer?

Build an implementation

How do I reorganize and reorder PDF pages using Java and the Apryse Server SDK?

Build an implementation

How do I redact text, images, and other sensitive information in PDFs using Apryse WebViewer?

3. Remove the MCP server

These steps are optional and remove the Apryse documentation MCP server.

1

To remove the MCP server configuration from Cursor, delete that entry from the .cursor/mcp.json configuration file.

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

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.

2

After making changes, restart Cursor to reload the MCP configuration.

3

Ask what MCP servers are available to make sure the apryse-docs MCP server was removed.

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
• Set up Codex
• Set up GitHub Copilot