For the complete documentation index, see llms.txt. This page is also available as Markdown.

Connect Codex to Apryse docs

Bring Apryse SDK documentation into your Codex workflows.

This guide explains how to connect Codex CLI to a Model Context Protocol (MCP) server that exposes published Apryse docs. After configuring the connection, Codex can access your documentation directly and use it to answer questions, retrieve information, and assist with documentation-related tasks.

Prerequisites

Before you start, make sure to:

Info: This guide uses the Codex CLI. Learn about other ways to use Codex.

1. Add the MCP server

First, add the MCP server to Codex and verify the connection. See the Codex MCP quickstart for more.

1

Open your terminal.

2

Add the MCP server:

codex mcp add apryse-docs --url https://docs.apryse.com/~gitbook/mcp

Codex may ask you to approve MCP requests or commands. Review each request before allowing it. Some clients can save your approval preference for future requests.

  • apryse-docs is the local name that Claude Code uses to identify the server.

  • You can replace apryse-docs as you prefer. It doesn't need to match the site name.

  • This server supports HTTP only. Don't use stdio. Configure with a url parameter and an HTTP endpoint.

3

Launch Codex:

codex

If prompted, sign in and complete browser authentication. Subsequent launches typically open directly in your terminal.

4

Verify that the server was added successfully:

codex mcp list

Successful output:

Configured MCP servers:

Name         URL                                                  Status
apryse-docs  https://docs.apryse.com/~gitbook/mcp                 enabled

2. Try a sample prompt

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

Info: Codex may fall back to doing a web search. To prevent this, be explicit and ask it to use the apryse-docs MCP first and to disclose any web fallbacks.

openaiBuild an implementation
openaiLearn about a feature
openaiBuild an implementation

3. Remove the MCP server

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

1

Remove the configured MCP server:

2

Remove the configured MCP server:

Troubleshooting

Codex cannot find or connect to the MCP server.
  • Verify that the HTTP endpoint URL for the MCP server is correct.

  • Don't use stdio or sse transport types.

  • Run codex mcp list to confirm the server is configured.

  • If the server is missing, add it again using codex mcp add.

  • Verify that the MCP server is running and reachable from your network.

  • Check for firewall, VPN, or proxy restrictions.

  • Don't use stdio or sse transport types.

Codex cannot access documentation content.
  • Confirm that the documentation has been published.

  • Complete any required authentication when prompted.

  • Verify that your account has permission to access the MCP server.

  • Verify that the MCP server provides access to the documentation content.

Codex 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 for.

  • Verify that the MCP server is connected and available.

Codex prompts for approval repeatedly.
  • Review and approve the requested action.

  • If available, choose the option to remember your approval preference.

  • Verify that your approval settings have not been reset.

  • Restart Codex and try again.

Next steps

Explore setup guides for other supported AI coding assistants:

Last updated

Was this helpful?