Set up Codex

Add the Veracity MCP server to Codex so your agent queries current Veracity documentation and API references inside your workflow.

Add the Veracity Development MCP Server to Codex so your agent can query official Veracity documentation and API references without leaving your workflow.

An MCP server is a service that exposes tools, prompts, and resources to an agent over the Model Context Protocol. The Veracity Development MCP Server exposes six tools (covering documentation search, document retrieval, and live API exploration) that give your agent access to current official Veracity documentation and API definitions.

Before you begin

  • Codex installed (codex.com or via npm install -g @openai/codex)
  • A ChatGPT plan that includes Codex, or an OpenAI API key
  • Network access to https://docs.veracity.com/mcp

Steps

Add the MCP server

Codex loads MCP server configuration from ~/.codex/config.toml for a global configuration, or from .codex/config.toml in a trusted project for a project-scoped configuration. The Codex IDE extension and the CLI share this configuration.

  1. Create or open ~/.codex/config.toml.
  2. Add the Veracity Docs server entry:
[mcp_servers.veracity-docs]
url = "https://docs.veracity.com/mcp"
  1. Save the file. Codex loads the server on the next invocation.

To scope the server to a single project, add the same entry to .codex/config.toml in the project root instead. Codex only reads project-scoped configuration from trusted projects.

Add an instructions file

An AGENTS.md file gives Codex persistent project-level instructions. Adding a Veracity entry ensures the agent queries documentation tools for Veracity-related tasks automatically.

  1. Open or create AGENTS.md in your project root.
  2. Add the following section:
## Veracity documentation

When working with Veracity APIs, platform features, or authentication flows, query the veracity-docs MCP server before writing or modifying code. Available tools: search_Veracity_dev_docs, get_Veracity_doc_by_path, get_Veracity_doc_range, list_Veracity_platform_apis, get_Veracity_api_methods, get_Veracity_api_method.
  1. Save the file.

For instructions that apply across all projects, add the same content to ~/.codex/AGENTS.md.

Verify the result

Ask the agent a question that requires current Veracity documentation, such as:

  • How do I add Veracity authentication to my .NET project?
  • Show me the Veracity API reference for tenant management

The agent invokes search_Veracity_dev_docs or get_Veracity_doc_by_path and applies the retrieved documentation to your question. In the Codex TUI, type /mcp to confirm that veracity-docs appears in the list of active servers.

Troubleshooting

The server does not appear when running /mcp Confirm that config.toml is in the correct location and contains valid TOML. For a project-scoped configuration, confirm that Codex has marked the project as trusted.

The agent answers without using the MCP tools Reference the server explicitly in your prompt: Use the veracity-docs MCP to find the current authentication guide.

The server URL is unreachable Verify network access to https://docs.veracity.com/mcp. If your organisation proxies outbound HTTPS, add the URL to your allow list.