Connect with Remote MCP

Remote MCP is recommended when your MCP client supports remote servers or custom connectors. You do not need to download or run the Amethyst MCP package on your computer.

Server URL

When your MCP client asks for a remote MCP server URL, use:

https://mcp.amethy.st/mcp

If your client manages MCP settings in mcp.json, start with this shape:

{
  "mcpServers": {
    "amethyst": {
      "type": "http",
      "url": "https://mcp.amethy.st/mcp"
    }
  }
}

Some clients use different field names for remote MCP transport. If your client does not accept type: "http", choose the HTTP or Streamable HTTP transport in that client’s settings and use the same url value.

Configure Codex

For Codex, add the remote MCP server to ~/.codex/config.toml:

[mcp_servers.amethyst]
url = "https://mcp.amethy.st/mcp"

Configure Claude custom connectors

For Claude custom connectors, see Anthropic’s remote MCP guide:

• Get started with custom connectors using remote MCP

Use https://mcp.amethy.st/mcp as the remote MCP server URL when Claude asks for the connector endpoint.

Complete authorization

Follow the authorization flow shown by your client. In the browser, sign in to Amethyst if needed, choose the workspaces to allow, and approve the request.

After authorization succeeds, ask your MCP client to use an Amethyst tool, for example:

List the Amethyst workspaces I can access.

Update workspace access

If you need to change the workspaces available to the client, remove or disconnect the Amethyst MCP connector in your client and connect it again.

Troubleshooting

• If your remote MCP client cannot connect, confirm that the server URL is exactly https://mcp.amethy.st/mcp.
• If authorization fails with a redirect or callback URL error, contact Amethyst support with the callback URL shown by your client.
• If a workspace does not appear, confirm that your Amethyst account has access to the workspace and that you selected it during authorization.