Installation and Configuration

The Thyris Documentation MCP is a public Streamable HTTP server. It does not require an API key, bearer token, OAuth flow, local process, or package installation.

Use this exact endpoint in every client:

https://docs.thyris.ai/mcp

Configuration names differ between clients. The following examples use thyris_docs as the server name.

Client	Recommended setup	Configuration scope
Claude and Claude Desktop	Add a custom remote connector	Claude account or organization
Claude Code	claude mcp add	User or project
OpenAI ChatGPT	Create a custom MCP app	User or workspace
Codex CLI	codex mcp add	User or project
Codex app and IDE extension	MCP server settings or shared Codex configuration	User or project
Visual Studio Code	MCP: Add Server or mcp.json	User profile or workspace

Claude and Claude Desktop

Claude web and Claude Desktop can use the endpoint as a custom remote connector. Because this is a remote connector, no claude_desktop_config.json, command, or local runtime is required.

Individual accounts

1. Open Customize → Connectors.
2. Select + → Add custom connector.
3. Set the connector name to Thyris Docs.
4. Enter https://docs.thyris.ai/mcp as the remote MCP URL.
5. Leave OAuth Client ID and Client Secret empty.
6. Select Add.
7. In a conversation, select + → Connectors and enable Thyris Docs.

Team and Enterprise organizations

An Owner or Primary Owner must add the connector first:

1. Open Organization settings → Connectors.
2. Select Add → Custom → Web.
3. Enter https://docs.thyris.ai/mcp.
4. Leave the optional OAuth fields empty.
5. Add the connector.

Organization members can then open Customize → Connectors, locate the custom connector, and select Connect.

Test it with:

Use Thyris Docs to explain the difference between Merchant MCP and UCP. Read the relevant sources and cite their URLs.

Claude connects to remote custom connectors from Anthropic infrastructure. The Thyris endpoint is already publicly reachable. See Anthropic's custom remote connector guide for current account and organization controls.

Claude Code

Add the server to your user scope so it is available in every project:

claude mcp add --transport http thyris_docs --scope user https://docs.thyris.ai/mcp

Verify the connection:

claude mcp get thyris_docs
claude mcp list

Inside an interactive Claude Code session, run:

/mcp

The server should appear as connected and expose seven tools.

Project-shared Claude Code configuration

To share the server with a repository, add it with project scope:

claude mcp add --transport http thyris_docs --scope project https://docs.thyris.ai/mcp

The generated .mcp.json representation is:

{
  "mcpServers": {
    "thyris_docs": {
      "type": "http",
      "url": "https://docs.thyris.ai/mcp"
    }
  }
}

Claude Code asks users to approve project-scoped MCP servers before using them. Do not omit "type": "http"; a URL without a type is treated as an invalid stdio configuration. See the official Claude Code MCP documentation.

OpenAI ChatGPT

ChatGPT configures remote MCP servers as custom apps. Availability and who may create or publish an app depend on the ChatGPT plan and workspace policy.

ChatGPT web

1. Confirm that Developer mode is available and enabled for your account or workspace.
2. Open Settings → Apps.
3. Select Create or Add custom app. In managed workspaces, an administrator may need to use Workspace settings → Apps → Create.
4. Set the name to Thyris Docs.
5. Enter https://docs.thyris.ai/mcp as the MCP endpoint.
6. Select no authentication when the UI asks for an authentication mechanism.
7. Select Scan Tools and wait for tool discovery to complete.
8. Select Create.
9. Start a new chat and enable Thyris Docs from the Apps or tools menu.

The tool scan should discover:

resolve_docs_action
research_docs
search_docs
get_document
read_documents
find_related_docs
list_doc_sections

ChatGPT desktop app

If the desktop app exposes direct MCP server settings:

1. Open Settings → MCP servers.
2. Select Add server.
3. Set the name to thyris_docs.
4. Choose Streamable HTTP.
5. Enter https://docs.thyris.ai/mcp.
6. Save and select Restart.
7. Use /mcp in the composer to inspect connected servers when available.

For hosted ChatGPT accounts that expose Apps rather than MCP server settings, use the ChatGPT web procedure above. ChatGPT web does not read local Codex configuration files. See the official OpenAI guides for ChatGPT developer mode and custom MCP apps and MCP client configuration.

Codex CLI

Add the remote server:

codex mcp add thyris_docs --url https://docs.thyris.ai/mcp

Confirm the configuration:

codex mcp get thyris_docs
codex mcp list

Inside the Codex terminal UI, run:

/mcp

No codex mcp login command is needed because this endpoint has no authentication.

Codex config.toml

The equivalent global configuration in ~/.codex/config.toml is:

[mcp_servers.thyris_docs]
url = "https://docs.thyris.ai/mcp"
enabled = true
required = false
startup_timeout_sec = 10
tool_timeout_sec = 60
enabled_tools = ["resolve_docs_action", "research_docs", "search_docs", "read_documents", "get_document", "find_related_docs", "list_doc_sections"]
default_tools_approval_mode = "auto"

For project-only configuration, place the same table in .codex/config.toml inside a trusted project. All Thyris Documentation MCP tools are read-only, so automatic tool approval is appropriate unless an organization requires confirmation for every external call.

The Codex CLI, Codex IDE extension, and ChatGPT desktop app share Codex MCP configuration on the same host. ChatGPT web is configured separately. See the official OpenAI Codex MCP guide and configuration reference.

Codex App and IDE Extension

The graphical Codex clients can use the server without running the CLI command:

1. Open the gear menu.
2. Select MCP servers.
3. Select Add server.
4. Enter thyris_docs as the name.
5. Choose Streamable HTTP.
6. Enter https://docs.thyris.ai/mcp.
7. Save and select Restart extension or restart the app.

The server list should show the endpoint as enabled. If the client is on the same host where the Codex CLI configuration was added, the server may already be present because these clients share config.toml.

Visual Studio Code

These instructions apply to VS Code chat clients that support MCP, including GitHub Copilot agent mode.

Command Palette setup

1. Open the Command Palette.
2. Run MCP: Add Server.
3. Choose HTTP.
4. Enter https://docs.thyris.ai/mcp.
5. Enter thyris_docs as the server ID.
6. Choose Global to use it across projects or Workspace to share it with the current repository.
7. Confirm that you trust the server when VS Code prompts you.

Workspace configuration

Create .vscode/mcp.json:

{
  "servers": {
    "thyris_docs": {
      "type": "http",
      "url": "https://docs.thyris.ai/mcp"
    }
  }
}

For a user-level configuration, run MCP: Open User Configuration and add the same entry to the servers object.

Verify in VS Code

1. Run MCP: List Servers from the Command Palette.
2. Select thyris_docs and start or restart it if required.
3. Open Chat in Agent mode.
4. Select Configure Tools and confirm that the Thyris tools are available.
5. If startup fails, select Show Output from the server actions to inspect the MCP log.

VS Code uses servers, while Claude Code uses mcpServers; do not copy one wrapper key into the other client's configuration. See the official VS Code MCP server guide.

MCP Inspector

Start MCP Inspector:

npx @modelcontextprotocol/inspector@latest

Use:

Transport: Streamable HTTP
URL: https://docs.thyris.ai/mcp

Connect, select List Tools, and invoke resolve_docs_action with:

{
  "action": "Explain what Thyris Merchant Services provides and cite the relevant documentation."
}

Generic Streamable HTTP Clients

Use the client's equivalent of this logical configuration:

{
  "name": "thyris_docs",
  "transport": "streamable_http",
  "url": "https://docs.thyris.ai/mcp"
}

Exact keys vary by client. The client must support MCP over Streamable HTTP and send MCP JSON-RPC requests to the exact /mcp path.

Do not use https://docs.thyris.ai/docs or the site root as the MCP URL. Those routes serve HTML rather than the MCP protocol.

Client-specific Troubleshooting

Symptom	Check
Claude Code reports a missing command	Ensure the entry has "type": "http"; do not configure the URL as stdio.
Claude web cannot see the connector	Enable it for the current conversation and confirm organization connector policy.
ChatGPT cannot create or scan the app	Confirm plan availability, Developer mode, workspace role, and app permissions.
Codex does not show the server	Run codex mcp get thyris_docs, then restart the app or extension.
VS Code does not show tools	Trust and start the server, then check MCP: List Servers → Show Output.
Any client returns HTML	Confirm that the URL ends with /mcp, not /docs or /.
Requests start returning 429	The endpoint permits 30 MCP HTTP requests per minute per client. Retry after the returned delay.